When you install a new WebSphere MQ network, you can tune the installation
for working with WebSphere Application Server. If you have an established
WebSphere MQ network, you can choose whether to modify some of the settings
for better interoperation. In either case, you need to set the WebSphere Application
Server MQ_INSTALL_ROOT environment variable.
About this task
To configure WebSphere MQ to interoperate with WebSphere Application
Server, complete the following steps:
Procedure
- Install a supported version of WebSphere MQ, as described in the
installation instructions provided with WebSphere MQ.
To
identify the supported version of WebSphere MQ, see the following article: Detailed system requirements page.
It is not recommended
to install Rational Application Developer and WebSphere Application Server
on the same machine when using WebSphere MQ.
For other installation
prerequisites, see the following WebSphere MQ publications:
- WebSphere MQ for HP OpenVMS Quick Beginnings
- WebSphere MQ for HP-UX Quick Beginnings
- WebSphere MQ for Windows V6.0 Quick Beginnings
- WebSphere MQ for AIX Quick Beginnings
- WebSphere MQ for Linux Quick Beginnings
- WebSphere MQ for Solaris Quick Beginnings
- WebSphere MQ for AIX V6.0 Quick Beginnings
- WebSphere MQ for iSeries V6.0 Quick Beginnings
You
can get these books from the WebSphere MQ messaging platform-specific books
Web page at
http://www.ibm.com/software/integration/wmq/library/.
-
Follow the WebSphere MQ instructions for verifying your installation
setup.
- At Node scope (not Server scope) set the WebSphere Application
Server MQ_INSTALL_ROOT environment variable to the directory where WebSphere
MQ is installed.
Note: By default the MQ_INSTALL_ROOT setting is
already at Node scope, so it is not necessary to create a new setting.
WebSphere
Application Server uses the MQ_INSTALL_ROOT setting to find the WebSphere
MQ libraries for the WebSphere MQ messaging provider. If
you use the default messaging provider and configure a WebSphere MQ server
bus member, the bus uses the MQ_INSTALL_ROOT setting to establish a direct
binding to WebSphere MQ rather than a TCP/IP network connection.
- Optional: At Cell scope or Node
scope, set the WebSphere Application Server MQ_CLEAR_MQ_FROM_OSGI_CACHE_ON_SHUTDOWN
environment variable to True. This allows
application server startup to automatically take account of changes that are
made to the MQ_INSTALL_ROOT environment variable and WebSphere MQ JMS client
libraries while the application server is stopped.
If you do not set this
variable, you must restart the application server a second time after any
changes of this type, to enable the application to perform messaging using
the WebSphere MQ messaging provider.
Note: If you set the MQ_CLEAR_MQ_FROM_OSGI_CACHE_ON_SHUTDOWN
environment variable, the startup time might increase because, on startup,
each application server needs to initialize an additional state associated
with WebSphere MQ installation.
What to do next
You are now ready to configure a messaging provider. If your business
uses WebSphere MQ, and you want to integrate WebSphere Application Server
messaging applications into a predominately WebSphere MQ network, the WebSphere
MQ messaging provider is the natural choice. However, there can be benefits
in using another provider. If you are not sure which provider combination
is best suited to your needs, see
Choosing messaging providers for a mixed environment.
To
configure messaging with the WebSphere MQ messaging provider, see Configuring JMS resources for the WebSphere MQ messaging provider.