Install WebSphere MQ as a JMS provider

WebSphere MQ as a JMS provider

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

Before you begin

If you have a messaging infrastructure based on WebSphere MQ, you may either connect directly using the included support for WebSphere MQ as a JMS provider, or configure a service integration bus with links to a WebSphere MQ network and then access the bus through the default messaging 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 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.
- It is not recommended to install Rational Application Developer and WebSphere Application Server on the same machine when using WebSphere MQ.
- For more information a security logging issue, see Security and WebSphere MQ.
- For more information about creating file systems for WebSphere MQ, and WebSphere MQ space requirements for /var file systems, see the section "Preparing for Installation: Creating WebSphere MQ file systems" in the appropriate WebSphere MQ Quick Beginnings book.
- For other installation prerequisites, see the appropriate WebSphere MQ Quick Beginnings book, as follows:
  - WebSphere MQ for Windows, Quick Beginnings, GC34-6073
  - WebSphere MQ for AIX, Quick Beginnings, GC34-6076
  - WebSphere MQ for Solaris, Quick Beginnings, GC34-6075
  - WebSphere MQ for HP-UX, Quick Beginnings, GC34-6077
  - WebSphere MQ for Linux for Intel and Linux for zSeries, Quick Beginnings , GC34-6078
  You can get these books from the WebSphere MQ messaging platform-specific books Web page at http://www-3.ibm.com/software/ts/mqseries/library/manualsa/manuals/platspecific.html

Why and when to perform this task

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

Steps for this task

Install a supported version of WebSphere MQ, with the required MQ features, as described in the installation instructions provided with WebSphere MQ.
To identify the a supported version of WebSphere MQ, see the Supported hardware and software Web page at http://www.ibm.com/software/webservers/appserv/doc/latest/prereq.html .
For information about installing WebSphere MQ, or migrating to a supported version of WebSphere MQ from an earlier version, see the appropriate WebSphere MQ Quick Beginnings book, as listed above.
(RHEL 3.0 and SLES 8) After you install WebSphere MQ on any of the following platforms, but before you try to accept the license, apply the fix located at: http://l3.hursley.ibm.com/cgi-bin/ViewPRB.pl?1812. Otherwise, you may see a segmentation fault error when attempting to run the mqlicense.sh -accept command to accept the WebSphere MQ license agreement. Also, export the following variable: LD_ASSUME_KERNEL=2.4.19
- Red Hat Enterprise Linux (RHEL) 3.0 on Intel or s390
- SUSE Linux Enterprise Server (SLES) 8 on Intel
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 Java Message Service (JMS) type request information. The solution is to apply the interim fix for WebSphere MQ V5.3 plus CSD08: Put the JAR files in the /opt/IBM/WebSphere/AppServer/lib/WMQ/java/lib directory and in the external websphere_mq_install_root/java/lib directories. For more information about this issue, see the Technote 1192026; for example, at http://www-1.ibm.com/support/docview.wss?rs=0&q1;=1192026&uid;=swg21192026
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 MQ Event Broker or WebSphere MQ Integrator (formerly MQSeries Integrator). For more information about these products, see the following Web sites:
- WebSphere MQ Event Broker Web site at http://www-4.ibm.com/software/ts/mqseries/platforms/#eventb
- WebSphere MQ Integrator Web site at http://www-4.ibm.com/software/ts/mqseries/platforms/#integrator
Follow the WebSphere MQ instructions for verifying your installation setup.
For AIX, see the WebSphere MQ readme.txt for additional steps.
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.
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.

ResultThis task has installed WebSphere MQ for use as a JMS provider for 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.

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

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

Searchable topic ID: tmj_instm