This section describes how to modify the above samples to use SSL communications between the TIBCO Enterprise Message Service server and WebSphere application server and client container. This section assumes you have already set up and run the samples over unencrypted connections, as detailed in the previous sections.
1. These lines explicitly set the tcp and ssl listen ports and specify the three required server-side SSL parameters: identity, private key, and password.
3. Start the TIBCO EMS server with the -ssl_debug_trace option:See Starting the EMS Server of the TIBCO Enterprise Message Service User’s Guide for more information.When the server restarts you should see messages like the following in the console window confirming SSL is enabled:TIBCO Enterprise Message Service is pre-configured with a sample SSL queue and topic connection factory. This step will create new JNDI names for the sample connection factories that are then be used throughout the rest of this section.
1. Verify that the SSL connection factories exist by starting the tibemsadmin tool and entering the command show factories. The names SSLTopicConnectionFactory and SSLQueueConnectionFactory should be among the names displayed.
2. Create new JNDI names for the existing SSL connection factories by entering the following commands:Locate the jndi.properties file in the WebSphere installation directory:<installation_directory>\properties\jndi.propertiesIf it does not already exist, create a text file called jndi.properties in the directory.Edit the jndi.properties file to add the following lines:These properties specify that the "SSL" protocol should be used for JNDI lookups, and that host verification is turned off (the JMS client will trust any host).Configure SSL Communications Between the Application Server and the TIBCO Enterprise Message Service ServerThis procedure adds the additional JAR files required for SSL to the CLASSPATH. It also modifies the external provider URL and the external JNDI name properties of the TIBCO JMS provider within the application server.This causes the application server to connect to the SSL port on the TIBCO Enterprise Message Service server for JNDI lookups of administered objects. Additionally, the connection factory external JNDI names are modified to specify SSL connection factories (connection factories that create SSL-based connections).
1. From the WebSphere Administrative Console, expand Resources > JMS > JMS providers and choose TIBCO in the content pane.
2. Add the following lines to the Class path property value:
3.
4. Click the OK button.Configure the Topic Connection Factory
5.
6. Select TIBCOConnectionFactory1.
7. For the External JNDI Name property value, change the name of the factory from sample.TCF to sample.SSLTCF.
8. Click the OK button.Configure the Queue Connection Factory
9.
10. Select TIBCOConnectionFactory2.
11. For the External JNDI Name property value, change the name of the factory from sample.QCF to sample.SSLQCF.
12. Click the OK button.
13. Click Save.
1. > java tibjmsTopicPublisher -server ssl://localhost:7243 -topic sample.weather "hello world"
2. > java tibjmsQueueSender -server ssl://localhost:7243 -queue sample.Q1 "hello world 2"
3. Open the WebSphere application server log, located in <installation_directory>\logs\<your server>\SystemOut.log, and verify that the WebSphere MDB consumed the sent messages.
Copyright © TIBCO Software Inc. All Rights Reserved.