Adding JMS Provider Client Libraries to Integration Server Classpath
Integration Server requires access to some of the JMS provider's Java client libraries. You can do one of the following:
![*](chapterTOC_bullet.png)
Place the libraries in the server's classpath by placing them in the
Integration Server_directory \instances\
instance_name\lib\jars\custom directory, as described in the procedure below.
![*](chapterTOC_bullet.png)
Make the libraries available to all server instances by placing them in the
Integration Server_directory \lib\jars\custom directory.
Note:
Files located in the server’s classpath take precedence over the files located at the Integration Server_directory \lib\jars\custom directory.
![*](chapterTOC_bullet.png)
Isolate the jars within a package classloader by placing them in the following directory:
packageName\code\jars.
If you place the files in the package classloader, make sure to set the Class Loader property when configuring a JMS connection alias to this JMS provider.
The JMS provider's .jar files could potentially conflict with other webMethods components running under Integration Server. If you encounter a conflict, consider using a package class loader instead.
Note:
The webMethods Broker and JNDI provider .jar files are already included in Integration Server. The Universal Messaging .jar files are included in Software AG_directory /common/lib.
![*](icon_task_xpe.png)
To add a third party JMS provider's JMS and JNDI libraries to the
Integration Server classpath
1. Copy your JMS provider's Java API libraries from the locations specified below and place them in Integration Server_directory \instances\instance_name\lib\jars\custom directory.
JMS Provider | Files to Copy |
Apache ActiveMQ | ActiveMQ_HOME\activemq-all-5.4.*.jar Where ActiveMQ_HOME is the directory in which Apache ActiveMQ is installed |
AMQP message formats | From Apache QPID library: apache-qpid-jms-amqp-0-x-6.3.3-bin.tar.gz OR apache-qpid-jms-amqp-0-x-6.3.3-bin.zip |
IBM MQ | For IBM MQ version 8.0: IBMMQ\Java\lib\com.ibm.mq.allclient.jar IBMMQ\Java\lib\fscontext.jar IBMMQ\Java\lib\providerutil.jar IBMMQ\Java\lib\jms.jar Where IBMMQ is the directory in which your IBM MQ is installed. |
JBoss Messaging | ![*](chapterTOC_bullet.png) jboss-messaging-client.jar (This is available in the JBoss Messaging distribution.) JBOSS_HOME\client\jbossall-client.jar JBOSS_HOME\server\ SERVER_NAME\deploy\jboss-aop.deployer\jboss-aop.jar JBOSS_HOME\server\ SERVER_NAME\lib\javassist.jar JBOSS_HOME\server\ SERVER_NAME\lib\trove.jar Where JBOSS_HOME is the directory in which JBoss is installed and SERVER_NAME is the name of the messaging server Note: JBoss Messaging 1.4.0 requires a patched version of jboss-remoting.jar. |
Oracle Streams Advanced Queuing (AQ) | For Oracle Streams Advanced Queuing (AQ) 10.2.*: ORACLE_HOME\jdbc\lib\classes12.jar ORACLE_HOME\jlib\orai18n.jar ORACLE_HOME\lib\xmlparserv2.jar ORACLE_HOME\rdbms\jlib\xdb.jar ORACLE_HOME\rdbms\jlib\aqapi13.jar ORACLE_HOME\rdbms\jlib\jmscommon.jar Where ORACLE_HOME is ORACLE_BASE\product\10.2.0\db_1 and ORACLE_BASE is the directory in which the Oracle database is installed. For Oracle Streams Advanced Queuing (AQ) 11.2.0: ORACLE_HOME\jlib\orai18n.jar ORACLE_HOME\lib\xmlparserv2.jar ORACLE_HOME\rdbms\jlib\xdb.jar ORACLE_HOME\rdbms\jlib\aqapi.jar ORACLE_HOME\rdbms\jlib\jmscommon.jar ORACLE_HOME\rdbms\jlib\ ojdbc6.jar Where ORACLE_HOME is ORACLE_BASE\product\11.2.0\db_1 and ORACLE_BASE is the directory in which the Oracle database is installed. Note: If you are using Oracle Streams Advanced Queuing (AQ) 11.2.0 as the JMS provider, the value of the watt.config.systemProperties property must include "oracle.jms.conservativeNavigation=true". For Oracle Streams Advanced Queuing (AQ) 12.2.0: ORACLE_HOME\jdbc\lib\ojdbc8.jar ORACLE_HOME\jlib\orai18n.jar ORACLE_HOME\lib\ xmlparserv2.jar ORACLE_HOME\rdbms\jlib\aqapi.jar ORACLE_HOME\rdbms\jlib\jmscommon.jar ORACLE_HOME\rdbms\jlib\ xdb.jar Where ORACLE_HOME is ORACLE_BASE\product\12.2.0\db_1 and ORACLE_BASE is the directory in which the Oracle database is installed. |
SonicMQ | For SonicMQ version 7.5: SonicMQ_directory\lib\mfcontext.jar SonicMQ_directory\lib\sonic_Client.jar SonicMQ_directory\lib\sonic_Crypto.jar SonicMQ_directory\lib\sonic_mgmt_client.jar SonicMQ_directory\lib\sonic_Selector.jar SonicMQ_directory\lib\sonic_XA.jar For SonicMQ version 7.6, all of the above, plus: SonicMQ_directory\lib\mgmt_client.jar SonicMQ_directory\lib\mgmt_config.jar SonicMQ_directory\lib\sonic_XMessage.jar Where SonicMQ_directory is the directory in which SonicMQ is installed. |
WebLogic | For WebLogic 9.1 and 9.2: WebLogic_directory\server\lib\weblogic.jar For WebLogic 10.3 and 12.1.3: WebLogic_directory\server\lib\wljmsclient.jar WebLogic_directory\server\lib\wlnmclient.jar WebLogic_directory\server\lib\wlclient.jar Where WebLogic_directory is the directory in which WebLogic is installed. |
WebSphere Application Server | For WebSphere Application Server version 8.5: WebSphereApplicationServer\AppServer\runtimes\com.ibm.ws.ejb.thinclient_8.5.0.jar WebSphereApplicationServer\AppServer\runtimes\com.ibm.ws.orb_8.5.0.jar WebSphereApplicationServer\AppServer\runtimes\com.ibm.ws.sib.client.thin.jms_8.5.0.jar Where WebSphereApplicationServer is the directory in which your WebSphere Application Server is installed. |
2. Restart Integration Server.
Note:
The list of files for each JMS provider is a general guideline. The requirements for each JMS provider may change. Make sure to review the documentation for your JMS provider to determine an exact list of required jar files. Furthermore, review your chosen JMS provider documentation to determine how to handle fixes and updates to the JMS provider’s Java client libraries. Updates or fixes to the Java client libraries may require updates to the provider client libraries added to the Integration Server classpath.