Configure a Static policy for service integration

After creating a new Static core group policy for a messaging engine, you configure the policy to specify which server the messaging engine runs on. Optionally, we can configure the frequency of messaging engine monitoring.

A core group policy with the policy type of Static must exist and you must 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 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.

1. Specify which server the messaging engine will run on:

   1. Click Static group servers.

   2. Select the server you require from the Core group servers list, then click Add.

   3. Ensure that there is only one server in the Static group servers list, then click OK.

2. Optional: If required, enter a value in the Is alive timer field. 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.

3. Click OK.

4. Save the changes to the master configuration.
   

Related

CoreGroupPolicyManagement (AdminTask)