Chapter 1. Features
1.1. Address federation
You can federate a
standard address space type with another AMQP server, meaning that an address of the remote AMQP server is mapped into the address space.
To enable address federation, you need to create an address space connector. For more information see Address space connector examples.
1.2. Message forwarding
Message store-and-forward involves automatically forwarding messages from a local address to a remote AMQP server outside of AMQ Online, or forwarding messages from a remote AMQP server to a local address.
To enable message store-and-forward, you first need to create an address space connector, and then you need to create an address forwarder for each address. For more information see Address space connector examples and Address forwarding examples.
For message store-and-forward, with the
queue address type, messages can be forwarded to a remote AMQP server or messages can be forwarded from a remote AMQP server to a local queue. With the
subscription address type, you can create a forwarder to a remote AMQP address, but you cannot create a forwarder that copies messages to the subscription.
Note that when using the message store-and-forward method to move messages from a local address to an address of the remote AMQP server, the way that the remote AMQP server signals error conditions, such as space constraints or other transient issues, is important. If the remote server uses the AMQP 1.0 rejected delivery state, affected messages are placed into the global dead-letter queue (DLQ). Using the Red Hat AMQ Console, you can view the number of messages that have been rejected in this way. For more information about how to view these messages in the Red Hat AMQ Console, see Viewing message and connection statistics using the Red Hat AMQ Console.
1.3. Purge queues and subscriptions
Using the Red Hat AMQ Console, you can purge—that is, clear all messages from—queues and subscriptions. For more information see Purging queues and subscriptions.