Installing WebSphere MQ to interoperate with WebSphere Application Server

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 New feature:

[Updated in February 2013] In previous versions of WebSphere Application Server (for example Version 6.1), you can connect to a queue manager by using the WebSphere MQ classes for JMS that are present in aWebSphere MQ Client or Server installation on the same machine (that is on a different directory from WebSphere Application Server). You achieve this configuration by setting the MQ_INSTALL_ROOT variable. [Updated in February 2013]

feb2013

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

  1. 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.

  2. Follow the WebSphere MQ instructions for verifying your installation setup.
  3. 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.

  4. [AIX] Optional: Run the dltmqlnk WebSphere MQ control command.

    If your application server is 64 bit, you must run the dltmqlnk WebSphere MQ control command as root before applications are able to connect to a queue manager using a BINDINGS transport type. The command must be rerun each time a WebSphere MQ fix pack is installed. For more information, see the Implications of a 64-bit queue manager section of the WebSphere MQ information center.

  5. Configure the WebSphere MQ messaging provider with native libraries information.

    The WebSphere MQ messaging provider does not include the native libraries required to connect to a WebSphere MQ queue manager in bindings mode. In order to use a bindings mode connection, WebSphere MQ must be installed onto the same machine as the application server, and the native library path for the resource adapter must be configured to point to the WebSphere MQ directory where these libraries are located. See Configuring the WebSphere MQ messaging provider with native libraries information for more details.

    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.
  6. 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.

    Attention: 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.

    For any change in the MQ product (such as a PTF upgrade), you must restart the WebSphere Application Server and all nodes.

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.




In this information ...


Related reference

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jun 11, 2013 8:40:09 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v701sca&product=was-nd-mp&topic=tmj_instm
File name: tmj_instm.html