Install WebSphere MQ as a JMS provider

 

+

Search Tips   |   Advanced Search

 

If you have a messaging infrastructure based on WebSphere MQ, you can connect directly using the included support for WebSphere MQ as a JMS provider.

(UNIX platforms only): Before you install WebSphere MQ on a UNIX platform, create and mount a journalized file system called...

/var/mqm

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

/var/mqm

You can also create separate file systems for your log data...

/var/mqm/log

...and error files...

/var/mqm/errors

You should 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...

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.

It is not recommended to install Rational Application Developer and WAS on the same machine when using WebSphere MQ.

See WebSphere MQ messaging platform-specific books for more information.

 

Overview

To install and configure WebSphere MQ for use as a JMS provider to IBM WAS...

 

Procedure

  1. Install a supported version of WebSphere MQ, with the required MQ features with WebSphere MQ.

    For RHEL 3.0 and SLES 8, before installing WebSphere MQ 5.3 on an Intel or zSeries Linux system using the 2.6 kernel, first download FixPack 10 or later (plus any applicable interim fixes) and follow the software prerequisite instructions. Otherwise, you might see a segmentation fault error when attempting to run...

    mqlicense.sh -accept

    ...to accept the WebSphere MQ license agreement. Also, export the following variable:

    LD_ASSUME_KERNEL=2.4.19

    See the WebSphere MQ V5.3 for Linux for Intel fix pack readme

    See the WebSphere MQ V5.3 for Linux for zSeries fix pack readme

    If request metrics is enabled when using WebSphere MQ V5.3, an exception is issued and request metrics functions fail. If you use WebSphere MQ V5.3 plus CSD08, no exception is issued; however, request metrics still fails to record the JMS type request information. The solution is to apply the interim fix for WebSphere MQ V5.3 plus CSD08. Put the JAR files in...

    /opt/IBM/WAS/AppServer/lib/WMQ/java/lib

    ...and in the external directories...

    websphere_mq_install_root/java/lib

  2. To use WebSphere MQ - Publish/Subscribe support, provide a broker using either WebSphere MQ Event Broker or WebSphere MQ Integrator.

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

  4. [AIX] For AIX, see the WebSphere MQ readme.txt for additional steps.

  5. Set the...

    MQ_INSTALL_ROOT

    ...environment variable to the directory where WebSphere MQ is installed.

  6. To connect to WebSphere MQ 5.3 support in bindings mode only, set the...

    MQ_INSTALL_VERSION

    ...environment variable to 5. In WAS V6, this environment variable is available in Version 6.1.0.5 or later.

 

Results

This task has installed WebSphere MQ for use as a JMS provider for WAS.

 

What to do next

You can configure JMS resources to be provided by WebSphere MQ, by using the console to define WebSphere MQ resources.

On UNIX systems, restrict access to the messaging errors directories and logging files...

  1. /var/mqm/errors

    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. /var/mqm/qmgrs/@SYSTEM/errors

    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




Configure resources for the WebSphere MQ JMS provider