Bus configurations

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 availability if there is a system failure.

A configuration that only has a single messaging engine might be adequate for some applications however, deploying more than one messaging engine and linking them together provides the following advantages:

The application servers that host a messaging engine in the service integration bus are called bus members. A WebSphere MQ server is the WebSphere MQ equivalent of a messaging engine. You can make a WebSphere MQ server a member of a bus, which becomes a messaging engine which is not hosted by an application server.

A bus configuration can include one or more bootstrap members. When an application needs a connection to the bus, it connects to the bootstrap member, which authenticates the request, and then directs the connection request to a suitable bus member. A bootstrap member responds only to bootstrap requests and does not always host a messaging engine.

If a bus configuration uses multiple security domains, you can isolate buses and the applications that use them by configuring the bootstrap members so that only a subset of servers can access a bus.

Concept topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 3:36:59 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-express-iseries&topic=cjj0003_
File name: cjj0003_.html