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.
About this task
This topic provides installation instructions for setting
up a new WebSphere MQ
installation to interoperate with WebSphere Application Server. If you have an established WebSphere MQ
network, treat this task as a source of tips to tune your existing WebSphere MQ installation.
New feature: In
previous versions of WebSphere Application Server,
you can connect to a queue manager by using the WebSphere MQ classes for
JMS that are in an external WebSphere MQ installation (a WebSphere MQ installation that is on a different machine from WebSphere Application Server). You achieve this configuration
by setting the MQ_INSTALL_ROOT variable.
In WebSphere Application Server Version 7.0, the MQ_INSTALL_ROOT
variable is only used to locate native libraries, and is overridden
by any native library path configured on the Resource Adapter.
newfeat
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 Detailed system requirements page.
You must
not install Rational® Application
Developer and WebSphere Application Server on the same machine when using WebSphere MQ.
For other installation
prerequisites, see the "Quick Beginnings" information for your
platform in the WebSphere MQ
information center.
- Follow the WebSphere MQ
instructions for verifying your installation setup.
-
Configure WebSphere Application Server and WebSphere MQ
to interoperate effectively.
For information about the
prerequisites and requirements for effective interoperation, see the
following technote: Information about using the WebSphere MQ messaging provider
for WebSphere Application Server Version 7.0.
-
Configure the WebSphere MQ messaging provider
with native libraries information.
To connect to a WebSphere MQ queue manager or queue-sharing
group in bindings mode, the WebSphere MQ messaging provider
needs to know where to load native libraries from. For more information,
see Configuring the WebSphere MQ messaging provider with native libraries information.
Note: For migration purposes
only, you can also specify native path information, when in an application
server environment, by setting the
MQ_INSTALL_ROOT WebSphere Application Server environment
variable. For more information see the version of this topic that
is in the
WebSphere Application Server Version 6.1 information center:
Installing
WebSphere MQ to interoperate with WebSphere Application Server.
- 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 by 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 predominantly 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
create WebSphere MQ messaging
provider resources, see Configuring JMS resources for the WebSphere MQ messaging provider.