Modifying the messaging engine policy for a cluster bus member

You 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.

Before you begin

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.

About this task

Use this procedure when you 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

  1. 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.
  2. If messaging engine policy assistance is not enabled, click Enable policy assistance and follow the instructions on the wizard.
  3. 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.
  4. 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 your 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.

  5. If necessary, save your 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.



In this information ...


Related information

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jan 30, 2014 9:17:32 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-iseries&topic=tjj1004_
File name: tjj1004_.html