WebSphere WebSphere Application Server Version 6.1.x Feature Pack for Web Services Operating Systems: AIX, HP-UX, i5/OS, Linux, Solaris, Windows, z/OS

Configuring high availability and workload sharing of service integration

You can configure high availability and workload sharing of service integration.

About 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. To do this, 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 usse unless you configure the system so that the engine uses another policy. The default policy is sufficient for many purposes and you might not need to alter the policy configuration. It is not advisable to alter the default policy, because those changes will affect all messaging engines that are managed by the policy. For this reason, it is better to create and configure a new specific policy.

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

Procedure

  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.
    • If you do not need a cluster, create a server and add it to your service integration bus. A messaging engine is created automatically. You do not need to alter the configuration of core group policies to manage the messaging engine; the defaults are sufficient.
    • If you need a cluster, create a cluster by using the topic Creating clusters, and add it to your service integration bus. This creates a single messaging engine that uses the default messaging engine policy. If you want high availability and not workload sharing, no further configuration is needed, unless you want to specify particular characteristics of how this messaging engine should be managed, as described in step 3.
  2. Optional: For workload sharing, add as many messaging engines as you require to the cluster.
  3. Optional: To customize the way that messaging engines are managed, create and configure a policy for the messaging engines. It is not advisable to change the default policy, because those changes will affect all messaging engines that are 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 also describes how to associate the policy with one or more messaging engines.

Related concepts
Service integration high availability and workload sharing configurations
Workload sharing configuration
Highly available messaging engine configuration
Automate peer recovery for transactions and messages in WebSphere Application Server

Task topic

Terms of use | Feedback


Timestamp icon Last updated: 27 November 2008
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.pmc.wsfep.multiplatform.doc/tasks/tjt0023_.html

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