Installing on Linux

 

Overview

The WebSphere MQ client is installed in /opt/mqm. You cannot change this directory, but there are ways to get around this stricture if you do not have enough space.

The following components are available:

Runtime Support for applications. Install before you install the Client component.
Client Client code
SDK Required for application development.
Sample programs Sample application programs that are needed if you want to verify that the WebSphere MQ client has been installed correctly.
Java messaging WebSphere MQ classes for Java and WebSphere MQ classes for JMS. Lots of useful programs. Recommended to install.
Message catalogs In US English. Installed automatically.
IBM Global Security Kit (GSKit) V6 Required SSL support. Contains the key management tool, iKeyman.
WebSphere MQ support for iKeyman Required for SSL support. Install after installing GSKit V6.

 

Create the file systems

The components are installed in /opt/mqm and working data is stored in /var/mqm. You cannot change these directories.

 

Create a file system for the components

Typical disk space requirements are as follows:

  • Without the SSL support: 27 MB
  • With the SSL support: 100 MB

If you do not have enough space to store the components in the /opt/mqm file system, you can do either of the following:

  • Create a new file system and mount it as /opt/mqm.

  • Create a new directory anywhere on your machine, and create a symbolic link from /opt/mqm to this new directory. For example: 
    mkdir /bigdisk/mqm
ln -s /bigdisk/mqm /opt/mqm

The file system for the components can be a remote network device, using NFS, for example. However, the mount options defined on that device must allow setuid programs, including root access, to run.

 

Creating a file system for the working data

Before you install the WebSphere MQ client, create and mount a file system called /var/mqm. In this way, other system activity is not affected if a large amount of working data builds up.

To determine the size of the /var/mqm file system for a client, consider:

  • The size of the error log files in the /var/mqm/errors directory

  • The amount of trace data that is written to the /var/mqm/trace" directory

Typically, allow 15 MB of disk space in the /var/mqm file system.

 

Creating a separate file system for the error log files

You can also create a separate file system, /var/mqm/errors, for the error log files. This file system can be NFS mounted but, if you choose to do this, you might lose the error logs if the network fails. Typically, allow 4 MB of disk space for the error log files.

 

Creating the mqm user ID and mqm group

The mqm user ID, with a primary group of mqm, is created automatically during the installation of WebSphere MQ, unless you are using Caldera OpenLinux. After installation, the mqm user ID owns the directories and files that contain the resources associated with the product.

You can create the mqm user ID and mqm group yourself. You might do this, for example, if you want to configure your security environment before installing WebSphere MQ. If you are installing on Caldera OpenLinux, you must create the mqm user ID and mqm group yourself before installing WebSphere MQ.

 

Installation

This installation procedure uses the Red Hat Package Manager (RPM) installer, which allows you to choose the components you want to install. The components are listed in Components for Linux.

  1. Log in as root.

  2. Mount WebSphere MQ Client CD-ROM 2 on the target machine.

  3. Select the set of client components that you want to use for the installation, and change into the corresponding directory on the CD-ROM.

    If you select a set of client components without the SSL support, you cannot install the IBM Global Security Kit (GSKit) V6 or the WebSphere MQ support for iKeyman. Table 2 shows each set of client components and its corresponding directory on the CD-ROM.

    Table 2. Sets of client components on Client CD-ROM 2

    Linux for Intel without the SSL support /linux_intel/MQClient
    Linux for Intel with the SSL support /linux_intel/MQClientwithSSL
    Linux for zSeries without the SSL support /linux_zseries/MQClient
    Linux for zSeries with the SSL support /linux_zseries/MQClientwithSSL

    Notes:

    1. If you do not have a locally attached CD-ROM drive, you can copy the contents of the directory you require from a machine that does have a CD-ROM drive to the target machine using, for example, the ftp utility. If you do this, ensure that you copy the entire directory structure for the set of client components you have selected, and that you maintain the same directory structure on the target machine.

      You can now install the client components from the local copy of the directory.

    2. If the machine hosting the CD-ROM is an NFS server, you can mount the contents of the CD-ROM on the target machine using NFS.

  4. Run the mqlicense.sh script.

    The license is displayed. If you accept the license, the installation continues. If you decline, the message: 

    Product cannot be installed until the license agreement has been accepted...

    is displayed, and the installation fails.

    If you are performing a silent or remote install, you can run the mqlicense.sh script with the -accept option, so that the license is accepted without being displayed.

  5. Use the rpm -i command to install a minimum client configuration. For example:

    • If you are installing on an Intel machine, enter the following commands, in the order shown, to install the Runtime and Client components: 
      rpm -i MQSeriesRuntime-5.3.0-1.i386.rpm
