Create a policy for messaging engines
Use the following procedure to create one or more core group policies for service integrationaaag to control the behavior of the messaging engine, or engines, in a server cluster. The policies support behavior such as high availability and workload sharing
As an alternative, we can create a policy using messaging engine policy assistance when we add a server cluster to a bus. Create messaging engines and their associated policies as part of the procedure, and use predefined messaging engine policy types that support frequently-used cluster configurations. Alternatively, we can use a custom policy type and configure the messaging engine policy as you require, and the relevant core group policies and their match criteria are created automatically.
Continue with the following procedure to create a core group policy for messaging engines if we are familiar with it. Otherwise, it is easier to create a policy using messaging engine policy assistance when we add a server cluster to a bus.
Decide what type of core group policy create for the configuration you require. For service integration, the following types of core group policy apply:
Policy Description Static Workload sharing or scalability configuration without high availability. Create one policy for each messaging engine in the cluster. One of N High availability configuration, or a workload sharing configuration with high availability. Create one policy for each messaging engine in the cluster. No operation Use an external high availability framework to manage the messaging engines in the cluster. Create one policy for all the messaging engines in the cluster. The configuration might be high availability, or workload sharing with high availability. For further information, see Policies for service integration.
A policy is a component of a core group. A core group can have a number of different policies; each policy applies to a particular high availability group and determines the high availability behavior of resources in that group. For service integration, the resources to control are the messaging engines. Typically, we create one policy for each messaging engine in the cluster, unless we want the messaging engines to be managed by external high availability framework.
Create a policy for a messaging engine
- In the navigation pane, click...
Servers -> Core groups -> Core group settings -> core_group_name -> [Additional Properties] Policies
A list of currently configured core group policies is displayed.
- Click New.
- Select one of the following options from the Policies list. Only the following policy types are applicable to service integration:
- Static
- A messaging engine cannot fail over in a WebSphere Application Server cluster.
- One of N
- A messaging engine can fail over in a WebSphere Application Server cluster.
- No operation
- A messaging engine is managed by an external high availability framework such as IBM HACMP. This option is for use with an external high availability cluster.
Do not select any other policy type, because they because they are not supported for the service integration bus component.
- Click Next. The policies configuration page is displayed.
- Enter a Name that is unique in the scope of the core group.
- Click Apply or OK.
- Configure the policy.
- Save changes to the master configuration.
Related:
Service integration high availability and workload sharing configurations Policies for service integration Messaging engine policy assistance Add a cluster as a member of a bus Deleting a redundant core group policy Add a cluster to a bus without using messaging engine policy assistance