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

One bus, multiple bus members
In this topology, there are multiple non-clustered application servers connected
as members of the bus (Figure 10-5). In this topology, most, if not all servers are
bus members. Take care to locate the queue points on the same application
server as the messaging application that is the primary user of the queue. This
will maximize the use of local connections and enhance performance.
Local
connection
Application server
Messaging
application
MDB
Messaging
application
Messaging
Engine
Queue point (A)
Messages
Queue destination
(A)
Bus
Local
connection
Figure 10-5 Single bus with multiple application server members
Application server
Messaging
application
MDB
Messaging
application
Messaging
Engine
Queue point (B)
Messages
Queue destination
(B)
Multiple buses
Many scenarios only require relatively simple bus topologies, perhaps even just a
single server. When integrating applications that have been deployed to multiple
servers, it is often appropriate to add those servers as members of the same bus.
However, servers do not have to be bus members to connect to a bus. In more
complex situations, multiple buses can be interconnected to create more
complicated networks.
A service integration bus cannot expand beyond the edge of a WebSphere
Application Server cell. When you need to use messaging resources in multiple
cells, you can connect the buses of each cell to each other. An enterprise might
also deploy multiple interconnected service integration buses for organizational
reasons. For example, an enterprise with several autonomous departments
might want to have separately administered buses in each location. Or perhaps
separate but similar buses exist to provide test or maintenance facilities.
If you use messaging resources in a WebSphere MQ network, you can connect
the service integration bus to the WebSphere MQ network, where it appears to
be another queue manager. This is achieved through the user of an MQ link.
Chapter 10. Messaging 347