Using SSL with JMS
If the connection between a JMS application and the
Broker is secured through SSL, you first need to configure and enable SSL on the
Broker Server. That process is detailed in
Configuring SSL for
Broker Server .
You can then use My webMethods to configure SSL for a JMS application. This process involves configuring the connection factory that will be used to connect to the Broker Server, and consists of:
Identifying the keystore file (repository of the SSL certificate) for the JMS application. This certificate file contains the JMS client application's SSL identity (also referred to as its SSL user identity). Since keystores are password protected, so you will need access to the JMS client keystore's password to configure it for SSL.
Identifying the trust store file (repository of the trusted root of the SSL certificate) for the JMS application. This certificate file contains the SSL identity of the certification authority, or CA, of the JMS client's certificate (also referred to as its SSL authorization identity).
For configuration instructions, see
Managing Connection Factories.
When creating durable subscribers and queue clients for SSL-secured JMS applications, you will need to supply the SSL user and authorization identities for the JMS application (these are both SSL distinguished names). You need to have administrative access to the client's keystore file to obtain this information. For more information, see
Keystore File.
For information about using the JMSAdmin command-line utility to configure SSL for JMS, see the webMethods Broker Messaging Programmer’s Guide.