Configuring high availability and workload sharing of service integration
You can configure high availability and workload sharing of service integration without using messaging engine policy assistance.
Before you begin
About this task
When you set up a service integration environment, you create bus members, either servers or clusters, that run messaging engines. For high availability, where the messaging engine can fail over, or workload sharing, where multiple messaging engines share the load on a destination, you need to create a cluster bus member and configure high availability and workload sharing characteristics of the messaging engines.
If you do not require high availability or workload sharing, you can use a simple configuration and create a server bus member. You do not need the steps described in this topic.
The high availability and workload sharing characteristics of the messaging engines in the cluster are set by core group policies.
To see the policies that are configured in your system, you can use the administrative console to open the Policies page. In the navigation pane, click .
One of the available policies is the default service integration policy, Default SIBus Policy, which is the policy that a messaging engine uses 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 service integration policy, because those changes will affect all messaging engines that the policy manages. Therefore, it is better to create and configure one or more new specific policies.
Procedure
What to do next
If you created a workload sharing configuration, you might want to deploy a queue destination to the cluster, so that the queue is partitioned across the set of messaging engines.