The following procedure gives an overview
of how you create a multi-instance
WebSphere MQ queue
manager. See
Creating a multi-instance queue manager for more information.
- Create a multi-instance WebSphere MQ queue
manager called QM1 on client node A. You do this by using the following command:
-crtmqm -md /SharedLocation/WMQ/data
-ld /SharedLocation/WMQ/logs QM1
where:
- md
- Is the name of the directory used to hold data files for a queue
manager.
- ld
- Is the name of the directory used to hold log files.
Note that it is important that the name of the
queue manager goes at the end of the syntax. See the WebSphere MQ documentation for further information
on the crtmqm command.
- Add the details of WebSphere MQ queue
manager QM1 onto client node B. You do this by using the following command:
-addmqinf -v Name=QM1 -v Directory=WMQ -v Prefix=/var/mqm
-v DataPath=/SharedLocation/WMQ/data/QM1
where:
- Name
- Is the name of the queue manager.
- Directory
- Is the name of the queue manager data directory.
- Prefix
- Is the directory path under which this queue manager data
directory is stored by default.
- Data Path
- Is the data path where the queue manager data files are placed.
The value of Directory is not appended automatically
to this path; you must provide the transformed queue manager name
as part of DataPath.
The parameters listed above are all required
parameters on Windows and UNIX platforms, with the exception
of DataPath, which is optional on UNIX platforms only.
See the WebSphere MQ documentation for further information
on the addmqinf command.
- Start queue manager QM1 on client node A in
multi-instance mode. You do this by using the following
command:
strmqm -x QM1
See the WebSphere MQ documentation for further information
on the strmqm command.
- Observe the queue manager running in active mode. You
do this by using the following command:
dspmq -x
See
the WebSphere MQ documentation for further
information on the dspmq command.
- Start queue manager QM1 on client node B. Observe the queue manager running in standby mode.
- Ensure that queue manager QM1 works
as follows when simulating a failover from node A to
node B:
- Stop queue manager QM1 on client node A. You do this by using the following command:
endmqm -s QM1
Observe
on client node B, queue manager QM1 running
in active mode, and on client node A that queue manager QM1 is
now stopped.
- Restart queue manager QM1 on client
node A. You do this by using the following
command:
strmqm -x QM1
Observe on client node
A, queue manager QM1 running in standby mode, and
on client node B, queue manager QM1 running in active
mode.
Last updated Friday, 21 July 2017