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

Create a multi-instance queue manager on Windows Server

An example shows how to set up an example multi-instance queue manager on Windows Server. The setup is small and simple, to demonstrate the concepts involved, rather than being production scale. The steps might differ, depending on the version of Windows Server.

Before you begin

On Windows, multi-instance queue managers must run on a domain controller. For this reason, and for this example, install two Windows servers, and configure them as domain controllers in the same domain.

The example was set up on a 2 GHz notebook computer with 3 GB RAM running Windows. Two VMware virtual machines ran Windows Server in 500 MB images. A WebSphere® MQ client was installed on an additional 400 MB VMware image that ran Windows to run the sample high availability applications. All the virtual machines were configured as part of a VMware host-only network for security reasons. Although it is recommended not to use automatically generated IP address, for a short demonstration it is satisfactory as the IP addresses ought not to change. As part of the configuration you need to update the TCP/IP properties of the virtual machines with the address of the domain server you have chosen to be the DNS server.

If you configure a queue manager to run as a service, you need to check that the user the service logs on as is a member of the local group mqm.

Example

Table 1. Illustrative multi-instance queue manager configuration on Windows Server
Server 1 Server 2
Log in with user who is a member of the local group mqm.
Create log and data directories in a folder on an NTFS drive, c:\MQHA, making sure that the owner is a member of mqm, and mqm has full-control authority to the folders.
C:\MQHA\data
C:\MQHA\log
 
Create a share MQHA for C:\MQHA. Connect to \\hostname\MQHA
Using WebSphere MQ Explorer, create a queue manager, QM1, overriding the default paths to the data and log folders and use UNC names to refer to the data and log folders. \\hostname\MQHA\data and \\hostname\MQHA\log.  
On a command-line run,
dspmqinf -o command QM1
and copy the result to the clip board,
addmqinf -s QueueManager
 -v Name=QM1
 -v Directory=QM1
 -v Prefix="C:\IBM\MQ\Data"
 -v DataPath="\\hostname\MQHA\data\QM1"
Paste and run the command,
addmqinf -s QueueManager 
-v Name=QM1 
-v Directory=QM1 
-v Prefix="C:\IBM\MQ\Data" 
-v  DataPath="\\hostname\MQHA\data\QM1"
Using WebSphere MQ Explorer, start the manager instances with the Permit a standby instance check box selected.

fa70161_.htm | Last updated Friday, 21 July 2017