Setting the native library path in WebSphere Application Server 7.0

If you deploy the Java Platform, Enterprise Edition (Java EE) database logger application on WebSphere® Application Server 7.0, and you want to use bindings mode connections between the application and IBM® MQ, you must configure the IBM MQ messaging provider with the location of the IBM MQ native libraries on the system.

About this task

If you do not set the native library path in your application server, you might receive the following error message in the WebSphere Application Server 7.0 system out log: 

A connection could not be made to WebSphere MQ for the following reason: 
  CC=2;RC=2495;AMQ8568: The native JNI library 'mqjbnd' was not found. [3=mqjbnd]
Use the WebSphere Application Server 7.0 administrative console to complete the following steps:

Procedure

  1. In the navigation pane, expand Resources > JMS > JMS Providers.
  2. Select the IBM MQ messaging provider that is at the correct scope for the connection factory or activation specification that creates the bindings mode connection.
    Note: 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.
  3. Under General Properties, in the Native library path field, enter the full name of the directory that contains the IBM MQ native libraries.
    For example, on Linux® enter /opt/mqm/java/lib. Enter only one directory name.
  4. Click OK.
  5. Restart the application server to refresh the configuration.
  6. Required: Restart the application server a second time to load the libraries.