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

Configuring a Static policy for service integration

Use this task to continue the configuration of a Static messaging engine policy.

To complete this task you must have first completed the steps in Configuring a policy for messaging engines.
A Static policy can be used to run a messaging engine in either a server or a cluster bus member. The use of a Static policy allows the messaging engine to be restricted to a particular server, even when in a cluster. This can be useful in situations where failover is not wanted. With a Static policy, the messaging engine can run only on one designated server. Although the static policy can accept multiple servers, you should not configure more than one static group server for use with a messaging engine.
  1. Specify which server the messaging engine will run on :
    1. Click Static group servers.
    2. Select one, and only one, server from the left hand pane, and add it to the right hand pane.
    3. Ensure you have only one server in the right hand pane, then click OK.
  2. 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 default is 120 seconds.
  3. Click OK.
  4. 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\tjt0038_.html

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