Implementation > Message exchange services for integrations > Integration message queuing services: Messaging > Configuration tasks > Copying jar files from Messaging to Integrator

Copying jar files from Messaging to Integrator

About handling jars

Some of the JAR files installed during the Messaging installation must be copied to the Integrator Server with which Messaging exchanges messages. You must repeat this operation every time there is a change in the Messaging installation.

Procedures

Copying JARS

Copy the following files from the lib directory of the Messaging installation directory, to a directory accessible by Integrator:

jmsapi.jar
jms-sun.jar
jta-101B.jar
xmsapi.jar

Editing the classpath

You must also create references to the JAR files in the classpath definition of the Integrator installation.

Windows

For Windows, add or modify the CLASSPATH environment variable for the user who installed Integrator (example):

CLASSPATH = …;c:\java\jms\jmsapi.jar;c:\java\jms\jmssun. jar;c:\java\jms\jta-101B.jar;c:\java\jms\xmsapi.jar

UNIX

For UNIX-based systems, open the file:

<CORE_ROOT>/local/bin/core_setup

and add the following line at the end of the file (example):

export CLASSPATH=$CLASSPATH:/home/java/jms/jmsapi. jar: /home/java/jms/jmssun. jar:/home/java/jms/jta-101B.jar: /home/java/jms/xmsapi.jar

In the paths of the preceding example, we assume that the JAR files have been copied in the directory /java/lib.

To avoid conflicts with other providers such as WebSphere MQ, you must not modify the global CLASSPATH environment variable.

It is possible to specify environment variables for each Integrator Processing engine. To do this, you must modify the the file <CORE_ROOT>/local/config/starter/starter.env

In this file you either:

Set the CLASSPATH environment variable directly in the starter.env file. If for example you name the dedicated Processing Engine task for the JMS CommAdapter 'ProcengineJMS', you then specify the CLASSPATH as follows:
ProcengineJMS:
CLASSPATH=$CLASSPATH:/full_path/jmsapi.jar:/full_path/jmssun. jar:/full_path/jta-101B.jar:/full_path/xmsapi.jar
Set the CORE_JVM_COMMON_CREATE_FILES environment variable in the starter.env file. Enter the path to a file which will be taken into account when launching the JVM. In this file (which can be shared between several ProcEngines) you can then specify the CLASSPATH value.