Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Service integration > Administer service integration buses > Configure buses > Configure the members of a bus
Modify the messaging engine policy for a cluster bus member
We can change the messaging engine policy for a cluster bus member that is already configured, and change the number of messaging engines and their behavior so that they conform with the new messaging engine policy. If you modify the messaging engine policy to provide a high availability configuration, the cluster should contain at least two nodes, each with a server on, that is, at least two physical machines.
Use this procedure when we have already added a server cluster as a member of a bus and configured its messaging engines, and you now want to change the configuration. For example, if a cluster is configured for high availability, there is one messaging engine for the cluster and it is set to fail over to any other server in the cluster.
To change the cluster to provide scalability, you need one messaging engine for each server, set so that each messaging engine cannot fail over. Messaging engine policy assistance guides you through this process by providing messages about the changes required to achieve the required configuration.
Procedure
- In the navigation pane, click Service integration -> Buses -> bus_name -> [Topology] Bus members -> bus_member_name . If messaging engine policy assistance is enabled, the Bus member detail pane is displayed. If messaging engine policy assistance is not enabled, the Messaging engine collection pane is displayed.
- If messaging engine policy assistance is not enabled, click Enable policy assistance and follow the instructions on the wizard.
- From the Bus member detail pane, select one of the following messaging engine policy types, then click Apply:
- High availability
- Scalability
- Scalability with high availability
If these policy types do not satisfy your requirements, is possible to select Custom and create your own configuration. If you do this, the system cannot generate any advice or warning messages.
- Examine the resulting diagram and the messages for the selected messaging engine policy type. Act on the messages as follows:
- To add a server or a node, go back and change the cluster topology before you continue with the current procedure.
- To add or remove messaging engines, under Additional Properties, click Messaging engines and use the options on the resulting pane.
- To correct messaging engine policies, under Additional Properties, click Messaging engine policy maintenance and use the options on the resulting pane.
At each stage, save changes to the master configuration. If the Bus members collection pane is displayed, click the cluster name to return to the Bus member detail pane.
When the "Is further configuration required" column for the selected messaging engine policy type displays No, the configuration is complete.
- If necessary, save changes to the master configuration.
Results
The cluster has the number of messaging engines that are required to conform to your selected messaging engine policy type. Any changes to the core group policies associated with the messaging engines are made automatically.
Messaging engine policy assistance
High availability messaging engine policy
Scalability messaging engine policy
Scalability with high availability messaging engine policy
Add a cluster as a member of a bus
Add a messaging engine to a cluster
Remove a messaging engine from a cluster
Correcting the messaging engine policy
Delete a redundant core group policy
Related
modifySIBusMemberPolicy command
correctSIBEnginePolicy command
createMissingSIBEnginePolicy command
Bus members [Settings]