Network Deployment (Distributed operating systems), v8.0 > Administer applications and their environment > Administer Messaging resources > Manage messaging with the WebSphere MQ messaging provider > Install WebSphere MQ to interoperate with WAS
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.
If you are running in a client environment, use launchClient to start a client application. In the system property MQ_INSTALL_ROOT enter the name of a directory that contains the WebSphere MQ native libraries, in a subdirectory of java/lib or java/lib64 depending on whether you are using 32 bit or 64 bit native libraries. For example, on Linux specify ./launchClient.sh myappclient.ear -CCDMQ_INSTALL_ROOT=/opt/mqm/.
If you are running in an application server environment, you can configure the WebSphere MQ messaging provider with native path information by using the command line, as described in WMQAdminCommands command group , or you can use the admin console...
Note: If your 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. See the "Implications of a 64-bit queue manager" in the Quick Beginnings for AIX section of the WebSphere MQ information center.
Procedure
- In the navigation pane, expand Resources > JMS > JMS providers .
- Select the WebSphere MQ messaging provider that is at the correct Scope for the connection factory or activation specification that will create the bindings mode connection.
- Native path information at Server scope is used in preference to native path information at all other scopes.
- Native path information at Cluster scope is used in preference to native path information at Node and Cell scopes.
- Native path information at Node scope is used in preference to native path information at Cell scope.
- Under General Properties, in the Native library path property, enter the full name of the directory that contains the WebSphere MQ native libraries. For example, on Linux enter /opt/mqm/java/lib.
Enter only one directory name.
- Click OK.
- Save any changes to the master configuration.
- If you are running in an application server environment, restart all affected servers twice when we have changed the native path information. Otherwise, a WMSG1623E message is produced, indicating that the WebSphere MQ messaging provider is not available.
If you are running in a client environment, rerun the client program twice. Otherwise, a WMSG2013E message is produced.
Whichever environment you are running in, until you perform these restarts any attempt to use a WebSphere MQ messaging provider resource (for example, a connection factory) from one of the affected servers causes a javax.naming.NamingException and a WMSG2003E message.
What to do next
For migration purposes only, you can also specify native path information, when in an application server environment, by setting the MQ_INSTALL_ROOT WAS environment variable. See the following topic in the WAS v6.1 information center:
Install WebSphere MQ to interoperate with WAS (Version 6.1).
Interoperation using the WebSphere MQ messaging provider
Install WebSphere MQ to interoperate with WAS
Configure JMS resources for the WebSphere MQ messaging provider