Create a multi-instance queue manager
Create a multi-instance queue manager, creating the queue manager on one server, and configuring IBM® WebSphere® MQ on another server. Multi-instance queue managers shared queue manager data and logs.
- Create the shares for the data and log files.
- Create the queue manager on one server.
- Run the command dspmqinf on the first server to collect the queue manager configuration data and copy it into the clipboard.
- Run the command addmqinf with the copied data to create the queue manager configuration on the second server.
File access control
You need to take care
that the user and group mqm
on all other servers
have permission to access the shares.
On UNIX and Linux, you need
to make the uid
and gid
of mqm
the same on all the systems. You might need to edit /etc/passwd on each system to set a common uid
and gid
for mqm
, and then reboot
your system.
- Create a queue manager with a global group as the alternative security principal. Authorize the global group to have full control access to the directories containing queue manager data and log files; see Secure shared queue manager data and log directories and files on Windows. Make the user ID that is running the queue manager a member of the global group. You cannot make a local user a member of a global group, so the queue manager processes must run under a domain user ID. The domain user ID must be a member of the local group mqm. The task, Create a multi-instance queue manager on domain workstations or servers, demonstrates how to set up a multi-instance queue manager using files secured in this way.
- Create a queue manager on the domain controller, so that the local mqm group has domain scope,
domain local
. Secure the file share with the domain local mqm, and run queue manager processes on all instances of a queue manager under the same domain local mqm group. The task, Create a multi-instance queue manager on domain controllers, demonstrates how to set up a multi-instance queue manager using files secured in this way.
Configuration information
Configure as many queue manager instances as you need by modifying the IBM WebSphere MQ queue manager configuration information about each server. Each server must have the same version of IBM WebSphere MQ installed at a compatible fix level. The commands, dspmqinf and addmqinf assist you to configure the additional queue manager instances. Alternatively, you can edit the mqs.ini and qm.ini files directly. The topics, Create a multi-instance queue manager on Linux, Create a multi-instance queue manager on domain workstations or servers, and Create a multi-instance queue manager on domain controllers are examples showing how to configure a multi-instance queue manager.
On Windows, UNIX and Linux systems, you can share a single mqs.ini file by placing it on the network share and setting the AMQ_MQS_INI_LOCATION environment variable to point to it.
Restrictions
- Configure multiple instances of the same queue manager only on servers having the same operating system, architecture and endianness. For example, both machines must be either 32-bit or 64-bit.
- All IBM WebSphere MQ installations must be at release level 7.0.1 or higher.
- Typically, active and standby installations are maintained at
the same maintenance level. Consult the maintenance instructions for
each upgrade to check whether you must upgrade all installations together.
Note that the maintenance levels for the active and passive queue managers must be identical.
Share queue manager data and logs only between queue managers that are configured with the same IBM WebSphere MQ user, group, and access control mechanism.
- On UNIX and Linux systems, configure the shared file system on networked storage with a hard, interruptible, mount rather than a soft mount. A hard interruptible mount forces the queue manager to hang until it is interrupted by a system call. Soft mounts do not guarantee data consistency after a server failure.
- The shared log and data directories cannot be stored on a FAT, or an NFSv3 file system. For multi-instance queue managers on Windows, the networked storage must be accessed by the Common Internet File System (CIFS) protocol used by Windows networks.