Jump to: navigation, search

WebSphereMQ—Interaction Server JVM

This page provides an example of configuring Interaction Server options to load JVM and all of the required libraries when using WebSphere MQ. See also the general description of configuring for Java.

Configuring Interaction Server options to load JVM and all of the required libraries (WebSphere MQ example)


  1. On the Options tab of the Interaction Server Application, create a section named java-config and add the option:
  2. jvm-path=/usr/lib/jvm/java-1.8.0-openjdk- (the full path to the libjvm.so, or jvm.dll if the operating system is Windows, on the host on which the Interaction Server is deployed).

  3. Create a section named jvm-options and add the following option:
    The example classpath contains list of jars required for IBM MQ 9.0.0. If you use another version of IBM MQ, refer to the corresponding documentation.
  4. Add the options -Xoss1m and -Xss1m to the jvm-options section. These options must have empty values.


Note on the first of the three options in Step 2: This option specifies the class path to Java archives that are necessary for JMS Capture Points on WebSphere MQ with iWD compatibility transformations to run. Note that in the class-path the jar files com.ibm.mq.jar, com.ibm.mqjms.jar, fscontext.jar, and jms.jar are located in some user-defined location, and are not supplied in the Interaction Server installation package. These files are installed on your host by the WebSphere MQ installation, server or client, and are typically located in the subdirectory /opt/mqm on Linux and C:\Program Files\IBM\MQ on Windows.

The connection to WebSphere MQ requires more than just the four jar files listed in the class-path, as these jar files depend on other jar files in the same directory. Therefore, the class-path should refer to them at the same location where they were placed by WebSphere MQ installation. Or, if they were copied, all files contained in the ./lib directory should be copied to the new location.

This page was last edited on February 14, 2022, at 08:23.
Comments or questions about this documentation? Contact us for support!