This section describes how to use SSL in your Universal Messaging client applications. Universal Messaging supports various wire protocols (see Communication Protocols and RNAMEs) including SSL enabled sockets and HTTPS. The example programs contained in the Universal Messaging package will all work with SSL enabled on the realm server.

This guide explains client SSL configuration on Java. Guides for C++ and C# are also available.

Once you have created an SSL enabled interface for your realm (see the description of how to do this in the section "Creating an SSL network interface" of the Enterprise Manager documentation), you need to ensure that your client application passes the required System properties used by your JSSE-enabled JVM. The Universal Messaging download contains some example Java keystore files that will be used in this example.

The first such keystore is the client keystore, called client.jks, which can be found in your installation directory, under the client/<umserver>/bin directory. The second is the CA keystore called nirvanacacerts.jks, which is again located in the client/<umserver>/bin directory. On Windows, these keystore files exist once you run the 'Server/<umserver>/Create Demo SSL Certificates' shortcut .

If you would like to add your own client certificates please see the section "How to generate certificates" of the Enterprise Manager documentation.

Using the example keystores, the following system properties are required by the Universal Messaging sample apps and must be specified in the command line as follows:

where:

CKEYSTORE is the client keystore location

CKEYSTOREPASSWD is the password for the client keystore

CAKEYSTORE is the CA keystore file location

CAKEYSTOREPASSWD is password for the CA keystore

The above system properties are used by the Universal Messaging sample apps, but are mapped to system properties required by a JSSE-enabled JVM by the utility program 'com.pcbsys.foundation.utils.fEnvironment', which all sample applications use. If you do not wish to use this program to perform the mapping between Universal Messaging system properties and those required by the JVM, you can specify the SSL properties directly. To do this in your own applications, the following system properties must be set:

where :

javax.net.ssl.keyStore is the client keystore location

javax.net.ssl.keyStorePassword is the password for the client keystore

javax.net.ssl.trustStore is the CA keystore file location

javax.net.ssl.trustStorePassword is password for the CA keystore

As well as the above system properties, if you are intending to use https, both the Universal Messaging sample apps and your own applications will require the following system property to be passed in the command line:

As well as the above, the RNAME (see Communication Protocols and RNAMEs) used by your client application must correspond to the correct type of SSL interface, and the correct hostname and port that was configured earlier.

In JMS, the RNAME corresponds to a JNDI reference. The example JMSAdmin application can be used to create a sample file based JNDI context, where the RNAME is specified as the content of the TopicConnectionFactoryFactory reference. Once your SSL interface is created you can simply change this value in your JNDI context to be the RNAME you require your JMS applications to use.