This section describes how to modify the above example to use SSL communications between the TIBCO Enterprise Message Service server, the WebLogic Server 8.1, and the client program. This section assumes you have already set up and run the example detailed in the previous sections.
Modify the WebLogic Server 8.1 environment setup script, setExamplesEnv.cmd
in the directory C:\bea\weblogic81\samples\domains\examples
. This script is used to setup the environment to run the examples and the examples WebLogic server.
setExamplesEnv.cmd
.CLASSPATH
and save the file.C:\Tibco\ems\clients\java\jcert.jar;C:\Tibco\ems\clients\java\ jnet.jar;C:\Tibco\ems\clients\java\jsse.jar;C:\Tibco\ems\ clients\java\tibcrypt.jar; C:\Tibco\ems\clients\java
jndi.properties
, add the following lines and save it to the directory C:\Tibco\EMS\clients\java
.com.tibco.tibjms.naming.security_protocol=ssl com.tibco.tibjms.naming.ssl_enable_verify_host=falseThese properties specify that the "SSL" protocol should be used for JNDI lookups and that host verification is turned off (the client will trust any host). JNDI reads this file automatically and adds the properties to the environment of the initial JNDI context.
In C:\Tibco\EMS\bin\tibemsd.conf
, add the following lines:
listen = ssl://localhost:7243 ssl_server_identity = certs/server.cert.pem ssl_server_key = certs/server.key.pem ssl_password = password listen = tcp://localhost:7222
These lines explicitly set the tcp and ssl listen ports and specify the three required server-side SSL parameters identity, private key, and password.
Save the file, then stop and restart the TIBCO Enterprise Message Service server. When the server restarts, you should see messages like the following in the console window confirming SSL is enabled:
2003-06-14 10:00:05 Secure Socket Layer is enabled, using openSSL <version
> 2003-06-14 10:00:05 Accepting connections on ssl://<machineName
>:7243. 2003-06-14 10:00:05 Accepting connections on tcp://<machineName
>:7222.
In the web browser load the page, http://<
machineName
>:7001/examplesWebApp/index.jsp
. Click on the Administration Console link. Enter weblogic
as the Username and Password and click Sign In.
tibjmsnaming://localhost:7243
. Click Apply.TIBCO.tcf
and the contents of the Remote JNDI Name box with SSLTopicConnectionFactory
. Click Apply.The modifications necessary for the example client program are similar to those that were necessary for MDB:
Restart the WebLogic Server Examples Server so that it picks up the SSL related changes to the environment.
From the example MDB source directory, enter the command:
As the build completes, you should see messages in the WebLogic Server Examples Server window indicating that it is activating the "message" application.
Create a new command prompt window and run the examples setup script, setExamplesEnv.cmd
, so that the SSL related changes to the environment are picked up.
From the example MDB source directory, enter the command:
You should see the same messages sent by the client and received by the MDB in the WebLogic server window. You may notice that this example runs slightly slower than the non-SSL version. This is because of the SSL handshake that occurs before the messages are displayed.
To show that SSL communications are in fact occurring, you could remove the SSL settings you added to tibemsd.conf
. Then restart the TIBCO Enterprise Message Service server and the WebLogic Server. If you check the WebLogic Server logs, you should see exceptions thrown indicating that it could not connect. If you now run the test program again, you should see that it throws an exception indicating that it could not connect to the server using the SSL protocol. Alternatively (or additionally), you could start the TIBCO Enterprise Message Service server from a command prompt window and turn SSL debug tracing on, as follows:
Then, if you re-start WebLogic Server and re-run the test program, you will see SSL debugging output on the tibemsd
console window.
TIBCO Enterprise Message Service™ Application Integration Guide Software Release 4.3, February 2006 Copyright © TIBCO Software Inc. All rights reserved www.tibco.com |