-
Language:
English
-
Language:
English
Chapter 8. Interoperability
This chapter discusses how to use AMQ Ruby in combination with other AMQ components. For an overview of the compatibility of AMQ components, see the product introduction.
8.1. Interoperating with other AMQP clients
AMQP messages are composed using the AMQP type system. This common format is one of the reasons AMQP clients in different languages are able to interoperate with each other.
When sending messages, AMQ Ruby automatically converts language-native types to AMQP-encoded data. When receiving messages, the reverse conversion takes place.
More information about AMQP types is available at the interactive type reference maintained by the Apache Qpid project.
Table 8.1. AMQP types
| AMQP type | Description |
|---|---|
| An empty value | |
| A true or false value | |
| A single Unicode character | |
| A sequence of Unicode characters | |
| A sequence of bytes | |
| A signed 8-bit integer | |
| A signed 16-bit integer | |
| A signed 32-bit integer | |
| A signed 64-bit integer | |
| An unsigned 8-bit integer | |
| An unsigned 16-bit integer | |
| An unsigned 32-bit integer | |
| An unsigned 64-bit integer | |
| A 32-bit floating point number | |
| A 64-bit floating point number | |
| A sequence of values of a single type | |
| A sequence of values of variable type | |
| A mapping from distinct keys to values | |
| A universally unique identifier | |
| A 7-bit ASCII string from a constrained domain | |
| An absolute point in time |
Table 8.2. AMQ Ruby types before encoding and after decoding
| AMQP type | AMQ Ruby type before encoding | AMQ Ruby type after decoding |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 8.3. AMQ Ruby and other AMQ client types (1 of 2)
| AMQ Ruby type before encoding | AMQ C++ type | AMQ JavaScript type |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table 8.4. AMQ Ruby and other AMQ client types (2 of 2)
| AMQ Ruby type before encoding | AMQ .NET type | AMQ Python type |
|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
8.2. Interoperating with AMQ JMS
AMQP defines a standard mapping to the JMS messaging model. This section discusses the various aspects of that mapping. For more information, see the AMQ JMS Interoperability chapter.
JMS message types
AMQ Ruby provides a single message type whose body type can vary. By contrast, the JMS API uses different message types to represent different kinds of data. The table below indicates how particular body types map to JMS message types.
For more explicit control of the resulting JMS message type, you can set the x-opt-jms-msg-type message annotation. See the AMQ JMS Interoperability chapter for more information.
Table 8.5. AMQ Ruby and JMS message types
| AMQ Ruby body type | JMS message type |
|---|---|
|
| |
|
| |
|
| |
| Any other type |
8.3. Connecting to AMQ Broker
AMQ Broker is designed to interoperate with AMQP 1.0 clients. Check the following to ensure the broker is configured for AMQP messaging:
- Port 5672 in the network firewall is open.
- The AMQ Broker AMQP acceptor is enabled. See Default acceptor settings.
- The necessary addresses are configured on the broker. See Addresses, Queues, and Topics.
- The broker is configured to permit access from your client, and the client is configured to send the required credentials. See Broker Security.
8.4. Connecting to AMQ Interconnect
AMQ Interconnect works with any AMQP 1.0 client. Check the following to ensure the components are configured correctly:
- Port 5672 in the network firewall is open.
- The router is configured to permit access from your client, and the client is configured to send the required credentials. See Securing network connections.
