[Version 5.0.1 and later]Installing WebSphere MQ as the JMS provider

Use this task to install and configure WebSphere MQ with support for the Java Message Service (JMS) for use with the WebSphere Application Server.

Before you begin

(UNIX platforms only) Before you install WebSphere MQ, 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 30 MB of storage for /var/mqm, 20 MB of storage for /var/mqm/log, and 4 MB of storage for /var/mqm/errors.

Why and when to perform this task

To install and configure WebSphere MQ (MQSeries) for use as a JMS provider to IBM WebSphere Application Server, complete the following steps:

Steps for this task

  1. Install WebSphere MQ with the required MQ features, as described in the installation instructions provided with WebSphere MQ.

    If you are installing WebSphere MQ on top of WebSphere Application Server embedded messaging, perform the following actions when installing WebSphere MQ:

    1. When asked if you want to remove or modify the version of WebSphere MQ currently installed, choose to remove the Server. (The WebSphere MQ install program recognizes the installed WebSphere embedded messaging as an installed version of WebSphere MQ.)
    2. Select the option to keep existing queue managers.
    3. Proceed with the installation of the full WebSphere MQ Server by running the install program again, after the old WebSphere MQ server (the Embedded Messaging Server) has been removed.

    [5.0 only][Version 5.0.1][Version 5.0.2]Note: The WebSphere Application Server Enterprise package includes copies of the WebSphere MQ and Event Broker installation packages, with restricted licensing for use with WebSphere Application Server Enterprise. (WebSphere MQ Event Broker is not available for Linux.) For more information about the usage restrictions for the WebSphere MQ and Event Broker installation packages, see the WebSphere Application Server Enterprise licensing information.

    If you want to use the original WebSphere MQ release, ensure that you install the CSD04 update.

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

    • For a WebSphere Application Server Embedded Messaging Server installation, the required MQ features are "Server" and "Java Messaging".
    • For a WebSphere Application Server Embedded Messaging Client installation, the only required MQ feature is "Java Messaging".

    [5.0 only][Version 5.0.1][Version 5.0.2]You can use the WebSphere MQ installation package provided with WebSphere Application Server Enterprise to install the required WebSphere MQ features into an existing WebSphere MQ or to install a new WebSphere MQ with the required MQ features for use with WebSphere Application Server Enterprise subject to the licensing conditions.

    For information about installing WebSphere MQ or migrating to WebSphere MQ from an earlier release, see the appropriate WebSphere MQ Quick Beginnings book, as listed above.

  2. If you want to use WebSphere MQ - Publish/Subscribe support, you need to provide a Publish/Subscribe broker.

    For example, you can do this by using either WebSphere Event Broker (formerly WebSphere MQ Event Broker) or WebSphere Message Broker (formerly WebSphere MQ Integrator).

    For more information about installing WebSphere Event Broker (formerly WebSphere MQ Event Broker) or WebSphere Message Broker (formerly WebSphere MQ Integrator), see the following Web sites:

  3. Follow the WebSphere MQ instructions for verifying your installation setup.
  4. For AIX, see the WebSphere MQ readme.txt for additional steps.
  5. If you want to install IBM WebSphere Application Server on the same host as WebSphere MQ, and have not yet done so, install IBM WebSphere Application Server.
    If you do not want to use the embedded WebSphere JMS provider, you can install WebSphere MQ then install WebSphere Application Server without the Embedded Messaging options.
  6. Set the MQJMS_LIB_ROOT environment variable to the directory where WebSphereMQ\Java\lib is installed.
    IBM WebSphere Application Server uses the MQJMS_LIB_ROOT to locate the WebSphere MQ libraries for the WebSphere MQ JMS Provider.

Results

This task has installed WebSphere MQ for use as the JMS provider with WebSphere Application Server.

What to do next

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

(UNIX platforms only) Restrict access to the messaging errors directories and logging files, by using the following commands. This is part of the procedure to secure the directories and log files needed for WebSphere MQ, as described in Securing messaging directories and log files.

  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
    

After installing WebSphere MQ and WebSphere Application Server on the same host, you should only service WebSphere MQ with its CSD updates, and separately service WebSphere Application Server with its fix packs. This approach helps to avoid potential failures if you later decide to uninstall WebSphere Application Server fix packs. Also, if you apply a fix pack to WebSphere Application Server, specify not to update the Embedded Messaging feature.


Related tasks
Defining a generic JMS provider
Installing and configuring a JMS provider
Moving from the embedded WebSphere JMS provider to WebSphere MQ
Configuring resources for the WebSphere MQ JMS provider



Searchable topic ID:   tmj_instm
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/tmj_instm.html

Library | Support | Terms of Use | Feedback