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 or server clusters that host a messaging engine in the service integration bus are called bus members.




Subtopics
Single-server bus
Multiple-server bus without clustering
Multiple-server bus with clustering
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-server buses without clustering
Planning issues for multiple-server buses with clustering
Planning issues for multiple-bus topologies
Planning issues for topologies that include WebSphere MQ
Service integration topologies
Learning about service integration buses
Concept topic    

Terms of Use | Feedback

Last updated: Sep 20, 2010 10:03:57 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-zos&topic=cjj0003_
File name: cjj0003_.html