JMS 1.1 SSL Configuration for WebSphere MQ

If you want to use WebSphere® MQ with SSL, you need to create a connection factory with the SSL parameters defined in it.

This connection factory will be used to do a look from JMS 1.1 Adapter. If you need information on how to configure the WebSphere MQ, see the IBM WebSphere documentation on how to create connection factories.

Important: If you are configuring JMS with an SSL Connection for WebSphere MQ, you need the classpath to include all the jars from the server side (WebSphere MQ install). Also, in the WebSphere MQ explorer channel settings you do not select a Cipher Suite.
While configuring SSL for IBM® WebSphere MQ 6.0 the only mode of operation is JNDI. You need to have the following jars in the classpath in this order:
  1. com.ibm.mq.jar
  2. com.ibm.mqjms.jar
  3. fscontext.jar
  4. connector.jar
  5. dhbcore.jar
  6. jta.jar
  7. providerutil.jar

The mq.jar needs to be before mqjms jar in Dynamic Classpath.

While configuring SSL for IBM WebSphere MQ 7.0, the only mode of operation is JNDI. You need to have the following jars in the classpath in this order:

  1. fscontext.jar
  2. com.ibm.mqjms.jar
  3. com.ibm.mq.postcard.jar
  4. jms.jar
  5. com.ibm.mq.jar
  6. com.ibm.mq.headers.jar
  7. com.ibm.mq.jmqi.jar
  8. com.ibm.mq.defaultconfig.jar
  9. providerutil.jar
  10. com.ibm.mq.commonservices.jar
  11. com.ibm.mq.pcf.jar
  12. com.ibm.mq.tools.ras.jar
  13. dhbcore.jar
Additional information:
  • When using WebSphere MQ, the com.ibm.mq.jar needs to be added to the dynamic classpath of SI using install3party script. This needs to be done for both custom class loading and the Sterling B2B Integrator dynamic class loading.
  • Also for WebSphere MQ 7.X, if the SSL does not work properly, you can provide the WebSphere 6.X jars.
  • The same jars can be used in custom class loading or segmented classloader for WebSphere MQ 6.0 and WebSphere MQ 7.0.