Configuring a policy for messaging engines using scripting

You can use a script that is provided with the application server to create and configure the core group policies for messaging engines. The core group policies that the script creates define the behavior of request processing across the cluster, for example, to provide workload management or high availability.

Before you begin

You need to know the name of the service integration bus, and the messaging engine or engines in the cluster.

For high availability without workload sharing, you can use the default configuration that is created when you add a cluster as a member of a bus and you do not need to configure the policy further.

About this task

You configure a core group policy for service integration to associate the policy with a specific messaging engine and to specify messaging engine behavior, such as which server a messaging engine runs on, whether a messaging engine can fail over or fail back, and the frequency of messaging engine monitoring.

The CreateCoreGroupPolicy.jacl script creates a core group policy and assigns that policy to the required messaging engine and server in the cluster, using a properties file to specify the required behavior. You create a properties file for each messaging engine in the cluster, then run the script against each properties file.

To set up workload management in a cluster, each server in the cluster must be able to process messages locally. To do this, you create additional messaging engines in the cluster so that autonomous message processing can occur. Typically, you create one messaging engine for each server in the cluster. You also need a core group policy for each messaging engine to specify which server the messaging engine runs on, and restrict the messaging engine to that server.

For high availability when you want messaging engine behavior that the default configuration does not provide, you need to create and configure a suitable core group policy for the messaging engine.

For high availability with workload sharing, you create additional messaging engines in the cluster, typically one messaging engine for each server in the cluster. You need a core group policy for each messaging engine to specify which server the messaging engine runs on, and which servers the messaging engine can fail over to.

For the example properties files in the following procedure, the script creates core group policies that assign each messaging engine to an individual server in the cluster and restrict the messaging engine to that server, thus providing a workload management configuration.

The CreateCoreGroupPolicy.jacl script is in the ${WAS_INSTALL_ROOT}/bin directory.

Procedure

  1. On the machine that hosts the deployment manager, create a properties file for each messaging engine in the cluster. Use the following file as an example:
     CoreGroupName=DefaultCoreGroup	
    	PolicyName=<policyName>	# Name of the core group policy.
    	PolicyType=OneOfNPolicy	
    	IsAlivePeriodSec=0
    	Failback=false	
    	QuorumEnabled=false
    	PreferredOnly=true
    	NumOfMatchCriteria=3
    	Name_0=type
    	Value_0=WSAF_SIB
    	Name_1=WSAF_BUS
    	Value_1=<busName>	# Name of the service integration bus.
    	Name_2=WSAF_SIB_MESSAGING_ENGINE
    	Value_2=<meName>	# Name of the messaging engine being assigned.
    	NumOfPolicyServers=1
    	NodeName=<nodeName>	# The node for the server.
    	ServerName=<serverName>	# The server being assigned to.
    For example, for a cluster of three servers where you require one messaging engine for each server, create the following three properties files:
     CoreGroupName=DefaultCoreGroup	
    	PolicyName=ME0	
    	PolicyType=OneOfNPolicy	
    	IsAlivePeriodSec=0
    	Failback=false	
    	QuorumEnabled=false
    	PreferredOnly=true
    	NumOfMatchCriteria=3
    	Name_0=type
    	Value_0=WSAF_SIB
    	Name_1=WSAF_BUS
    	Value1=Bus1
    	Name_2=WSAF_SIB_MESSAGING_ENGINE
    	Value_2=was-cluster-1.000-Bus1	
    	NumOfPolicyServers=1
    	NodeName=Node1	
    	ServerName=Server1 
     CoreGroupName=DefaultCoreGroup	
    	PolicyName=ME1	
    	PolicyType=OneOfNPolicy	
    	IsAlivePeriodSec=0
    	Failback=false	
    	QuorumEnabled=false
    	PreferredOnly=true
    	NumOfMatchCriteria=3
    	Name_0=type
    	Value_0=WSAF_SIB
    	Name_1=WSAF_BUS
    	Value1=Bus1
    	Name_2=WSAF_SIB_MESSAGING_ENGINE
    	Value_2=was-cluster-1.001-Bus1	
    	NumOfPolicyServers=1
    	NodeName=Node1	
    	ServerName=Server2
     CoreGroupName=DefaultCoreGroup	
    	PolicyName=ME2	
    	PolicyType=OneOfNPolicy	
    	IsAlivePeriodSec=0
    	Failback=false	
    	QuorumEnabled=false
    	PreferredOnly=true
    	NumOfMatchCriteria=3
    	Name_0=type
    	Value_0=WSAF_SIB
    	Name_1=WSAF_BUS
    	Value1=Bus1
    	Name_2=WSAF_SIB_MESSAGING_ENGINE
    	Value_2=was-cluster-1.002-Bus1
    	NumOfPolicyServers=1
    	NodeName=Node1	
    	ServerName=Server3
    For more information about the parameters in the properties file, see the information about core group policy settings and match criteria settings.
  2. For each properties file, run the CreateCoreGroupPolicy.jacl script, supplying the path to the properties file as an argument. [Windows]
    ${WAS_INSTALL_ROOT}/bin/wsadmin.bat 
    	-conntype SOAP 
    	-f ${WAS_INSTALL_ROOT}/bin/CreateCoreGroupPolicy.jacl 
    	properties_file_path
    [AIX] [HP-UX] [Linux] [Solaris] [z/OS]
    ${WAS_INSTALL_ROOT}/bin/wsadmin.sh 
    	-conntype SOAP 
    	-f ${WAS_INSTALL_ROOT}/bin/CreateCoreGroupPolicy.jacl 
    	properties_file_path

Results

For each properties file, a core group policy is created and configured.



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 1:23:07 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-dist&topic=tjt0029_
File name: tjt0029_.html