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

Creating a multi-instance broker

How you create a multi-instance broker using an existing multi-instance queue manager for a high availability configuration.

Note: The set of instructions that follows assumes that the multi-instance queue manager exists. To create a multi-instance broker and multi-instance queue manager together, see Creating a multi-instance broker and a multi-instance queue manager.
Before you start:

Create the WebSphere® MQ multi-instance queue manager.

The queue manager must be created with the “-a” or “-ar” flag on crtmqm, specifying a domain group that WMQ can use for securing shared files. If you have the option, use the “-ar” flag. The “-ar” flag is available when using WebSphere MQ Version 7.1.

For more information, see Creating the WebSphere MQ multi-instance queue manager.

You do not require a Windows installation on the domain controllers to use these instructions. To use an existing queue manager to create a multi-instance broker:

  1. Create the shared directories that you require for the multi-instance broker. For more information about shared directories, see Creating the shared directories
  2. Define the following user and groups:
    1. A domain group which is a member of the local mqbrkrs on both systems. For example, WMB\Domain mqbrkrs
    2. A domain user which is a member of the Domain mqbrkrs group. This ID is used for running the broker. For example, WMB\mqsiuser.
    3. A domain user which is a member of the Domain mqbrkrs group and a member of the local Administrators group on both machines. This ID is used for creating the broker. It can be the same as the previous ID, but it is not necessary to run the broker as an Administrator. For example, WMB\mqsiuser-admin.
  3. Create a folder for the broker shared files on the file server, c:\mqsishare. Update the security permissions of the folder, using the change permissions section of the Advanced Security Settings panel:
    1. Clear "include inheritable permissions from this objects parent".
    2. Remove all of the existing entries.
    3. Add "Domain mqbrkrs" with "Full Control". If this folder is also being used for multi-instance queue manager, then the domain group used to secure the queue manager must also be added with “Full Control” as well. Use the advanced sharing options to share this folder.
    4. Remove the default "Everyone" user from the list.
    5. Add "Domain mqbrkrs" with "Full Control".
    6. Optional: If this share is also being used for the multi-instance queue manager, then the domain group used to secure the queue manager must also be added with “Full Control” as well.
  4. As user mqsiuser-admin, open a command console with elevated privileges. To open a command console with elevated privileges, use the mqsicommandconsole command. For more information, see mqsicommandconsole command
  5. Create a multi-instance broker called MB1 on client node A. Do this by using the following command:
     mqsicreatebroker MIMB1 -i "WMB\mqsiuser" -a <password> –q MIQM1 –e \\MyServer\\mqsishare -B "WMB\Domain mqbrkrs"

    Where MIQM1 is the name of the existing multi-instance queue manager created with the -a or -ar flags as mentioned in the above code. Replace <password> with the mqsiuser-admin password. If you want to start the multi-instance broker as a WebSphere MQ service, you can specify -d defined on the mqsicreatebroker command.

    You must ensure that the SharedLocation exists, and that your user ID has access to the shared location before you run this command.

    See mqsicreatebroker command for further information.

  6. Add the details of broker MB1 onto client node B. Do this by using the following command:
     mqsiaddbrokerinstance MIMB1 -i "WMB\mqsiuser" -a <password> –e \\MyServer\\mqsishare
    See mqsiaddbrokerinstance command for further information.

    Note that the preceding example is for a UNIX system.

  7. Start queue manager MIQM1 so that it is active on client node A.
  8. Start broker MB1 on client node A. Do this by using the following command:
    mqsistart MB1
  9. Start broker MB1 on client node B. Observe that broker MB1 is running in standby mode against the standby queue managerQM1. Do this by using the following command:
    mqsilist 
  10. Optional: Ensure that broker MB1 works as follows:
    1. Stop broker MB1 and queue manager QM1 on client node A. Observe on client node B that broker MB1 and queue manager QM1 change from standby to active mode.
    2. Restart queue manager QM1 and broker MB1 on client node A. Observe on client node B that queue manager QM1 and broker MB1 return to standby mode.
You have created a multi-instance broker using an existing multi-instance queue manager. When broker MB1 and queue manager QM1 stop on client node A, the same broker and queue manager on client node B become active, and return to standby when client node A becomes active again.
Notices | Trademarks | Downloads | Library | Support | Feedback

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

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


Task topicTask topic | Version 8.0.0.7 | be13682_