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

Foreign buses

A foreign bus is a property of a service integration bus, and represents a bus in another cell (or within the same cell) or a WebSphere MQ network, with which the service integration bus can exchange messages.

Messages are routed to a foreign bus either directly through a link between the two buses, or indirectly through one or more intermediate buses. Regardless of where buses exist, of one is foreign to the other, it requires a foreign bus link. For example, if a cell contains more than one bus, each of the buses within it are regarded as foreign to one another. Before you can create and configure a link, you must create a foreign bus.

Notes:
  • When you create a foreign bus that represents another service integration bus, the name of the foreign bus must match the name of the other service integration bus.
  • When you intend to link two buses directly, you must assign them unique names.
  • You must not change the name of a foreign bus name after it has been configured.

In Figure 1, buses 1 and 2 are linked directly, while buses 1 and 3 are linked indirectly through bus 2.

Figure 1. Linking of service integration buses. Three service integration buses connected through a service integration bus link on a messaging engine in each of the buses.
The routing definition (virtual link) for a foreign bus indicates the type of physical link, as follows:

You can define an explicit destination on a foreign bus, to which an application can send messages. You can also configure default properties to be used for messages sent to destinations on a foreign bus when there is no explicit foreign destination definition, and the application does not explicitly provide values for the properties. An application cannot receive messages from a foreign destination; it can only consume messages from a destination on the bus to which it is connected.

An application subscribing to a local topic space can receive messages published to a topic on a foreign bus. To allow publish/subscribe messaging between buses, topic space names on a local bus must be mapped to topic space names on a foreign bus.

A topic space mapping allows subscribers on the local topic space to receive messages published in the foreign topic space. For publications to flow from the local topic space into the foreign bus, an equivalent topic space mapping is required by the foreign bus.

Topic space mapping is administered through the routing properties for a foreign bus. Topic space names for the local bus are mapped to topic space names defined on the foreign bus. It will be common for the two names to match. Note that mapping two topic spaces implies that the topics within them are "the same".

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

Concept 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\concepts\cjj0030_.html

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