Try OpenEdge Now
skip to main content
Messaging and ESB
Working with the Generic JMS Adapter : Configuring and administering the Generic JMS Adapter : Updating the classpath for your JMS Provider
 

Updating the classpath for your JMS Provider

To use a JMS provider other than SonicMQ, you have to replace the references to the Sonic client JAR files with your provider JAR files. To do this, open %DLC%\properties\ AdminServerPlugins.properties in a text editor and add the location of the client JAR files of your JMS provider to the pluginclasspath and the classpath properties. In the following example, com.ibm.mqjms.jar is the WebSphereMQ JMS client jar that is appended to the pluginclasspath and the classpath properties.
PluginPolicy.Progress.SonicMQ]

pluginclasspath=C:\Progress115\OpenEdge/java/progress.jar,
C:\PROGRA~2\IBM\WEBSPH~1\java\lib\com.ibm.mqjms.jar

classpath=C:\Progress115\OpenEdge/java/progress.jar,
C:\PROGRA~2\IBM\WEBSPH~1\java\lib\com.ibm.mqjms.jar

jvmargs=-DsonicMQExtensions=false -DjmsProvider=WebSphereMQ
Note: SonicMQ is a string in the section header and PluginPolicy.Progress.SonicMQ is the name of the plug-in that OpenEdge provides, not the SonicMQ provider.
The provider JAR files are added to the classpath, and the run-time picks up the provider-specific connection factory objects.