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

Direct and indirect routing between service integration buses

You can use direct and indirect links to connect service integration buses together so that all of the buses can exchange messages.

Buses can be linked directly or indirectly. In the case of a direct connection, two buses are connected directly by a single service integration bus link. In the case of an indirect connection, there are one or more intermediate buses connected in a chain of links between the two buses. For example, to get indirectly from Bus A to Bus C, your messages might be routed through a link from Bus A to Bus B, then through another link from Bus B to Bus C.

Each bus needs to know how to get to every other bus to which it is connected. In this context, the bus in question is referred to as the local bus, and each of the buses to which it is connected is referred to as a foreign bus. Routing information from the local bus to each foreign bus is stored in the local bus in a routing definition, also known as a virtual link. The routing definition indicates: For more information about foreign buses, see Foreign buses.

The following diagram shows an existing network of three buses, Bus 1, Bus 2 and Bus 3, to which a new bus, Bus n, is to be added. Bus n will be connected directly to Bus 1, and indirectly to Buses 2 and 3.

A network of three service integration buses, bus 1, bus 2 and bus 3, connected in a linear fashion by two service integration bus links between messaging engines in each bus. A fourth bus, bus n, is yet to be added to the network.

To add Bus n to the network, the following items are created:

In Bus n:

In Bus 1:

In Bus 2:

In Bus 3:

The following diagram illustrates the network after adding Bus n.

A network of three service integration buses, bus 1, bus 2 and bus 3, connected in a linear fashion by two service integration bus links between messaging engines in each bus. A fourth bus, bus n, is now linked to the rest of the network via Bus 1.

Related tasks
Connecting buses
Connecting buses directly
Extending the bus network
Configuring foreign buses
Adding a foreign bus
Configuring the properties of a foreign bus
Listing the foreign buses
Removing a foreign bus
Configuring destination defaults for a foreign bus
Creating a routing definition
Configuring a routing definition
Removing a routing definition
Configuring service integration bus links
Creating a foreign bus destination
Planning a bus topology
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\cjj0092_.html

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