Install MQ as the JMS provider

 

File Systems

For UNIX platforms, before you install MQ, create and mount a journalized file system called /var/mqm for messaging working data.

Use a partition strategy with a separate volume for the MQ data. This means that other system activity is not affected if a large amount of messaging work builds up in /var/mqm.

One can also create separate file systems for your log data (var/mqm/log) and error files (var/mqm/errors). Store log files on a different physical volume from the messaging queues (var/mqm). This ensures data integrity in the case of a hardware failure. If you are creating separate file systems, allow a minimum of 30 MB of storage for /var/mqm, 20 MB of storage for /var/mqm/log, and 4 MB of storage for /var/mqm/errors.

The /var file system is used to store all the security logging information for the system, and is used to store the temporary files for email and printing. Therefore, it is critical that you maintain free space in /var for these operations. If you do not create a separate file system for messaging data, and /var fills up, all security logging will be stopped on the system until some free space is available in /var. Also, email and printing will no longer be possible until some free space is available in /var.

 

Configuration Steps

 

  1. Install MQ 5.3, with the required MQ features.

    The WAS Enterprise package includes copies of the MQ 5.3 and Event Broker installation packages, with restricted licensing for use with WAS Enterprise. (MQ Event Broker is not available for Linux.)

    If you want to use the original MQ 5.3 release, ensure that you install the CSD03 update.

    If you want to use MQ 5.3 on the same machine as WAS embedded messaging, ensure that you install the following MQ features:

    • For a WAS Embedded Messaging Server installation, the required MQ features are "Server" and "Java Messaging".

    • For a WAS Embedded Messaging Client installation, the only required MQ feature is "Java Messaging".

    One can use the MQ 5.3 installation package provided with WAS Enterprise to install the required MQ features into an existing MQ 5.3 or to install a new MQ 5.3 with the required MQ features for use with WAS Enterprise subject to the licensing conditions.

  2. If you want to use MQ - Publish/Subscribe support, you need to provide a Publish/Subscribe broker. One can do this by using either of the following:

  3. Follow the MQ 5.3 instructions for verifying your installation setup.

  4. For AIX, see the MQ 5.3 readme.txt for additional steps.

  5. (Optional)  

    If you want to install IBM WAS on the same host as MQ, and have not yet done so, install IBM WAS. If you do not want to use the embedded WebSphere JMS provider, you can install MQ then install WAS without the Embedded Messaging Server option. You are recommended to install and use the WAS Embedded Messaging Client.

  6. Set the MQJMS_LIB_ROOT environment variable to the directory where WebSphereMQ\Java\lib is installed. IBM WAS uses the MQJMS_LIB_ROOT to locate the MQ libraries for the MQ JMS Provider.

 

Results

This task has installed MQ for use as the JMS provider with WAS.

One can configure JMS resources to be provided by MQ, by using the WAS admin console to define MQ resources.

 

What to do next

(UNIX platforms only) Restrict access to the messaging errors directories and logging files, by using the following commands:

  1. For the /var/mqm/errors directory: 

    chmod 3777 /var/mqm/errors
chown mqm:mqm /var/mqm/errors

touch /var/mqm/errors/AMQERR01.LOG 
chown mqm:mqm /var/mqm/errors/AMQERR01.LOG
chmod 666 /var/mqm/errors/AMQERR01.LOG

touch /var/mqm/errors/AMQERR02.LOG
chown mqm:mqm /var/mqm/errors/AMQERR02.LOG
chmod 666 /var/mqm/errors/AMQERR02.LOG

touch /var/mqm/errors/AMQERR03.LOG
chown mqm:mqm /var/mqm/errors/AMQERR03.LOG 
chmod 666 /var/mqm/errors/AMQERR03.LOG

  2. For the /var/mqm/qmgrs/@SYSTEM/errors directory: 

    chmod 3777 /var/mqm/qmgrs/@SYSTEM/errors
chown mqm:mqm /var/mqm/qmgrs/@SYSTEM/errors

touch /var/mqm/qmgrs/@SYSTEM/errors/AMQERR01.LOG 
chown mqm:mqm /var/mqm/qmgrs/@SYSTEM/errors/AMQERR01.LOG
chmod 666 /var/mqm/qmgrs/@SYSTEM/errors/AMQERR01.LOG

touch /var/mqm/qmgrs/@SYSTEM/errors/AMQERR02.LOG
chown mqm:mqm /var/mqm/qmgrs/@SYSTEM/errors/AMQERR02.LOG
chmod 666 /var/mqm/qmgrs/@SYSTEM/errors/AMQERR02.LOG

touch /var/mqm/qmgrs/@SYSTEM/errors/AMQERR03.LOG
chown mqm:mqm /var/mqm/qmgrs/@SYSTEM/errors/AMQERR03.LOG 
chmod 666 /var/mqm/qmgrs/@SYSTEM/errors/AMQERR03.LOG

This is part of the procedure to secure the directories and log files needed for MQ, as described in Securing messaging directories and log files.

Managing WebSphere internal JMS servers
Defining a generic JMS provider
Installing and configuring a JMS provider
Moving from the embedded WebSphere JMS provider to MQ
Configure resources for the MQ JMS provider

 

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.