WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with the WebSphere MQ messaging provider
Install WebSphere MQ to interoperate with WAS
When you install a new WebSphere MQ network, we can tune the installation for working with WAS. 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 WAS. If we have an established WebSphere MQ network, treat this task as a source of tips to tune your existing WebSphere MQ installation.
- 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.
You should not install Rational Application Developer and WAS on the same machine when using WebSphere MQ.
For other installation prerequisites, see the Quick Beginnings section for the platform, in the WebSphere MQ information center.
- Follow the WebSphere MQ instructions for verifying your installation setup.
- Configure WAS 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 WAS v8.0.
-
Optional: Run the dltmqlnk WebSphere MQ control command.
If the application server is 64 bit, 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.
- 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 WAS environment variable. For more information see, Install WebSphere MQ to interoperate with WAS.
- Optional: 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 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 WebSphere MQ product (such as a PTF upgrade), you must restart WAS and all nodes.
You are now ready to configure a messaging provider. If your business uses WebSphere MQ, and to integrate WAS 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 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
- 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. This information is known as native path information. The way native path information is set depends on whether the connection is established in an application client or in an application server environment. - Maintain the WebSphere MQ resource adapter
The WebSphere MQ resource adapter is used by all applications that perform JMS messaging with the WebSphere MQ messaging provider. The WebSphere MQ resource adapter is usually updated automatically when we apply WAS fix packs, but if we have previously manually updated the resource adapter manually update your configuration to ensure that maintenance is applied correctly.
Related concepts:
Interoperation using the WebSphere MQ messaging provider
Related
Choose messaging providers for a mixed environment
Configure JMS resources for the WebSphere MQ messaging provider
Reference: