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

Extending the bus network

Use this task to extend a network of service integration buses.

Before you begin

The buses must exist and each bus have at least one bus member before you can connect them.

Why and when to perform this task

You can add a bus to an existing network of buses to enable all of the buses to exchange messages. To extend the bus network in this way, carry out the following steps:

Steps for this task

  1. In the bus to be added, create a foreign bus for each of the buses already in the network. See Adding a foreign bus. Use a direct routing definition type for one of the foreign buses; the existing bus that this foreign bus represents will act as the "next bus in route" through which other buses in the network can link to the bus to be added. Use an indirect routing definition type for the other buses, using the "next bus in route" foreign bus as the next bus in the route. This provides the indirect link routing to the other buses.
  2. In each of the buses in the network, create a foreign bus for the bus to be added. For the bus that will be connected directly to the new bus, use a direct routing definition type. For the other buses use an indirect routing definition type, which provides the indirect link routing to the bus to be added.
  3. In the bus to be added, create a service integration bus link from the messaging engine that is to host the link to the next bus in route. See Adding a service integration bus link This associates the messaging engine with the routing definition (virtual link).
  4. In the next bus in route, create a service integration bus link from the messaging engine that is to host the link to the bus to be added. The name of the service integration bus link must match the name of the service integration bus link that you created in the bus to be added. This associates the messaging engine with the routing definition.
  5. Restart the messaging engine in each bus (or restart the server that contains the messaging engine). The service integration bus link is started when the messaging engine is started, as long as its Initial state is configured as started.
All of the buses are now connected and they can exchange messages.
For example, 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 concepts
Foreign buses

Task topic

Terms of Use | Feedback

Last updated: 2 Aug 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.express.doc\tasks\tjj0092_.html

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