Core group policies
Use this page to 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. To view this console page, click Servers > Core Groups > Core group settings > New, or select an existing core group, and then click 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. For more information about the extra actions, see the Related tasks.
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 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
Specifies a description of the policy.
Policy type
Desired policy type.
Restrictions:
- If we are setting up a policy for a transaction manager, you must select One of N as the policy type.
- If we are setting up a policy for service integration, you 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.
Following is a list of valid policy types:
- All active
- The All active policy indicates that the high availability manager keeps all of the application components that are running on all of the servers in the high availability group active at all times.
- M of N
- The M of N policy is similar to the One of N policy. However, it enables you 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
- The No operation policy indicates that no high availability group members are made active.
- One of N
- The One of N policy keeps 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
- The Static policy allows us to statically define or configure the active members of the high availability group.
Match criteria
Specifies 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 concepts
Policies for service integration
Related tasks
Configure high availability and workload sharing of service integration Configure a One of N policy for service integration