WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Using a broker with an existing Windows Cluster (Windows Server 2003 or 2008)

You can use WebSphere® Message Broker with the existing high availability manager for Windows Server 2003 (Microsoft Cluster Service - MSCS) or Windows Server 2008 (Failover Cluster Manager).

With the introduction of multi-instance brokers in WebSphere Message Broker Version 7.0, configuring WebSphere Message Broker with a high availability (HA) manager is much easier. Before WebSphere Message Broker Version 8.0, support pack IC91 was provided to assist in configuring this requirement.

A number of scripts were provided in support pack IC91, but most of these scripts are no longer required because WebSphere Message Broker has built-in many of the functions as a result of the multi-instance work.

This topic summarizes how to complete the following tasks:
  1. Complete the prerequisite setup.
  2. Configure a local group.
  3. Create a broker.
  4. Add broker instances to the additional nodes.
  5. Add the broker service to the cluster configuration
  6. Start and stop a broker.
  7. Delete a broker.
  1. To complete the prerequisite setup, complete the following steps:
    1. Validate your MSCS configuration (on Windows Server 2003) or Failover Cluster Manager configuration (on Windows Server 2008).
    2. Complete all of the steps documented in 'Supporting the Microsoft Cluster Service' of the WebSphere MQ documentation to create a cluster configuration that contains the queue manager on which you want the broker to run.
    3. Note the haregtyp.exe command as a prerequisite for creating WebSphere MQ resources in the cluster.
  2. To configure a local group, ensure that the domain user under which you want the broker to run exists in the local mqbrkrs group on all nodes on which you want the broker to run.
  3. To create a broker, use the following mqsicreatebroker command on the node on which your cluster is currently running.
     mqsicreatebroker MyBroker -q MQ1 -e E:\Broker\Workspace
    where:
    • MyBroker is the name of the broker.
    • MQ1 is the name of the queue manager.
    • E:\Broker\Workspace is the directory of a shared disk (nonquorum) in your cluster configuration.
  4. To add this broker instance to the other nodes in your cluster, switch your cluster to each node in turn. When a node is active, use the following mqsiaddbrokerinstance command.
     mqsiaddbrokerinstance MyBroker –e E:\Broker\Workspace
    where:
    • MyBroker is the name of the broker.
    • E:\Broker\Workspace is the directory of a shared disk (nonquorum) in your cluster configuration.
  5. To add a broker generic service resource to the cluster which contains the broker queue manager, complete the following steps:
    1. Select the IBM® WebSphere Message Broker component MyBroker service when asked. All other settings can be left unchanged.
    2. Add a dependency on the WebSphere MQ resource, to ensure that the queue manager is started before the broker.
  6. To start and stop the broker resource, use the MSCS configuration (on Windows Server 2003) or Failover Cluster Manager (on Windows Server 2008).
  7. To delete a broker resource from the MSCS configuration (on Windows Server 2003) or Failover Cluster Manager (on Windows Server 2008), take the following steps:
    1. Delete the broker generic service from the cluster configuration.
    2. Use the mqsiremovebrokerinstance command on all nodes but one, moving the cluster between nodes before running each command.
    3. On the final node, use the mqsideletebroker command to completely remove the broker configuration.

For further information about configuring WebSphere MQ with a high availability manager for Windows Server, see the WebSphere MQ Version 7 Information Center online.

See the following topics:
  • Introducing MSCS clusters
  • Supporting the Microsoft Cluster Service (MSCS)
  • Setting up WebSphere MQ for MSCS clustering
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:06


Task topicTask topic | Version 8.0.0.7 | be13800_