Configuring A Multi-Instance Message Broker For High Availability Support

Product documentation


Abstract

WebSphere Message Broker V7.0 introduces software High Availability support as an alternative to using HACMP

This note provides a general description of the feature along with additional information and corrections to the V7.0 documentation

Content

General Description of High Availability Software Support:

High availability (HA) is a protocol and associated implementation that ensures a certain degree of operational continuity when unplanned downtime events impact parts of a system. WebSphere Message Broker has supported, and been supported by, high availability technologies such as IBM’s HACMP, but the HA marketplace has now changed to accommodate solutions that have a lower price-of-entry. These solutions rely entirely on software, as opposed to traditional reliance on shared disk hardware, custom network links, and similar resources.

WebSphere MQSeries V7.0.1 includes software HA, and WebSphere Message Broker follows suit in Version 7.0, with the multi-instance broker building upon the capabilities of the multi-instance queue manager solution, as shown in Figure 1 below.

For this scenario, a multi-instance broker is created using the mqsicreatebroker command, with an additional -e option that specifies the location in shared network storage (see Figure 1) of the broker registry and other configuration data. Additional instances of the broker can then be created on other machines in the network using a new command called mqsiaddbrokerinstance, using the -e option to target the same location in shared network storage. Broker logging, error handling and shared Java Classes remain local to the machine that hosts the broker or broker instance. For a description of how the failover is managed for a multi-instance broker please see below.




User Tasks:
  • Restrictions on creating a multi-instance broker or broker instance:
    A multi-instance broker can be created only by using the mqsicreatebroker command. It is not possible to convert an existing broker that is not multi-instance to a multi-instance broker by using the mqsichangebroker command. Nor is it possible to migrate a broker from a previous release to a V7.0 multi-instance broker. Similarly a broker instance can be created only by using the mqsiaddbrokerinstance command.

  • Mapping IDs across the servers :
    Before creating multi-instance queue managers or multi-instance brokers, ensure that the numeric ID for the users and groups that create and run the brokers and queue managers are matched across the servers in the network.


  • Removal of a multi-instance message broker and broker instances:
    The order of deletion of a multi-instance message broker and its associated instances is important, so be careful to use the correct command for each step in the cleanup process.

    1) Run the mqsiremovebrokerinstance command to remove all the broker instances before you try to remove the broker itself. This command removes all local references to the broker instance, but does not affect the shared configuration for the multi-instance broker on the shared work path (which was specified by using the -e option on the mqsicreatebroker and mqsiaddbrokerinstance commands). You cannot use the mqsiremovebrokerinstance command against a standby broker instance.

    2) Run the mqsideletebroker command to remove the multi-instance broker. This removes all references to the broker on both the local and shared work paths. You cannot use this command against a standby broker instance.

    If you mistakenly remove a broker instance, you can recreate it by running the mqsiaddbrokerinstance command, provided that you have not yet run the mqsideletebroker command to delete the broker itself.

    If the multi-instance broker is removed by running the mqsideletebroker command before removing the associated broker instances, then it will no longer be possible to start the broker instances. To recover from this situation you can recreate the multi-instance broker by running the mqsicreatebroker command, using the -e option to specify the original shared work path location.


Topics in the WebSphere MQSeries Information Center that relate to configuring a multi-instance message broker :

Take the following points into consideration when setting up the multi-instance queue manager for a multi-instance broker to run on it.
.
In a Windows environment :
  • When configuring a multi-instance queue manager, the userid creating the queue manager must be part of the domain mqm group. For more details please refer to the following topics in the WebSphere MQSeries Information Center:

http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.amqtac.doc/wq10840_.htm

and

http://publib.boulder.ibm.com/infocenter/wmqv7/v7r0/index.jsp?topic=/com.ibm.mq.amq1ac.doc/lq10740_.htm

  • The machines hosting the multi-instance queue manger and queue manager instances need to be Windows domain controllers.
  • WebSphere MQSeries APAR IC64521 resolves a problem when the endmqm command is used to stop an active instance of the queue manager, and thereby in turn the standby instance too, some queue manager processes do not stop cleanly on the standby instance, so you need to stop them manually.

Original publication date

2009/11/17

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Message Broker
Broker

Software version:

7.0

Operating system(s):

AIX, HP-UX, Linux, Linux SUSE - zSeries, Solaris, Windows

Software edition:

All Editions

Reference #:

7017319

Modified date:

2010-08-02

Translate my page

Machine Translation

Content navigation