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

When you add a server to a service integration bus, you create a server bus member and a single messaging engine that does not have any workload sharing or high availability characteristics. When you add a cluster to a service integration bus, you create a cluster bus member and a single messaging engine that has high availability characteristics. You can configure the cluster to provide high availability, workload sharing, or both.

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, because 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 high availability, workload sharing, or both, depending on the number of messaging engines in the cluster and the policy that is bound to each messaging engine's HAGroup.

When you add a cluster to a bus, a single messaging engine is created that is active on only one server in the cluster. If the server or messaging engine fails, the messaging engine becomes active on another server in the cluster, if one is available, thus providing high availability.

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 is 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.

By default, there is no workload management or scalability because there is only a single messaging engine active for the cluster. To achieve greater throughput of messages, you can spread the messaging load across multiple servers and, optionally, across multiple hosts. You can achieve this, while maintaining a simple destination model, by creating additional messaging engines for the cluster, each of which has a preference to run on a separate server in 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
Workload sharing with queue destinations
Service integration high availability and workload sharing configurations
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
Configuring high availability and workload sharing of service integration
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=cjt0005_
File name: cjt0005_.html