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

Connecting buses

Use these tasks to connect service integration buses in a network.

You might use separate service integration buses for different departments within organizations, or perhaps to separate test and production facilities. Whilst you can use these buses separately, you can also connect them to allow messages to pass between the 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.

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. Consider the following 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. Then you then select messaging engine M1 and create a service integration bus link. In the link properties, you set the Remote messaging engine name field to M2 and the Bootstrap endpoints field to hostname:portname. The host name is the name of the server containing messaging engine M2, and the port name is the SIB_ENDPOINT_ADDRESS of the application server that M2 runs on. In bus B2, you create a foreign bus to represent B1. Then you select messaging engine M2 and create a link back to M1.

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

If the messaging engine M2 is in a cluster and might run on any one of several servers, you list all the possible hostname:portname values in the Bootstrap endpoints field, separating each value with a comma.

This example shows that 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 names 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.

Related concepts
Service integration buses
Foreign buses
Direct and indirect routing between service integration buses
Related tasks
Planning a multiple-bus topology
Creating a foreign bus destination

Task 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\tasks\tjj0090_.html

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