rpm -i MQSeriesClient-5.3.0-1.i386.rpm

    • If you are installing on a zSeries machine, enter the following commands, in the order shown, to install the Runtime and Client components: 
      rpm -i MQSeriesRuntime-5.3.0-1.s390.rpm
rpm -i MQSeriesClient-5.3.0-1.s390.rpm

    • To install only the Java messaging component on an Intel machine, enter the following command: 
      rpm -i MQSeriesJava-5.3.0-1.i386.rpm
    The WebSphere MQ license notice is shown only when the first component is installed. It is not shown again for subsequent components.

  6. Use the rpm -i command to install any other components that you require.

    For example, to install the IBM Global Security Kit (GSKit) V6 and the WebSphere MQ support for iKeyman on a zSeries machine, enter the following commands in the order shown: 

    rpm -i gsk6bas-6.0-n.nn.s390.rpm
rpm -i MQSeriesKeyman-5.3.0-1.s390.rpm

    Look for the gsk6bas package on the CD-ROM to find the value of n.nn.

Distributions that do not use the Red Hat Package Manager (RPM) installer by default might generate an error when you install the WebSphere MQ client.

 

Translated messages

Messages in U.S. English are always available. If you require messages in a different language, ensure that:

  1. You install the appropriate message catalog.

  2. Your NLSPATH environment variable includes the appropriate directory. For example, to select messages in German use the following: 
    export LANG=de
export NLSPATH=/usr/share/locale/%L/LC_MESSAGES/%N

To find out which language is currently installed, use the locale command.

 

Removing the WebSphere MQ client from Linux

Before you attempt to remove the WebSphere MQ client, check that no WebSphere MQ client application is running on your system.

To remove the WebSphere MQ client, first find out the package names of the components currently installed on your system. To list the package names with their version information, enter the following commands: 

rpm -q -a | grep MQ
rpm -q -a | grep gsk

Alternatively, to list the package names without their version information, enter the following commands: 

rpm -q -a --queryformat "%{NAME}\n" | grep MQ
rpm -q -a --queryformat "%{NAME}\n" | grep gsk

To remove a component, with package name MQSeriesSamples for example, enter the following command: 

rpm -e MQSeriesSamples

Some of the components are dependent on others. The rpm command does not remove a component if others are dependent on it. For this reason, remove the components in an order such that each component you remove has no other component dependent on it. To list all the components on which a specific component depends, MQSeriesClient for example, enter the following command: 

rpm -q --requires MQSeriesClient

Alternatively, remove the components in the order shown in Table 3. Remove only those components that you have installed on your system.

Table 3. Order for removing components

Message catalogs MQSeriesMsg_xx1
Sample programs MQSeriesSamples
Client MQSeriesClient
SDK MQSeriesSDK
Runtime MQSeriesRuntime
WebSphere MQ support for iKeyman MQSeriesKeyMan
IBM Global Security Kit (GSKit) V6 gsk6bas2
Java messaging MQSeriesJava

After removing the WebSphere MQ client, delete the /var/mqm directory, unless you are migrating to a later release of the WebSphere MQ client.

 

Migrating to and from the WebSphere MQ SSL support

To upgrade a WebSphere MQ client without the SSL support to one with the SSL support, install the two additional components, IBM Global Security Kit (GSKit) V6 and WebSphere MQ support for iKeyman. To downgrade a WebSphere MQ client with the SSL support to one without the SSL support, simply remove these two components. You do not have to remove any other components.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.