A messaging application connected to one bus can send messages to a point-to-point queue in another bus, when the two buses are connected.
When creating the message producer for a queue in a different bus, you identify the name of the bus that hosts the queue, that is, defining it as its foreign bus. You then establish a service integration bus link that connects those two buses. A foreign bus is a representation of another service integration bus, or a WebSphere MQ queue manager, with which an existing service integration bus, or a WebSphere MQ queue manager, can exchange messages. The local bus knows of the destination’s bus through a foreign bus definition. If the bus directly connected to the local bus does not hold the specified destination, more service integration links are used to flow the message to the next bus on route to the destination’s bus. When the message enters the destination’s bus that bus will attempt to deliver the message to the intended destination.
When sending to a destination, you get a number of messaging defaults and the defaults apply when sending to destinations in a foreign bus. These defaults are inherited from the Destination defaults associated with a foreign bus definition. It is possible to administratively override these defaults for individual destinations in foreign buses. You can do this by defining a Foreign Destination in the local bus that identifies the destination in the foreign bus, and explicitly sets the defaults associated with it. For more information see Configuring destination defaults for a foreign bus.