![[IBM MQ Advanced]](ngadv.gif)
Installing RDQM (replicated data queue managers)
Installation tasks associated with RDQM are grouped in this section. RDQM is available on x86-64 for RHEL 8 (8.8 or later) and RHEL 9 (9.2 or later).
Before you begin
RDQM requires that the mqm user has the same UID on each node and that the
mqm group has the same GID on each node. You should create the mqm
IDs before running the installation procedure, using the groupadd and
useradd commands to set the UID and GID the same on each node. See Setting up the user and group on Linux.
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 8 and RHEL 9 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.
- cifs-utils
- libtool-ltdl
- libxslt
- net-snmp-libs
- nfs-utils
- perl-TimeDate
- psmisc
- python36
- python3-lxml
- libxslt
- net-snmp-libs
- nfs-utils
- nfs-utils-coreos
- perl-TimeDate
- python3-lxml
- python-unversioned-command
- selinux-policy
- selinux-policy-base
- rpm-plugin-selinux
- selinux-policy-targeted
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.
hacluster and a group
named haclient. By default, these use a uid and gid of 189, although it is possible
to specify a different uid and gid if required. The installation of Pacemaker creates the user and
group if they do not exist. About this task
- 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. You should install the versions supplied with IBM MQ. Do not download your own versions, and you should ensure that the install does not pick up any other versions of these packages that you already have on your system.
To ensure that the packages supplied with RDQM are used, add exclude lines to the definition of any yum repository that could supply alternatives, such as the AppStream repository in RHEL 8. The exclude line needs to be applied to any yum repository defined on the system that could supply the standard RHEL alternative to any of the packages supplied with IBM MQ.
exclude=cluster* corosync* drbd kmod-drbd libqb* pacemaker* resource-agents* ktls-utils* For
example, for RHEL 9 use the following exclude
line:exclude=cluster* corosync* crm* libknet* libnozzle* libqb* pacemaker* python3-parallax* resource-agents* ktls-utils* For supported levels of RHEL 8, components are found under the Advanced/RDQM/PreReqs/el8/ directory. For supported levels of RHEL 9, components are found under the Advanced/RDQM/PreReqs/el9/ directory.
modprobe: ERROR: could not insert 'drbd': Required key not available- Download the linbit-keyring package for your operating system version from https://packages.linbit.com/public/linbit-keyring/.
- Issue the following command to install the linbit-keyring package:
rpm -i linbit-keyring.rpm - Issue the following command to import the LINBIT signing key:
rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-linbit
Without this step, an RPM install of these packages issues the following warnings:
warning: rpm-name: Header V4 RSA/SHA512 Signature, key ID b826fe48: NOKEYYou can have multiple IBM MQ installations on each server, but only one of these installations should be an RDQM installation (see Installing RDQM alongside other IBM MQ installations). You can install the IBM MQ components in a custom location, if required, see Installing RDQM to a non-default location.
Procedure
Complete the following steps on each node: