Core group policies
Create or update the various high availability group policies. For a given high availability group, the associated policy determines which members of the group should be made active.
From the admin console, click...
- Servers > Core Groups > Core group settings > core group> Policies
Click New to define a new policy. After a policy is defined there are several fields that we can no longer change. To change those fields, delete and redefine the policy. Click Delete after selecting a policy to delete the selected policy.
After adding a high availability group, we need to take more actions to enable workload balancing for messaging resources.
All of the policy fields on this page are read-only. To change the values specified in any of these fields, click on the name of the policy we want to change. When the console page Core group settings > core_group_name > Policies > policy_name displays, and we can edit the policy properties.
Name
Name of the policy.
Description
Description of the policy.
Policy type
If we are setting up a policy for a transaction manager, we must select One of N as the policy type. If we are setting up a policy for service integration, we must select One of N, Static, or No operation as the policy type. The default service integration policy uses a One of N policy type.
Valid policy types
- All active
- The high availability manager keeps all of the application components running on all of the servers in the high availability group active at all times.
- M of N
- Similar to the One of N policy. However, it enables us to specify the number (M) of high availability group members to keep active if it is possible to do so. The number of active members must be greater than one and less than or equal to the number of servers in the high availability group. If the number of active servers is set to one, this policy is a match for the One of N policy.
- No operation
- No high availability group members are made active.
- One of N
- Keep one member of the high availability group active at all times. This is used by groups that desire singleton failover. If a failure occurs, the high availability manager starts the singleton on another server.
- Static
- Statically define or configure the active members of the high availability group.
Match criteria
One or more name-value pairs used to associate this policy with a high availability group. These pairs must match attributes contained in the name of a high availability group before this policy is associated with that group.
Related: