Using match criteria to associate a policy with a messaging engine

You configure match criteria in a policy definition to associate that core group policy with a messaging engine, or group of messaging engines. The match criteria of the policy need to match the properties of the high availability group (HAGroup) that you want the policy to manage, that is, the HAGroup that contains the required messaging engines.

Before you begin

To associate a policy with a messaging engine, or group of messaging engines, you must have created a suitable policy. To associate a policy with a messaging engine, you must know the name of the messaging engine, and preferably, the name of the bus and the cluster in which the messaging engine runs. To associate a policy with a group of messaging engines, you must know the name of the bus or the cluster in which the messaging engines run.

Decide on the match criteria that you want to set. For more information about match criteria for messaging engines, see Match criteria for service integration.

About this task

Each messaging engine is managed by an HAGroup to which a policy is assigned at run time. The policy assigned to an HAGroup is chosen by comparing the match criteria of the set of configured policies with the properties of the HAGroup. The policy with the strongest match is assigned to the HAGroup.

Typically, for a policy of type Static or "One of N", you associate the policy with a single messaging engine. Typically, for a policy of type "No operation", you associate the policy with all the messaging engines (one or more) in a cluster.

Procedure

  1. Open the match criteria page for your policy by clicking Servers > Core groups > Core group settings > core_group_name > [Additional Properties] Policies > policy_name > [Additional Properties] Match criteria .
  2. Repeat the following steps to create enough match criteria to create a strong match for the policy:
    1. Click New.
    2. Enter a suitable Name and Value to specify a messaging engine, or group of messaging engines, that will match this policy. Valid values for the Name are:
      • type
      • WSAF_SIB_BUS
      • IBM_hc
      • WSAF_SIB_MESSAGING_ENGINE

      For more information about finding the correct names for match criteria, see the topic about core group settings.

    3. Click OK.
    It is advisable to add as many match criteria as possible to make the match strong, and to restrict the HAGroups that the policy can match. For example, to associate a policy with a specific messaging engine in a cluster, specify all the following match criteria:
    Name Value
    type WSAF_SIB
    WSAF_SIB_BUS bus_name
    IBM_hc cluster_name
    WSAF_SIB_MESSAGING_ENGINE messaging_engine_name

    You must specify at least two match criteria to ensure that the policy creates a stronger match than the match that the "Default SIBus Policy" creates. For example, to associate a policy with a specific messaging engine, you must specify at least type=WSAF_SIB and WSAF_SIB_MESSAGING_ENGINE=messaging_engine_name.

  3. Save your changes to the master configuration.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=tjt0035_
File name: tjt0035_.html