Migrate an integration node to a multi-instance integration
node by moving the queue manager data to a shared directory, and
reconfiguring the integration node on two other servers.
Before you begin
Multi-instance integration nodes require a multi-instance queue manager. You must first
check the prerequisites for running a multi-instance queue manager, and migrate your queue manager
if it is single-instance. For more information, see Migrating from a single instance to
a multi-instance queue manager in the IBM® MQ product documentation.
For the latest
information about tested environments, see Testing statement for IBM MQ multi-instance queue manager file
systems. This support statement contains detailed version and prerequisite information for each
environment. A test tool is provided with IBM MQ to assist you in
testing unsupported environments.
You must provide three servers to run a multi-instance
integration node, which provide the following functions:
- A shared file system to store the integration node data and logs.
- Active instances of the integration node.
- Standby instances of the integration node
For more information, see Create a multi-instance queue manager in the IBM MQ product documentation.
Procedure
On the servers that will run the active and standby instances
of the integration node, configure the required users and groups
so that they have access to a shared directory on the network
file system.
- On Windows, create
the following users and groups:
- A domain group that is a member of the local mqbrkrs group on
both servers. For example, WMB\Domain mqbrkrs
- A domain group that is a member of the local mqm group
on both servers. For example, WMB\Domain mqm
- A domain user that is a member of the domain mqbrkrs and
mqm groups. This ID is used for running the integration node. For example,
WMB\mqsiuser
- A domain user that is a member of the domain mqbrkrs group
and a member of the local administrators group on both machines.
For example, WMB\mqsiuser-admin. This
ID is used for creating the integration node. It can be the
same as the previous ID, but you do not have to run the integration
node as an administrator.
- On UNIX and Linux®, the uid and gid for mqbrkrs in
/etc/password must be the same on each server. For more information, see Creating a shared file
system in the IBM MQ product documentation.
Create a shared directory on the network file system
with the correct access permissions. A typical configuration consists
of a single shared directory that contains all data for all integration
nodes that use the shared file system. Each integration node creates
its own data directories under the shared directory.
- On Windows, create
a directory on the file server for the files shared by the integration
node, for example, C:\mqsishare. Update
the security permissions of the directory by completing the following
steps:
- In Windows Explorer,
right-click the shared directory that you have just created
and select Properties.
- Click the Security tab, then
click
- Clear the "Include inheritable permissions from this
object's parent" checkbox.
- In the Permission entries window, select the entries
for individual users and click Remove.
Leave the entries for SYSTEM, Administrators, and CREATOR OWNER.
- Click Add..., and then enter
the name of the global group domain mqm.
Click Check Names and click OK.
- In the Permission Entry window,
select the Allow checkbox for the Full
Control entry.
- Repeat the previous two steps for the global group domain
mqbrkrs.
- In the Properties window, click
the Sharing tab and then click Advanced
Sharing. Select the Share this folder checkbox,
and leave the share name as mqsishare.
Click Permissions.
- Click Add, and enter the name
of the global group domain mqbrkrs.
Click Check Names.
- In the Group or user names panel,
select the domain mqbrkrs. Select the
Allow checkbox for the Full
Control entry, and then click Apply.
- Repeat the previous two steps for the global group Administrators.
- In the Group or user names panel,
remove the group Everyone.
- On Linux and UNIX, complete the following steps:
- Create /HA/mqsi on the shared drive.
Ensure that /HA/mqsi is owned by the user and group
mqbrkrs, and has the access permissions
rwx.
- If you are using an NFS v4 file server, add the following line to the
/etc/exports
file:
/IBHA * rw,sync,no_wdelay,fsid=0)
Start the NFS daemon by
using the following command:
/etc/init.d/nfs start
Copying the integration node data to the share is a manual
procedure. Before you continue, ensure that you have backed up
your integration node. For more information, see Backing up the integration node.
- Stop the integration node.
Move the IBM App Connect Enterprise configuration
directories.
- On Windows, run the
following commands:
mkdir \\<server_name>\mqsishare\mqsi\
where <server_name> is the name of your
server.
xcopy /e /i /q /z C:\ProgramData\IBM\MQSI\components\<int_node_name> \\<server_name>\mqsishare\mqsi\components\<int_node_name>
where <int_node_name> is the name of
your integration node.
xcopy /e /i /q /z C:\ProgramData\IBM\MQSI\registry\<int_node_name> \\<server_name>\mqsishare\mqsi\registry\<int_node_name>
rmdir C:\ProgramData\IBM\MQSI\components\<int_node_name> /q
/s
rmdir C:\ProgramData\IBM\MQSI\registry\<int_node_name> /q
/s
- On Linux and UNIX,
run the following commands:
mkdir -p /HA/mqsi/components/
mkdir -p /HA/mqsi/registry/
mv
/var/mqsi/components/<int_node_name>\
/HA/mqsi/components/
mv
/var/mqsi/registry/<int_node_name>\
/HA/mqsi/registry/
Create a file called HASharedWorkPath that
contains the location of the new shared directory and place it
with the integration nodes registry directory. The file must
not contain any newline characters.
- On Windows, run the
following commands:
mkdir C:\ProgramData\IBM\MQSI\registry\<int_node_name>
<nul set /p =\\<server_name>\mqsishare\mqsi>
C:\ProgramData\IBM\MQSI\registry\<int_node_name>\HASharedWorkPath.dat
- On Linux and UNIX,
run the following commands:
mkdir
/var/mqsi/registry/<int_node_name>
chmod 770
/var/mqsi/registry/<int_node_name>
echo –n /HA/mqsi>
/var/mqsi/registry/<int_node_name>/HASharedWorkPath
On the standby server, add the standby instance
using mqsiaddbrokerinstance.
For more information, see mqsiaddbrokerinstance command.
- Configure the standby integration node:
- On Windows, run
the following command:
mqsiaddbrokerinstance <int_node_name> -i
<user_name> -a <password> -e
\\<server_name>\mqsishare
- On Linux and UNIX,
run the following command:
mqsiaddbrokerinstance
<int_node_name> -e /HA/
- On the active server, run the following command:
mqsistart <int_node_name>
- On the standby server, run the following command:
mqsistart <int_node_name>
Results
Your single-instance integration node has been converted
to a multi-instance integration node. You can verify this by using
the mqsilist command.
See mqsilist command.