Specifying a preferred server for messaging requests
If a core group includes a cluster of application servers, and a messaging engine is configured for that cluster, any of the servers in that cluster can handle work items for the messaging engine. The default message provider that is included in the product is based on Service Integration Bus (SIB) technology, and is governed by the Default SIBus policy, which is a One of N policy. This policy ensures that only one of the application servers in the cluster is active at a time). You can modify the high availability group policy to specify that a specific cluster member handles the messaging work.
Before you begin
- You should review the following topics:
- You must determine:
- The name of the core group that includes the server that you want to handle messaging requests.
- The name of the high availability group for the messaging function.
- The name of the policy that is associated with this high availability group
- You must create a new policy specific to the high availability
group that controls the messaging engine cluster, if one does not
already exist.
It is possible for a single policy to govern several different high availability groups. Therefore, to modify the policy for cluster scoped control, you must create a new policy specific to the high availability group that controls the messaging engine cluster. See Creating a policy for a high availability group for more information on how to create this policy.
After you create the new policy and associate the policy with the high availability group for a given cluster, You can specify a preferred server for messaging requestws..