If the connection between Integration Server and the JMS provider is secured through SSL, you must configure and enable SSL on the JMS provider.

When connecting to the JMS provider using JNDI (the JMS connection alias specifies JNDI Lookup), configure SSL on the JMS provider. Specifically, configure the connection factory that will be used to connect Integration Server to the JMS provider. For more information, refer to the documentation for the JMS provider.

Some JMS providers require that JMS clients use the JVM default SSL context for the SSL handshake. To do this, JMS client must set the keystore location, truststore location, and password information using the javax.net.ssl properties for the JVM. However, these properties take String values which can result in storing password information in plain text somewhere on the file system. If you do not want to store password information in plain text, you can assign a keystore alias and/or trusstore alias to be used by the JVM when establishing the default SSL context. At start up, Integration Server sets the javax.net.ssl properties by obtaining the store locations and passwords from the aliases and then creates the default SSL context. For more information, see Configuring SSL Information for the Integration Server JVM.

When connecting to the webMethods Broker using the native webMethods API, configure SSL information (Keystore, Keystore Type, Truststore, and Truststore Type) when you create the JMS connection alias.