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 with Windows on the Domain Controller

How you create a multi-instance broker for a high availability configuration, when Windows is installed on the Domain Controller.

Note: The set of instructions that follows assumes that all machines with brokers are Windows Domain Controllers. To create a multi-instance broker that does not require the host to be a Windows Domain Controller, see Creating a multi-instance broker.

Before you start:

Create the WebSphere® MQ multi-instance queue manager; see Creating the WebSphere MQ multi-instance queue manager.
Create the shared directories that you require for the multi-instance broker; see Creating the shared directories.

A multi-instance broker can be created only by using the mqsicreatebroker command. It is not possible to convert an existing broker to a multi-instance broker by using the mqsichangebroker command, nor is it possible to migrate a broker from a previous release to a Version 9.0 multi-instance broker.

Similarly, a broker instance can be created only by using the mqsiaddbrokerinstance command.

You can configure a multi-instance broker to start as a WebSphere MQ service.

To create a multi-instance broker:

Create a multi-instance broker called MB1 on client node A, by entering the following command:
```
 mqsicreatebroker MB1 –q QM1 –e /SharedLocation/WMB
```
On Windows systems, to run the mqsicreatebroker command you must 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.

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.

For more information, see the mqsicreatebroker command.
Add the details of broker MB1 onto client node B. Do this by using the following command:
```
 mqsiaddbrokerinstance MB1 –e /SharedLocation/WMB
```
For more information, see mqsiaddbrokerinstance command.
Note that the preceding example is for a UNIX system.
Start queue manager MIQM1 so that it is active on client node A.
Start broker MB1 on client node A. Do this by using the following command:
```
mqsistart MB1
```
Start broker MB1 on client node B. Observe that broker MB1 runs in standby mode against the standby queue managerQM1. Do this by using the following command:
```
mqsilist 
```
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.

be13680_.htm |

Last updated Friday, 21 July 2017