WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Service integration high availability and workload sharing configurations

The configuration of service integration is very flexible. You can have individual messaging engines, or clusters containing multiple messaging engines that can share workload, be highly available, or both.

The type of bus member you create affects the options you have available to you. You create a bus member by adding either a server or a cluster to a bus. Creating a server bus member creates a single messaging engine. For many purposes this is sufficient, but such a messaging engine is a single point of failure and cannot share workload.

If you want to avoid a single point of failure by allowing failover, or if destinations need to be partitioned (to allow sharing of the messaging workload), use a cluster bus member. With a cluster bus member you can achieve either failover, workload sharing or both, depending on the policy you configure for a messaging engine. See Bus member types and their effect on high availability and workload sharing configuration for more information about server and cluster bus members.

Once you have created a bus member, you configure a policy to control the availability behavior of the messaging engine on that bus member. If you want high availability, use a cluster bus member and the default policy (One of N), which will allow the messaging engine to failover. You can customize your policy to specify other availability behavior, such as a preference for particular servers.

If you want workload sharing but not high availability, use a cluster bus member and create a Static policy for each messaging engine. This could be useful for scalable express messaging, in which there is no persistent state associated with any one messaging engine so no failover is required.

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

With the options provided above it is possible to achieve either failover, workload sharing, or both. The following table shows how you can achieve different configurations. See the links below for some for examples of what you can configure.
  Workload sharing
  No Yes
Highly available No Simple configuration
  • Bus member type = server
  • Number of messaging engines = 1
  • Policy = Static or One of N
  • OR
  • Bus member type = cluster
  • Number of messaging engines = 1
  • Policy = Static
Workload sharing configuration
  • Bus member type = cluster
  • Number of messaging engines = more than 1
  • Policy = Static
Yes Highly available messaging engine configuration
  • Bus member type = cluster
  • Number of messaging engines = 1
  • Policy = One of N or 'No operation'
Highly available messaging engines with workload sharing configuration
  • Bus member type = cluster
  • Number of messaging engines = more than 1
  • Policy = One of N or 'No operation'

Sub-topics

Related concepts
WebSphere Application Server high availability
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

Concept topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\concepts\cjt0007_.html

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