Service integration high availability and workload sharing configurations

The configuration of service integration is very flexible. You can have a single messaging engine that does not provide high availability or workload sharing. With a cluster bus member, you can have a single highly available messaging engine. Alternatively, with a cluster bus member, you can have multiple messaging engines that share workload, or that share workload and also provide high availability.

The configurations that are possible depend on the type of bus member you create. You create a bus member by adding either a server or a cluster to a bus. If you create a server bus member, you can create only a simple configuration. If you create a cluster bus member, you can create any of the configurations in the previous list, depending on the number of messaging engines in the cluster and the behavior of those messaging engines. For more details, see Bus member types and their effect on high availability and workload sharing configuration.

For details and examples of the configurations you can create, see the subtopics.

Configuring messaging engine behavior

After you create a bus member, you configure a policy to control the availability behavior of the messaging engine on that bus member.

For more information about policies and configuration, see Policies for service integration.

With the options just described, it is possible to achieve high availability, workload sharing, or both. The following table shows how you can achieve different configurations. See the related links for some examples of what you can configure.
Table 1. Service integration configurations
Configuration Type of bus member Number of messaging engines Policy type
Simple Server 1 Default ("One of N")
Simple Cluster 1 Static
High availability Cluster 1 "One of N" or "No operation"
Workload sharing without high availability Cluster more than 1 (typically, one messaging engine for each server) Static
High availability and workload sharing Cluster more than 1 (typically, one messaging engine for each server) "One of N" or "No operation"



Subtopics
Bus member types and their effect on high availability and workload sharing configuration
Simple configuration without workload sharing or high availability
Configuration for workload sharing or scalability
Configuration for high availability
Configuration for workload sharing with high availability
Policies for service integration
Related concepts
WebSphere Application Server high availability
Multiple-server bus with clustering
Learning about high availability and workload sharing
Related tasks
Configuring high availability and workload sharing of service integration
Creating a policy for messaging engines
Configuring a policy for messaging engines
Using match criteria to associate a policy with a messaging engine
Configuring a Static policy for service integration
Configuring a "One of N" policy for service integration
Configuring a "No operation" policy for service integration
Configuring shared durable subscriptions
Configuring a policy for messaging engines using scripting
Related information
Core group policy settings
Match criteria settings
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=cjt0007_
File name: cjt0007_.html