Bus members

The members of a service integration bus can be application servers or server clusters. Bus members that are application servers or server clusters contain messaging engines, which are the application server components that provide asynchronous messaging services.

To use a service integration bus, you must add at least one member that is an application server or server cluster.

Adding a bus member automatically creates a messaging engine for that bus member. Each messaging engine has its own data store, used for example to store persistent messages and maintain durable subscriptions. By default a messaging engine associated with a server is configured with an in-process, Cloudscape-based data store. In other cases, you are asked to provide the Java™ Naming and Directory Interface (JNDI) name of a Java Database Connectivity (JDBC) data source for use by the messaging engine.

When the bus member is an application server, it can have only one messaging engine. If the bus member is a server cluster, it can have additional messaging engines to provide high availability or workload sharing characteristics.

To host queue-type destinations, the messaging engine can hold messages until consuming applications are ready to receive them. Each messaging engine also has a data store where it can hold messages so that if the messaging engine fails, messages are not lost.

When you define a queue-type destination, you assign it to a bus member. When that bus member is an application server or a server cluster, the messaging engine (or engines) in that bus member holds the messages.

A WebSphere® Application Server application does not have to be running on a service integration bus member to use its messaging services. If necessary, WebSphere Application Server automatically provides a connection to a suitable bus member.

If required, you can remove members from a bus. However, this action deletes any messaging engines that are associated with a bus member, including knowledge of any messages held by the data store for those messaging engines. Therefore, you must plan this action carefully.

When a bus member is deleted, the data source associated with this bus member is not automatically deleted, because users often associate their own data source with a bus member. This also applies to bus members created using the default data source: the data source is not automatically deleted and you must remove it manually.

If you do not delete the data source manually and another messaging bus member is created, the messaging engine will fail to start.




Related concepts
Learning about service integration buses
Related tasks
Configuring the members of a bus
Listing the members of a bus
Removing a member from a bus
Listing the messaging engines defined for a server bus member
Listing the messaging engines for a cluster bus member
Adding a messaging engine to a cluster
Removing a messaging engine from a cluster
Setting up the data store for a messaging engine
Configuring a messaging engine to use a data store
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=cjj0020_
File name: cjj0020_.html