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

Configuring a 'No operation' policy for service integration

Use this task to continue the configuration of a 'No operation' messaging engine policy.

To complete this task you must have first completed the steps in Configuring a policy for messaging engines.
A 'No operation' policy allows an external HA cluster to control when and where a messaging engine runs.
  1. Associate the messaging engine with an externally managed resource group by creating an HA cluster resource for it. Refer to the documentation for your external HA product.
  2. Write scripts for the external HA framework to enable it to use the HAManager to start or stop the messaging engine. The scripts invoke operations on the HAManager MBean on the server that is taking ownership of the resource that represents the messaging engine.
  3. Ensure that the messaging engine can always reach its data store. If the messaging engine is configured to be able to failover then its data store must be accessible from any server in the cluster on which it may run. The set of possible servers depends on how you have configured the external HA resource group. A typical configuration is to include the data store as an additional resource in the resource group managed by the external HA cluster. The HA cluster will then ensure that the data store and the messaging engine failover together and remain collocated after the failover. Whether this is the case or whether a network server is used to make the data store available, the data store must be accessible from any server that may run the messaging engine.
  4. If the messaging engine needs to always be accessible using the same IP address, for example because it is the receiving end of a WebSphere MQ link, then you need to arrange for that IP address to remain collocated with the messaging engine. You can achieve this by creating an IP address resource in the same external HA resource group as the resource representing the messaging engine.
  5. If required, alter the isAlive health monitoring interval. This determines the frequency with which the HAManager checks that a messaging engine is running properly. The 'No Operation' policy is primarily intended for when an external high availability framework, such as IBM HACMP, is being used, in which case it is most likely that you will want to create a monitoring script that is called periodically by the external framework. If you set the isAlive interval to a value greater than or equal to 0, the HAManager will perform health monitoring and your external monitoring script can retrieve the state from the HAManager MBean. Alternatively, you could set the isAlive interval to -1 to disable monitoring by the HAManager, and your external monitoring script can retrieve the state from the messaging engine MBean.
  6. Click OK.
  7. Save your changes to the master configuration.
Related concepts
Service integration high availability and workload sharing configurations

Task 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\tasks\tjt0031_.html

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