Forwarding Messages to a Remote Cluster or Territory
Provide the complete destination name if you want to forward the messages delivered to a queue on the local cluster or territory to a remote cluster or territory across the gateway.
For example, if you specify the destination as:
Q1,
Broker will try to deliver the message only to the Q1 queue present on the same
Broker.
Broker2/Q1,
Broker will try to deliver the message only to the Q1 queue on Broker2 in the same territory or cluster.
/Cluster2/Broker2/Q1,
Broker will try to find a gateway that reaches Cluster2, forward the message through the gateway if the forward permissions are configured for the gateway, and deliver the message to the Q1 queue on Broker2.
While forwarding messages to a remote cluster or territory, if the message delivery path involves multiple Broker hops, enable the dead letter queue on all the Brokers so that if any message gets dropped, you can trace which Broker dropped the message.