WebSphere WebSphere Enterprise Service Bus, Version 6.0.1 Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Multiple-server enterprise service bus with clustering

A deployment manager cell can be used for an enterprise service bus that consists of multiple servers, some or all of which are members of server clusters.

Why and when to perform this task

A server that hosts queue destinations for SCA modules has one messaging engine in the SCA.SYSTEM bus. For many purposes this is sufficient, but such a messaging engine can only run in the server it was created for. The server is therefore a single point of failure; if the server cannot run, the messaging engine is unavailable. By configuring a server cluster as a bus member instead, the messaging engine has the ability to run in one server in the cluster, and if that server fails, the messaging engine can run in an alternative server. This is illustrated in Figure 1.

Another advantage of configuring a cluster bus member is the ability to share the workload associated with an SCA module across multiple servers. For an SCA module deployed to a cluster bus member, the queue destinations used are partitioned across the set of messaging engines run by the cluster servers. The messaging engines in the cluster each handle a share of the messages passing through the SCA module.

To summarize, with a cluster bus member you can achieve either failover, workload sharing, or both, depending on policies that you can configure.

Figure 1. A multiple-server bus with clustered servers for failover
A SCA.SYSTEM bus with a server cluster as its only bus member. The figure illustrates the scenario where a messaging engine has the ability to run in one server in the cluster, and if that server fails, the messaging engine can run in an alternative server.
Figure 2. A multiple-server bus with clustered servers for workload sharing
An SCA.SYSTEM bus with a service cluster as its only bus member. The figure illustrates the scenario where each server in the cluster runs a messaging engine. Each bus destination is partitioned across the messaging engines running in the cluster member.

There are several different ways to create a multiple-server enterprise service bus:

Alternatives for this task

What to do next

You can now run the WebSphere ESB samples and deploy service applications into your enterprise service bus.
Related concepts
Server clusters
Service integration high availability and workload sharing configurations
Bus member types and their effect on high availability and workload sharing configuration
An enterprise service bus with links to WebSphere MQ networks
Related tasks
Balancing workloads with server clusters
Planning WebSphere ESB installation scenarios

Task topic

Terms of Use | Rate this page

Timestamp iconLast updated: 13 Dec 2005
http://publib.boulder.ibm.com/infocenter/dmndhelp/v6rxmx/index.jsp?topic=/com.ibm.websphere.wesb.doc\tasks\tjj0072_.html

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