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

Configuring high availability and workload sharing of service integration

Use this task to configure high availability and workload sharing of service integration.

Why and when to perform this task

Setting up a service integration environment involves the creation of bus members, either servers or clusters, that run messaging engines. The high availability and workload sharing characteristics of the messaging engines are dictated by core group policies.

To see the policies that are configured in your system use the administrative console to open the Policies page: in the navigation pane click Servers > Core groups > Core group settings > core_group_name [Content Pane] > Configuration > Policies [Additional Properties]. In the set of available policies you will see the default service integration policy, "Default SIBus Policy", which is the policy that a messaging engine will use unless you configure the system so that the engine uses another policy. The default policy is sufficient for many purposes and you may not need to alter the policy configuration. Indeed it is recommended that you do not change the default policy, as those changes will affect all messaging engines being managed by the policy. Instead you should create and configure a specific policy.

To determine what you need to configure, and how to configure it, use the following steps:

Steps for this task

  1. Decide whether you want multiple messaging engines to share the load on a destination and whether you want your messaging engine to be able to failover. If you want either of these capabilities you will need a cluster, otherwise you can use a server. For more information, see Service integration high availability and workload sharing configurations.
  2. If you do not need a cluster then simply create a server and add it to your service integration bus. A messaging engine will be created for you automatically. You do not need to alter the configuration of core group policies to manage the messaging engine; the defaults are sufficient.
  3. If you do need a cluster, then create a cluster by using the topic Creating clusters, and add it to your service integration bus. This creates a single messaging engine which will use the default messaging engine policy. If you want high availability and not workload sharing then there is no further configuration needed, unless you want to specify particular characteristics of how this messaging engine should be managed, as described in step 5.
  4. If you want workload sharing then you need to add as many messaging engines as you require to the cluster.
  5. If you want to customize the way that messaging engines are managed, create and configure a policy for the messaging engines. It is recommended that you do not change the default policy, as those changes will affect all messaging engines being managed by the default policy.
    1. Create a policy by following the steps in Creating a policy for messaging engines.
    2. Configure the attributes of the policy by following the steps in Configuring a policy for messaging engines.

      These attributes include the frequency of messaging engine monitoring, whether a messaging engine has a preferred server, which servers are preferred, and whether the messaging engine should automatically fail back to its preferred server whenever possible. This task includes instructions on how to associate the policy with a particular messaging engine or messaging engines.

Sub-topics
Related concepts
Service integration high availability and workload sharing configurations
Highly available messaging engine configuration
Related tasks
Adding a cluster as a member of a bus

Task topic

Terms of Use | Feedback

Last updated: 15 Mar 2007
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\tasks\tjt0023_.html

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