Bus topologies

You can connect buses in different ways depending on your requirements. For example, you can link messaging engines to distribute message workload, and to provide system availability if there is a system failure.

A topology that consists of a single messaging engine might be adequate for some applications. Deploying more than one messaging engine, and linking them together, has advantages:

A bus topology can contain links to WebSphere® MQ networks. This allows messages to flow between applications connected to a WebSphere MQ queue manager and applications attached to a service integration bus.

The application servers that host a messaging engine in the service integration bus are called bus members. A WebSphere MQ server can be a bus member, but it does not host a messaging engine.




Subtopics
Single-server bus
Interconnected buses
Related concepts
Planning issues for bus topologies
Planning issues common to all bus topologies
Planning issues for single-server bus topologies
Planning issues for multiple-bus topologies
Planning issues for topologies that include WebSphere MQ
Service integration topologies
Learning about service integration buses
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 4:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-dist&topic=cjj0003_
File name: cjj0003_.html