Creating a multi-instance broker

1. On the computers that will run the instances of the integration node, configure the required users and groups so that they have access to the directory for the shared file system. For more information about shared directories, see Creating the shared directories.
   • On Linux and UNIX, the uid and gid for mqbrkrs in /etc/password must be the same on each server. For more information, see Creating a shared file system in the WebSphere MQ product documentation.
   • On Windows, create the following users and groups:
     1. A domain group that is a member of the local mqbrkrs on both systems. For example, IIB\Domain mqbrkrs.
     2. A domain user that is a member of the Domain mqbrkrs and mqm groups. This ID is used for running the integration node.
     3. A domain user that 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 integration node. You can use the same ID for both creating and running the integration node, but you do not have to be an Administrator to run the integration node. For example, WMB\mqsiuser-admin. The listed user and groups are using the example domain name IIB.
2. Create a directory for the integration node shared files on the file server.
   • On Linux and UNIX, Create /HA/mqsi on the shared drive. Ensure that /HA/mqsi is owned by the user and group mqbrkrs, and has the access permissions rwx.
     If you are using an NFS v4 file server, add the following line to the /etc/exports file:

     /IBHA * rw,sync,no_wdelay,fsid=0)

     Start the NFS daemon by using the following command:

     /etc/init.d/nfs start

   • On Windows, update the security permissions of the folder:
     1. In Windows Explorer, right-click the shared directory that you created, and select Properties.
     2. Click the Security tab, then click Advanced > Change Permissions...
     3. Clear include inheritable permissions from this objects parent.
     4. In the Permission entries window, select the entries for individual users and then click Remove. Leave the entries for SYSTEM, Administrators, and CREATOR OWNER.
     5. Add mqbrkrs with Full Control. If this folder is also being used for multi-instance queue manager, then the domain group that is used to secure the queue manager must also be added with Full Control set.
     6. Add the global group domain mqm. Click Check Names, and then click OK. If this folder is also being used for multi-instance queue manager, then the domain group that is used to secure the queue manager must also be added with Full Control set.
     7. Remove the default Everyone user from the list.
3. As user mqsiuser-admin, open a command console with elevated privileges.

   On Windows, open a command prompt with elevated privileges by using the mqsicommandconsole command; see mqsicommandconsole command

Create the multi-instance integration node, and then the instances of that integration node for all of the computers that the queue manager runs on.

4. Create a multi-instance integration node on computer A. Use the following command, where IB9NODE is the name of the integration node, and MIQM1 is the name of the existing multi-instance queue manager that was created with the -a or -ar options:

   mqsicreatebroker IB9NODE -i "WMB\mqsiuser" -a <password> -q MIQM1 -e \\MyServer\\mqsishare -B "WMB\Domain mqbrkrs"

   Replace <password> with the mqsiuser-admin password.

   If you want to start the multi-instance integration node as an MQ Service dependency, specify -d as defined on the mqsicreatebroker command. For more information, see mqsicreatebroker command.

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

5. Add the details of integration node IB9NODE onto computer B as an instance of that integration node. Use the mqsiaddbrokerinstance command, in the appropriate format for your operating system. For example, on Linux and UNIX:

   mqsiaddbrokerinstance IB9NODE -i "WMB\mqsiuser" -a <password> -e \\MyServer\\mqsishare

   On Windows:

   mqsiaddbrokerinstance IB9NODE -i "WMB/mqsiuser" -a <password> -e /mqsishare

   For more information, see mqsiaddbrokerinstance command.

   Repeat this step for every computer that the multi-instance queue manager runs on.

6. Start queue manager MIQM1 so that it is active on computer A. See Starting and stopping a multi-instance queue manager in the WebSphere MQ product documentation.
7. Start integration node IB9NODE on computer A. Use the mqsistart command:

   mqsistart IB9NODE

8. Start integration node IB9NODE on computer B. You can observe that integration node IB9NODE is running in standby mode against the standby queue manager QM1 by running the command mqsilist.
9. Optional: Optional: test that the integration node works as follows:
   1. Stop integration node IB9NODE and queue manager QM1 on computer A. Observe on computer B that integration node IB9NODE and queue manager QM1 change from standby to active mode.
   2. Restart queue manager QM1 and integration node IB9NODE on computer A. Observe on computer B that queue manager QM1 and integration node IB9NODE return to standby mode.