Core group policies
For a given high availability group, the associated policy determines which members of the group should be made active.
To create or update HA group policies....
Servers | Core Groups | Core group settings | core_group | PoliciesClick 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 an HA 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 you want to change. When the console page...
Core group settings | core_group_name | Policies | policy_name...displays, we can edit the policy properties.
- Name
- Name of the policy.
- Description
- Description of the policy.
- Policy type
- Desired policy type.
Restrictions:
- If setting up a policy for a transaction manager, select One of N as the policy type.
- If setting up a policy for service integration, select One of N, Static, or No operation as the policy type. The default service integration policy uses a One of N policy type.
Following is a list of valid policy types:
- All active
- The HA manager keeps all of the application components that are running on all of the servers in the HA group active at all times.
- M of N
- Similar to the One of N policy. However, it enables you to specify the number (M) of HA 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 HA group. If the number of active servers is set to one, this policy is a match for the One of N policy.
- No operation
- The No operation policy indicates that no HA group members are made active.
- One of N
- Keeps one member of the HA group active at all times. This is used by groups that desire singleton failover. If a failure occurs, the HA manager starts the singleton on another server.
- Static
- Statically define or configure the active members of the HA group.
- Match criteria
- Name-value pairs used to associate policy with an HA group.
These pairs must match attributes contained in the name of an HA group before this policy is associated with that group.
Related concepts
Policies for service integration
Related tasks
Create a policy for an HA group
Set HA and workload sharing of service integration
Set a One of N policy for service integration