Create a multi-instance queue manager using an independent ASP and NetServer on IBM i
Create a multi-instance queue manager to run on two IBM i servers. The queue manager data is stored an IBM i server using NetServer. The queue manager journal is
stored on an independent ASP. Use IBM i clustering or
a manual procedure to transfer the independent ASP containing the queue manager journal to the other
IBM i server.
Before starting
The task requires three IBM i servers.
Install IBM MQ on two of them, ALPHA and BETA in the
example. IBM MQ must be at least at version 7.0.1.1.
The third server is an IBM i server,
connected by NetServer to ALPHA and BETA. It is used to share the queue manager data. It does not
have to have an IBM MQ installation. It is useful to
install IBM MQ on the server as a temporary step, to set
up the queue manager directories and permissions.
Make sure that the QMQM user profile has the same password on all three
servers.
Create procedures to transfer the independent ASP from the failed queue manager to the standby
that is taking over. We might find some of the techniques in SupportPac MC41: Configuring
IBM MQ for iSeries for High Availability helpful in designing
your independent ASP transfer procedures.
Perform the following steps to create the configuration shown in Figure 1. The queue manager data is connected using IBM i
NetServer.
Create connections from ALPHA and BETA to the directory share on GAMMA that is to store
the queue manager data. The task also sets up the necessary permissions, user profiles and
passwords.
As a result, ALPHA and BETA have a share, /QNTC/GAMMA/WMQ, that
points to /QIBM/UserData/mqm/qmgrs on GAMMA. The user profiles
QMQM and QMQMADM have the necessary permissions, and
QMQM has matching passwords on all three systems.
Create a queue manager instance of QM1 on BETA using the ADDMQMINF command.
Run the following command on BETA to modify the queue manager control information in
/QIBM/UserData/mqm/mqs.ini on BETA.
The status of the queue manager instance on ALPHA should be *ACTIVE.
The status of the queue manager instance on BETA should be *STANDBY.
Example
Figure 1. Transfer a queue manager journal using an independent ASP
What to do next
Verify that the active and standby instances switch over automatically. We can run
the sample high availability sample programs to test the switch over; see High availability sample programs.
The sample programs are 'C' clients. We can run them from a Windows or Unix platform.
Use NetServer to place the queue manager data on an IBM i server.
Instead of using an independent ASP to transfer the queue manager journal to the standby server,
use remote journaling to mirror the journal onto the standby server.