Installing RDQM (replicated data queue managers)
Installation tasks associated with RDQM are grouped in this section. RDQM is available on RHEL 7.6 and onwards on x86-64, and on RHEL 8.2 and onwards on x86-64.
Before starting
Pacemaker is one of the prerequisites for RDQM. Pacemaker requires that certain Linux packages are installed on the system. The list for supported levels of RHEL 7 assumes that a minimal set of system packages has been installed that includes of all the mandatory and default packages from the @core package group and mandatory packages from the @base package group. The list for supported levels of RHEL 8 assumes that a minimal set of system packages has been installed that includes the mandatory and default packages from the mandatory groups of the Server environment group.
The prerequisites for supported levels of RHEL 7 (Pacemaker 1) are:
- cifs-utils
- gnutls
- libcgroup
- libtool-ltdl
- lvm2
- net-snmp-libs
- nfs-utils
- perl-TimeDate
- psmisc
- PyYAML
The prerequisites for supported levels of RHEL 8 (Pacemaker 2) are:
- cifs-utils
- libxslt
- net-snmp-libs
- nfs-utils
- perl-TimeDate
- psmisc
- python3-lxml
- python36
These packages in turn have their own requirements (which are not listed here). When Pacemaker is installed, it reports any missing packages that also need to be installed before installation can complete successfully.
To install support for RDQM (replicated data queue managers), you complete the following tasks:
- Install DRBD on each node.
- Install Pacemaker on each node.
- Install IBM MQ on each node.
- Install RDQM on each node.
The DRBD and Pacemaker RPM packages are supplied on the IBM MQ media. We should install the versions supplied with IBM MQ. Do not download your own versions. For supported levels of RHEL 7, the components are found under the Advanced/RDQM/PreReqs/el7/ directory. For supported levels of RHEL 8, components are found under the Advanced/RDQM/PreReqs/el8/ directory.
The DRBD and Pacemaker packages are signed with the LINBIT GPG key. Use the following command to import the public LINBIT GPG key:rpm --import https://packages.linbit.com/package-signing-pubkey.ascWithout this step, an RPM install of these packages issues the following warnings:
warning: rpm-name: Header V4 DSA/SHA1 Signature, key ID 282b6e23: NOKEY"You can have multiple IBM MQ installations on each server, but only one of these installations should be an RDQM installation.
Attention: We should retain the installation media, in case there is a need to revert to this level, after upgrading to a later level.
Procedure
Complete the following steps on each node:
- Log in as root, or switch to the superuser using the su command.
- Change into the directory containing the installation image.
- Determine which DRBD kernel module is needed for the system on which RDQM is being installed. See https://ibm.biz/mqrdqmkernelmods for up-to-date kernel module information. Helper scripts are provided in the kmod-drbd-9 directories. For example, on a RHEL 8.2 system, running the helper script Advanced/RDQM/PreReqs/el8/kmod-drbd-9/modver returns the following information, identifying the kernel module that we need to install:
kmod-drbd-9.0.23_4.18.0_193-1.x86_64.rpm- Install the appropriate DRBD kernel module that you identified in step 1. For example, for RHEL 8.2 you run the following command:
yum install Advanced/RDQM/PreReqs/el8/kmod-drbd-9/kmod-drbd-9.0.23_4.18.0_193-1.x86_64.rpm- Install the required DRBD utilities. For example, for RHEL 8.2 you run the following command:
yum install Advanced/RDQM/PreReqs/el8/drbd-utils-9/*- Install Pacemaker. For example, for RHEL 8.2 you run the following command:
yum install Advanced/RDQM/PreReqs/el8/pacemaker-2/*The Pacemaker installer reports any missing packages that also need to be installed before the install can complete successfully.- Accept the IBM MQ license:
./mqlicense.sh- Install IBM MQ. This is like a standard IBM MQ install. At the minimum, we must install the following:
yum install MQSeriesGSKit* MQSeriesServer* MQSeriesRuntime*- Install RDQM:
yum install Advanced/RDQM/MQSeriesRDQM*
What to do next
We can now configure the Pacemaker cluster and replicated data queue managers, or we can configure disaster recovery replicated data queue managers. See RDQM high availability or RDQM disaster recovery.
- Uninstalling RDQM (replicated data queue managers) if no longer required
How to uninstall RDQM if it is no longer required.- Uninstalling RDQM (replicated data queue managers) and upgrading
How to uninstall RDQM in preparation for upgrading IBM MQ and RDQM.- Installing RDQM alongside other IBM MQ installations
We can install RDQM alongside other installations of IBM MQ although there can only be one RDQM installation.- Applying maintenance level updates for RDQM
There are different procedures for applying maintenance level updates to a high availability (HA) configuration, a disaster recovery (DR) configuration, or a combined DR/HA configuration.- Removing maintenance level updates for RDQM
There are different procedures for removing maintenance level updates to a high availability (HA) configuration, a disaster recovery (DR) configuration, or a combined DR/HA configuration.- Applying OS updates with RDQM
RDQM uses a DRBD kernel module which must be compatible with the current OS kernel level.Parent topic: Installing IBM MQ Advanced for Multiplatforms
Related information