Network Deployment (Distributed operating systems), v8.0 > Establishing high availability > Establishing high availability for Service integration > High availability and workload sharing > Configure high availability and workload sharing of service integration > Configure a core group policy for messaging engines
Configure a Static policy for service integration
After you create a new Static core group policy for a messaging engine, you configure the policy to specify which server the messaging engine runs on. Optionally, you can configure the frequency of messaging engine monitoring. A core group policy with the policy type of Static must exist and have first completed the steps in Configure a core group policy for messaging engines. We can use a Static policy to run a messaging engine in either a server or a cluster bus member. A Static policy restricts the messaging engine to a particular server, even in a server cluster. This is useful for a workload sharing configuration, where you want to spread messaging load across multiple servers and failover is not required. We can have multiple messaging engines running in a cluster, with each one restricted to a specific server. Although the Static policy can accept multiple servers, do not configure more than one static group server for use with a messaging engine.
Procedure
- Specify which server the messaging engine will run on:
Optional. If required, enter a value in the Is alive timer field. This value specifies the interval of time, in seconds, at which the high availability manager (HAManager) checks that a messaging engine is running properly. When this value is 0 (zero), the default value of 120 seconds is used.
- Click Static group servers.
- Select the server you require from the Core group servers list, then click Add.
- Ensure that there is only one server in the Static group servers list, then click OK.
- Click OK.
- Save your changes to the master configuration.
Related
CoreGroupPolicyManagement command group