If you have a WebSphere MQ messaging infrastructure, you can install and configure it as a JMS provider to WebSphere Application Server.
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 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 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 following WebSphere MQ publications:
You can get these books from the WebSphere MQ messaging platform-specific books Web page at http://www.ibm.com/software/integration/wmq/library/
To install and configure WebSphere MQ for use as a JMS provider to IBM WebSphere Application Server, complete the following steps:
To identify the supported version of WebSphere MQ, see the following article: Detailed system requirements page.
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) (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 at http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006464. Otherwise, you might 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
To see the WebSphere MQ V5.3 for Linux for Intel fix pack readme see http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006464
To see the WebSphere MQ V5.3 for Linux for zSeries fix pack readme see http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006464
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.ibm.com/support/docview.wss?rs=0&q1;=1192026&uid=swg21192026.
You can configure JMS resources to be provided by WebSphere MQ, by using the WebSphere Application Server 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.
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
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
For information about how WebSphere Application Server can interact with a WebSphere MQ network, using either a WebSphere MQ Link or a WebSphere MQ server, see the following topics: