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

Connecting buses directly

You can connect two service integration buses directly, so they can exchange messages.

Before you begin

The buses must exist, and each bus must have at least one bus member before you can connect them. The buses can be in the same cell, or in different cells.
Note: The buses that you connect must have unique names. The connection fails if the buses have the same name.

Why and when to perform this task

To connect two separate bus configurations so that messages can be exchanged between them:

Steps for this task

  1. Start with one bus, create a foreign bus definition to represent the second bus using a direct routing definition type, see Adding a foreign bus for instructions.
  2. In the second bus, create a foreign bus to represent the first bus, again using a direct routing definition type.
  3. In the first bus:
    1. Optional: Create a topic space mapping, see Creating topic space mappings You need only create a topic space mapping if you need to connect topic spaces. See Configuring topic space mappings between service integration buses
    2. Configure destination defaults, unless a foreign destination will be created explicitly. See Configuring destination defaults for a foreign bus
  4. In the first bus, create a service integration bus link from the messaging engine that is to host the link to the second (foreign) bus. See Adding a service integration bus link. This associates the messaging engine with the virtual link.
  5. In the second bus, create a service integration bus link from the messaging engine that is to host the link to the first (foreign) bus. The name of the service integration bus link must match the name of the service integration bus link that you created in the first bus. This associates the messaging engine with the virtual link.
  6. Restart the messaging engine in the first bus (restart the server that contains the messaging engine). The service integration bus link is started when the messaging engine is started.
  7. Restart the messaging engine in the second bus (restart the server that contains the messaging engine).

The two buses are now connected and they can exchange messages. When you create default messaging resources, configure the connection factory to connect to the local bus, and configure the destination to connect to the foreign bus.
Related concepts
Foreign buses
Direct and indirect routing between service integration buses
Multiple bus topology
Related information
JMS connection factory settings

Task topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjj0091_.html

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