Single-server bus

The simplest topology is a bus consisting of a single server. Use this configuration if there is a low volume of message throughput and scalability is not essential.

In a single-server bus, there is one messaging engine. All destinations, such as queues and topic spaces, are assigned to this single messaging engine.

To decide whether a single messaging engine is adequate, consider factors such as the number of client connections, message throughput rates, and the size of messages.

Figure 1. Service integration bus with a single member
In this figure, a service integration bus with an application server hosts a messaging engine. A bus destination is attached to the messaging engine.

Use this single-server bus topology for a single server environment.

An application can connect to the messaging engine, and therefore can connect to and use the bus, in any of the following situations:
[Fix Pack 35 or later]
Figure 2. Applications connecting to a messaging engine
In this figure, there are applications in the server bus member, the same cell with a client connection, and in a different cell with a client connection. All connect to the messaging engine in the server bus member.




Related concepts
Planning issues for bus topologies
Planning issues common to all bus topologies
Planning issues for single-server bus topologies
Bus topologies
Concept topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 5:25:00 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-base-dist&topic=cjj0070_
File name: cjj0070_.html