Multiple-server bus without clustering

A bus that consists of multiple servers provides advantages of scalability, the ability to handle more client connections, and greater message throughput. A multiple-server bus includes multiple messaging engines that can share the work of distributing the messages.

Another advantage of a multiple-server bus is that you can locate the queue that an application consumes from in the same application server as that application, which might be more efficient if there are multiple application servers running applications.

You can configure a bus to have multiple server bus members, each of which runs one messaging engine. All the servers in the bus must belong to the same cell.

All of the messaging engines in the bus are implicitly connected, and applications can connect to any messaging engine in the bus. All the messaging engines in the bus know about the resources that are assigned to each messaging engine in that bus.

The messaging engines do not need to all run at the same time; if one messaging engine stops, the other messaging engines in the bus continue to operate. However, if a messaging engine stops, the resources that the messaging engine owns are unavailable. Specifically, the destinations that are assigned to that messaging engine are unavailable.

Figure 1. Service integration bus with multiple servers
In this figure, a service integration bus has three server bus members. Each server hosts a messaging engine. There are two bus destinations, each attached to a messaging engine.




Related concepts
Planning issues for bus topologies
Planning issues common to all bus topologies
Planning issues for multiple-server buses without clustering
Planning issues for multiple-server buses with clustering
Bus topologies
Concept topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=cjj0071_
File name: cjj0071_.html