WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

Figure 10-6 illustrates how a service integration bus can be connected to another
service integration bus and to a WebSphere MQ network.
Alias
destination
Application server
Queue
destination
Messaging
application
Messaging
Engine
Bus Link
Application server
Foreign bus
Foreign bus
Bus Link
Messaging
Engine
Figure 10-6 Multiple bus scenario
Bus
Bus
QMGR
WebSphere MQ
In the case of the connection between the two service integration buses, each
messaging engine contains a service integration bus link configuration that
defines the location of the messaging engine on the remote bus.
For the WebSphere MQ connection, the messaging engine contains an MQ link
configuration that defines the queue manager on WebSphere MQ and identifies
a queue manager name that it will be known by from the view of the WebSphere
MQ network.
When an application sends a message to a queue on the remote bus, it can send
it to an alias destination defined on the local bus that points to the queue
destination on the second bus.
Because there is a single link to a foreign bus, there is no workload management
capability. It is important to note that an application cannot consume messages
from a destination in a foreign bus.
348 WebSphere Application Server V7.0: Concepts, Planning, and Design
Application server
Messaging
application
Messaging
Engine
MQ Link
Foreign bus
Queue
Alias
destination
MQ
client