WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Creating a multi-instance queue manager

Create a multi-instance queue manager by creating the queue manager on one server, and configuring WebSphere® MQ on another server to use the shared queue manager data and logs.

Most of the work of setting up a multi-instance queue manager involves setting up the network storage that holds the queue manager data and log files, and making the files available to other servers using network shares. These tasks need to be performed by someone with administrative authority, such as root on UNIX systems. Once the shares are set up, and a normal queue manager has been created using the shares for its queue manager data and logs, you only need to configure WebSphere MQ on the other servers. You do not create the queue manager again on the other servers.

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 platforms, 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, then reboot your UNIX systems.

On Microsoft Windows, you must install WebSphere MQ on a domain server, and create a user to own WebSphere MQ resources. The user must either be a member of domain group mqm or a member of another global domain group which is directly or indirectly a member of mqm. Make this user the owner of the shared queue manager and log files. The sid of the user who owns the queue manager and log files is then the same as the sid of the user that runs instances of the queue manager.

Configuration information

Configure as many queue manager instances as you need by modifying the WebSphere MQ configuration information about each server that has WebSphere MQ installed and is to run a queue manager instance. The commands, dspmqinf and addmqinf help you to configure the additional queue manager instances, or you can edit the mqs.ini file on UNIX servers directly. The topics, Create a multi-instance queue manager on Linux and Create a multi-instance queue manager on Windows Server are examples showing how to configure a multi-instance queue manager.

On UNIX 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.

On Microsoft Windows, WebSphere MQ has for a number of releases kept its configuration information in the Windows registry. As from Version 7.0.1, some configuration information has moved from the registry into configuration files.

Multi-instance queue manager configuration is moved out of the registry into qm.ini and qmstatus.ini files, which are located in the queue manager data directory. The WebSphere MQ configuration information (mqs.ini on UNIX platforms) remains in the registry on Windows as does all the configuration information for existing queue managers and new queue managers that are configured to use the default data directory.

Restrictions

  1. Configure multiple instances of the same queue manager only on servers having the same operating system, architecture (both machines having 32-bit or 64-bit word size, for example), and endian settings.
  2. All WebSphere MQ installations must be at Version 7.0.1 (or later).
  3. Typically active and standby installations are maintained at the same maintenance level. Consult the maintenance instructions for each upgrade to check if you must upgrade all installations together.
  4. The network share that contains queue manager data and logs can only be shared between queue managers that are configured with the same WebSphere MQ user, group, and access control mechanism. For example, the network share set up on a Linux server could contain separate queue manager data and logs for AIX®, Solaris, HP-UX, and Linux queue managers.

  5. On UNIX 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 crash.
  6. On Microsoft Windows, the domain group mqm must have full access to shared WebSphere MQ log and data directories.
  7. The shared log and data directories cannot be stored on a FAT, or an NFSv3 file system.
  8. z/OS® does not support multi-instance queue managers; use queue sharing groups.
  9. Multi-instance queue managers are supported only on the platform on which they are created.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:48:34


Concept topicConcept topic | Version 8.0.0.7 | fa70159_