Core Groups and Core Group Policies

To specify a specific Core Group for you Cluster you need to override the default parameter in you .py file and specify the name of the Core Group you wish your Cluster to be a part of, as shown below.

nonDefaultCoreGroup = "true"
coreGroupName = "SIPPECoreGroup"

The scripts will create the Core Group if it doesn�t already exist and once all the members in your cluster have been created, move all the servers in the cluster to the specified Core Group.

Configuring Core Group Policies

To configure a custom Core Group policy to govern your messaging engines or anything else you need to override the default setting for non Default Core Group policies as below.

nonDefaultCGPolicy = "true"

There are five types of Policy which can be configured, OneOfNPolicy, MOfNPolicy, AllActivePolicy, StaticPolicy & NoOpPolicy.

The example below is for a OneOfNPolicy for governing a particular Messaging Engine. The specific Messaging Engine is identified using match criteria which specify the cluster name, bus name, and the ME Name as well as specifying that it is a SIB policy.

It is also possible to specify failback and the preferred servers for the Messaging Engine to failover to, as well as the order in which the ME will fail to different members of a Cluster.

coreGroupPolicyName_1 = "SIPPEBUS_ME000_Policy"
coreGroupPolicyType_1 = "OneOfNPolicy"
coreGroupPolicyDescription_1 = "Messaging Engine Policy"
coreGroupPolicyFailback_1 = "true"
coreGroupPolicyPreferredServersOnly_1 = "true"
coreGroupPolicyMCType_1 = "WSAF_SIB"
coreGroupPolicyMCCluster_1 = clusterName
coreGroupPolicyMCSIBus_1 = "SIPPEBUS"
coreGroupPolicyMCMEName_1 = "SIPPEBUSServerElab01.000-SIPPEBUS"
coreGroupPolicyPreferredServers_1 = ["SIPPEBUSServerElab01_clone1", "SIPPEBUSServerElab01_clone3", "SIPPEBUSServerElab01_clone4", "SIPPEBUSServerElab01_clone2"]