WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

Match criteria for service integration

You can make a policy bind to a particular messaging engine, or a set of messaging engines, by configuring the match criteria of the policy to match the properties of the HAGroup that you want the policy to manage (in other words, the HAGroup that contains the messaging engine).

The table below lists the names and values of the HAGroup properties for a messaging engine, and the set of matching messaging engines if a property is used in the policy match criteria:
Name Value The messaging engine or engines that the policy will match
type WSAF_SIB Any messaging engine
WSAF_SIB_MESSAGING_ENGINE The name of your messaging engine. This will be in the form node.server-bus for a messaging engine in a server, or cluster.number-bus for a messaging engine in a cluster, where number relates to the order that messaging engines were added to the bus (the messaging engine that is created automatically when you add the cluster to a bus has the number 000). A particular messaging engine
WSAF_SIB_BUS The name of your bus All messaging engines in a particular bus
IBM_hc The name of your cluster All messaging engines in a particular cluster

Using the match criteria you have the ability to associate the policy with all messaging engines, all messaging engines on a named bus, all messaging engines in a particular cluster, or a single messaging engine with a specific name.

The most general policy is the default included with the product, the Default SIBus Policy. This policy has a single match criterion, with Name type and Value WSAF_SIB. This will match any messaging engine that does not have a stronger match to another policy.

For a policy to be assigned to an HAGroup all the policy's criteria must match. You can specify multiple match criteria; the more that match, the stronger the match becomes. The criteria are logically conjoined and are effectively filtering conditions on the set of policies that can match the messaging engine's HAGroup. If a policy has any match criteria that do not match one of the HAGroup properties then the policy cannot match that HAGroup.

For example, you could add a match criterion that requires that the HAGroup has the "WSAF_SIB_BUS"="MyBus" property that would restrict the policy to only match messaging engines on the bus called "MyBus".

Alternatively, you could add a match criterion that requires that the HAGroup has the "WSAF_SIB_MESSAGING_ENGINE"="MyCluster.002-MyBus" property that would restrict the policy to only match the messaging engine with the specified name "MyCluster.002-MyBus".

Be careful that you do not configure a logically impossible combination of criteria. For example if you specified a bus that did not exist, or named a messaging engine that did not exist, the policy would not match any HAGroup.

The use of the "IBM_hc" match criterion is to allow the same policy to be used for resources (not necessarily of the same type) that are in the same server cluster.

Related tasks
Using match criteria to associate a policy with a messaging engine

Concept topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\concepts\cjt0012_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)