WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Multiple bus topology

A topology can contain multiple interconnected service integration buses.

Separate service integration buses might be used for different departments within organizations, or perhaps to separate test and production facilities. Whilst you can use these buses in their own right, you can also connect them to allow messaging across buses. You can also connect together buses in different organizations. When buses are interconnected, applications can send messages to applications on other buses, and use resources provided on other buses. Published messages can span multiple buses where the links between the buses are configured to allow it.

A bus must be contained within a single cell; that is, a bus cannot span multiple cells. However, a cell may contain more than one bus. In this case, each bus in the cell is foreign to each other bus in the cell. You can connect buses together within a cell, or between different cells. Regardless of where a bus exists, if one bus is foreign to the other, a foreign bus link is required, in both directions.

The process for linking one bus to another bus is the same, whether the buses are in the same cell or in different cells.

To create a link between two buses, the administrator of the first bus creates a foreign bus that represents the second bus, as a property of the local bus. The administrator of the second bus also creates a foreign bus to represent the first bus, as a property of the second bus. Each administrator then creates a virtual link and a physical link (called a service integration bus link) from the local bus to the foreign bus.

The difference between linking buses within the same cell, and in different cells lies in the values you define when you create the link. For example, you have a bus called B1 in a cell called C1 that you want to link to bus B2 in cell C2. In bus B1, you choose a messaging engine called M1 to host the link. In bus B2, you choose a messaging engine called M2 to host the link back to B1. In bus B1, you create a foreign bus to represent B2. For M1, you create a service integration bus link. You use the Bootstrap endpoints field to identify the server (or, in a cluster, the servers) containing messaging engine M2.

If you are running with security enabled, use the SIB_ENDPOINT_SECURE_ADDRESS port.

There is no difference in how you set up the link for buses within the same cell or in different cells. In both cases, you provide values for the bootstrap endpoints. In one case, you provide the name of a server in the same cell, and in the other case you name a server in a different cell.

The route between two buses can be made indirectly, through one or more intermediate foreign buses.

The administrator can define a foreign destination that identifies a destination on another bus. A foreign destination enables an application on one bus to access directly the destination on the other bus. If a foreign destination is not explicitly defined, destination defaults can be defined.

Foreign buses provides more information about messaging across interconnected buses.

Figure 1. Service integration buses in a multiple-bus topologyThree service integration buses connected through a service integration bus link on a messaging engine in each of the buses.
Related tasks
Planning a bus topology
Planning issues common to all bus topologies
Planning a multiple-server bus without clustering
Planning a multiple-server bus with clustering
Planning a multiple-bus topology
Planning a topology that includes WebSphere MQ

Concept topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\concepts\cjj0004_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)