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

About this task

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 for the AdminTask object, or you can use the administrative console to complete the following steps:

Procedure

  1. In the navigation pane, expand Resources > JMS > JMS providers .
  2. 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. Note that native path information at Server scope is used in preference to native path information at higher scopes, and native path information at Node scope is used in preference to native path information at Cell scope.
    [z/OS] Note: When using WebSphere MQ messaging provider connection factories or activation specifications that create bindings mode connections to a WebSphere MQ for z/OS® queue manager, ensure that the IDBACK parameter is large enough. Otherwise, MQExceptions with a completion code of 2, and a reason code of 2025 (MQRC_MAX_CONNS_LIMIT_REACHED) can occur. For more information on how to set the IDBACK parameter, refer to the CSQ6SYSP macro section in the following the WebSphere MQ information centre pages:

    WebSphere MQ Version 7.0: Task 17: Tailor your system parameter module

    WebSphere MQ Version 6.0: Task 17: Tailor your system parameter module.

  3. 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.
  4. Click OK.
  5. Save any changes to the master configuration.
  6. If you are running in an application server environment, you must restart all affected servers twice when you 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, you must 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

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 following topic in the WebSphere Application Server Version 6.1 information center: Installing WebSphere MQ to interoperate with WebSphere Application Server (Version 6.1).



In this information ...


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    

Terms of Use | Feedback

Last updated: Oct 21, 2010 10:04:34 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=tmj_adm33
File name: tmj_adm33.html