Installing an IBM MQ client on Linux using rpm

Installing an IBM® MQ client on a 64 bit Linux® system.

1. Log in as root, or with sufficient authority to run the following commands.

   You can do this by adding sudo before the commands, or by changing to the root user in the shell with the su command. For more information, see Exploring the differences between sudo and su commands in Linux.

2. Set your current directory to the location of the installation packages.

   The location might be the mount point of a DVD, a network location, or a local file system directory. See Where to find downloadable installation images.

3. From IBM MQ 9.2.0, you have the option of accepting the license before or after installing the product. To accept the license before installing, run the mqlicense.sh script:

   ./mqlicense.sh

   The license agreement is displayed in a language appropriate to your environment and you are prompted to accept or decline the terms of the license.

   If possible, mqlicense.sh opens an X-window to display the license.

   If you need the license to be presented as text in the current shell, which can be read by a screen reader, type the following command:

   ./mqlicense.sh -text_only 

   See License acceptance on IBM MQ for Linux for more information about license acceptance.
4. If you have multiple installations on this system, you must run crtmqpkg to create a unique set of packages to install on the system:
   1. Enter the following command:

      
      ./crtmqpkg suffix
      

      where suffix is a name of your choosing, that will uniquely identify the installation packages on the system. suffix is not the same as an installation name, although the names can be identical. suffix is limited to 16 characters in the ranges A-Z, a-z, and 0-9.
   2. Set your current directory to the location specified when the crtmqpkg command completes.
      This directory is a sub-directory of /var/tmp/mq_rpms, in which the unique set of packages is created. The packages have the suffix value contained within the filename.
5. Optional: Obtain the IBM MQ public signing gpg key and install it into rpm.

   rpm --import ibm_mq_public.pgp

   The IBM-provided RPMs are signed with a digital signature, and your system will not recognize that signature without further steps. This only needs to be done once for each system. For more information, see IBM MQ code signatures.

   The validity of any of the IBM MQ RPMs can then be verified, for example:

   # rpm -Kv MQSeriesRuntime-9.2.4-0.x86_64.rpm
   MQSeriesRuntime-9.2.4-0.x86_64.rpm:
       Header V3 RSA/SHA256 Signature, key ID 0209b828: OK
       Header SHA1 digest: OK
       V3 RSA/SHA256 Signature, key ID 0209b828: OK
       MD5 digest: OK
   

   Note: If you skip this step, then a harmless warning might be issued during RPM installation to indicate there is a signature but the system does not recognize the signing key, for example:

   warning: MQSeriesRuntime-9.2.4-0.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 0209b828: NOKEY

6. Install IBM MQ.
   The minimum components you must install are the MQSeriesRuntime, the MQSeriesClient, and the MQSeriesGSKit.
   • To install to the default location, /opt/mqm, use the rpm -ivh command to install each component that you require.
     For example, to install all components to the default location use the following command:

     
     rpm -ivh MQSeries*.rpm
     

     If you are using Ubuntu, add the --force-debian attribute. For example, to install all components to the default location use the following command:

     
     rpm --force-debian -ivh MQSeries*.rpm
     

     You must include this option to prevent seeing warning messages from the version of RPM for your platform, which indicates that the RPM packages are not intended to be directly installed using RPM.
   • To install to a non-default location use the rpm --prefix option. For each installation, all of the IBM MQ components that you require must be installed in the same location.

     The installation path specified must either be an empty directory, the root of an unused file system, or a path that does not exist. The length of the path is limited to 256 bytes and must not contain spaces.

     For example, to install the runtime and server components to /opt/customLocation on a 64-bit Linux system:

     
     rpm --prefix /opt/customLocation -ivh MQSeriesRuntime-V.R.M-F.x86_64.rpm MQSeriesClient-V.R.M-F.x86_64.rpm
     

     where:

     V

     Represents the version of the product that you are installing

     R

     Represents the release of the product that you are installing

     M

     Represents the modification of the product that you are installing

     F

     Represents the fix pack level of the product that you are installing