IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Creating a multi-instance broker and a multi-instance queue manager

How you create a multi-instance broker and a multi-instance queue manager together for a high availability configuration.

Before you start:

When you create the multi-instance queue manager, use the -ar crtmqm option. Before you can create a multi-instance broker on a single domain, you must configure user and file permissions.

As user mqsiuser-admin, open a command console with elevated privileges by using the mqsicommandconsole command. To create a multi-instance broker and a multi-instance queue manager together, complete the following steps:

  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 group which is a member of the local mqm group on both systems. For example, WMB\Domain mqm
    3. A domain user which is a member of the Domain mqbrkrs and mqm groups. This ID is used for running the broker. For example, WMB\mqsiuser.
    4. 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.The listed user and groups are using the example domain name WMB.
  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".
    4. Add "Domain mqm" with "Full Control".
    5. Remove the default "Everyone" user from the list.
    6. Add "Domain mqbrkrs" with "Full Control".
  4. 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.

    Specify -d defined on the mqsicreatebroker command to start the multi-instance broker as a WebSphere MQ service.

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

    See the mqsicreatebroker command for further information.

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

  6. Start queue manager MIQM1 so that it is active on client node A.
  7. Start broker MB1 on client node A. Do this by using the following command:
    mqsistart MB1
  8. 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 
  9. 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 both a multi-instance broker and 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. When node A becomes active again, it takes on the role of standby node.

be13681_.htm | Last updated Friday, 21 July 2017