+

Search Tips   |   Advanced Search

Install WebSphere MQ to interoperate with WebSphere Application Server

When you install a new WebSphere MQ network, we can tune the installation for working with WebSphere Application Server. If we have an established WebSphere MQ network, we can choose whether to modify some of the settings for better interoperation.

This topic provides installation instructions for setting up a new WebSphere MQ installation to interoperate with WebSphere Application Server. If we have an established WebSphere MQ network, treat this task as a source of tips to tune the existing WebSphere MQ installation.

  1. [In WebSphere MQ] 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.

    We can not install Rational Application Developer and WAS on the same machine when using WebSphere MQ.

    See the following for other installation prerequisites of different WebSphere MQ releases:

  2. [In WebSphere MQ] Follow the WebSphere MQ instructions for verifying the installation setup. We can verify the server installation either using the command line or using the postcard application.

  3. [In WebSphere Application Server and WebSphere MQ] Configure WebSphere Application Server and WebSphere MQ to interoperate effectively.

    For more information, see Connect WebSphere Application Server to WebSphere MQ .

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

    If the 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 product information.

    This step applies to releases that are earlier than WebSphere MQ version 7.1. For more information, see UNIX and Linux: crtmqlnk and dltmqlnk removed and UNIX and Linux :/usr symbolic links removed.

  5. [In WebSphere Application Server] 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 Configure the WebSphere MQ messaging provider with native libraries information.

    For migration purposes only, we 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 Installing WebSphere MQ to interoperate with WebSphere Application Server.

  6. Optional: [In WebSphere Application Server] At Cell scope or Node scope, set the WAS 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 we 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.

    If we 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 WebSphere MQ product (such as a PTF upgrade), you must restart WebSphere Application Server and all nodes.

  7. Optional: [In WebSphere Application Server] At Cell scope or Node scope, set the WAS MQ_USE_BUNDLE_REFERENCE_INSTALL environment variable to True. When this variable is set to True, the WebSphere MQ JMS bundle is installed using a reference installation.

    (iseries)(dist) The OSGi framework shares a storage area on disk. Because all servers of the installation use this storage area, multiple servers in the installation might read and or write data to this storage area concurrently, causing resource contention. The likelihood of a contention scenario occurring increases if the MQ_CLEAR_MQ_FROM_OSGI_CACHE_ON_SHUTDOWN variable is set to True. Setting the MQ_USE_BUNDLE_REFERENCE_INSTALL variable to True causes the WebSphere MQ JMS bundle to be installed using a reference installation, thereby avoiding the need for the OSGi framework to persist the WebSphere MQ JMS bundle file to the shared storage area. Instead, each server creates a unique bundle file for its use

    (zos) The OSGi framework shares a storage area on disk. Because all servers of the installation use this storage area, multiple servers in the installation might read and or write data to this storage area concurrently, causing resource contention. The likelihood of a contention scenario occurring increases if the MQ_CLEAR_MQ_FROM_OSGI_CACHE_ON_SHUTDOWN variable is set to True. Setting the MQ_USE_BUNDLE_REFERENCE_INSTALL variable to True causes the WebSphere MQ JMS bundle to be installed using a reference installation, thereby avoiding the need for the OSGi framework to persist the WebSphere MQ JMS bundle file to the shared storage area. Instead, each server and controller creates a unique bundle file for its use.


What to do next

We are now ready to configure a messaging provider. If wer business uses WebSphere MQ, and 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 we are not sure which provider combination is best suited to the needs, see Choose messaging providers for a mixed environment.

To create WebSphere MQ messaging provider resources, see Configure JMS resources for the WebSphere MQ messaging provider.


Subtopics


Related concepts

  • Interoperation using the WebSphere MQ messaging provider


    Related tasks

  • Choose messaging providers for a mixed environment
  • Configure JMS resources for the WebSphere MQ messaging provider


    WebSphere MQ library