Adding Third Party JMS Provider Client Libraries to Integration Server Classpath
Integration Server has been tested with at least one version of the JMS providers listed in the table in
Supported JMS Providers.
To use third party JMS providers with Integration Server, you need to make some of the JMS provider’s Java client libraries accessible to Integration Server. You can add a third party JMS provider's JMS and JNDI libraries to the Integration Server classpath by doing one of the following:
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.
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.
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.
Make sure to restart Integration Server after placing copies of the JMS provider’s Java client libraries in one of the above locations. Class loading occurs during server initialzation.
The JMS provider's .jar files could potentially conflict with other webMethods components running on Integration Server. If you encounter a conflict, consider using a package class loader instead.
Examples for configuring a version of a supported third-party JMS providers can be found in
Considerations and Example Configuration Information
for Third-Party JMS Providers.
Note:
When using webMethods Broker or Universal Messaging as the JMS provider, you do not need to add the client libraries to Integration Server. 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.