WebSphere WebSphere Application Server Version 6.1.x Feature Pack for Web Services Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Bus member types and their effect on high availability and workload sharing configuration

You can add either a server or a cluster to a service integration bus, to create either a server bus member or a cluster bus member.

Adding a server to a bus

When you add a server to a service integration bus, a messaging engine is created automatically. This single messaging engine cannot participate in workload sharing with other messaging engines; it can only do that in a cluster. The messaging engine also cannot be highly available, since there are no other servers in which it can run.

Adding a cluster to a bus

When you add a server cluster to a service integration bus, a single messaging engine is created automatically; you can then add further messaging engines if required. The rest of the information in this topic applies only to cluster bus members.

A cluster deployment can provide workload sharing, availability, or both, depending on the number of messaging engines in the cluster and the policy that is bound to each messaging engine's HAGroup.

If there is only one messaging engine in the cluster and you deploy a destination to the same cluster, the destination is localized by that messaging engine. All messaging workload for that destination are handled by that messaging engine; the workload cannot be shared. The availability characteristics of the destination are the same as the availability characteristics of the messaging engine.

You can benefit from increased scalability by introducing additional messaging engines to the cluster. When you deploy a destination to the cluster, the destination is localized by all the messaging engines in the cluster and the destination becomes partitioned across the messaging engines. The messaging engines share all traffic passing through the destination, which reduces the impact of one messaging engine failing. The availability characteristics of each destination partition are the same as the availability characteristics of the messaging engine that the partition is localized by.

You control the availability behavior of each messaging engine by modifying the core group policy that the HAManager applies to the messaging engine's HAGroup. See Policies for service integration for more information.

Related concepts
Bus topologies
Related tasks
Adding a server as a new bus member
Adding a cluster as a member of a bus
Adding a messaging engine to a cluster

Concept topic

Terms of use | Feedback


Timestamp icon Last updated: 27 November 2008
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.wsfep.multiplatform.doc/concepts/cjt0005_.html

Copyright IBM Corporation 2004, 2008. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)