This section describes how to modify the above example to use SSL communications between the TIBCO Enterprise Message Service server, JBoss, and the client program. This section assumes you have already set up and run the example detailed in the previous sections.
The following JAR files, distributed with TIBCO Enterprise Message Service, must be added to the CLASSPATH
of the JBoss server, in the same manner that you added the non-SSL jar files to the JBoss CLASSPATH
in the previous example:
Add the following line under the <server>
element in jms-service.xml
:
<classpath codebase="file://C:\TIBCO\EMS\clients\java" archives="jcert.jar, jnet.jar, jsse.jar, tibcrypt.jar" />
tibemsadmin
:>create factory SSLXAQueueConnectionFactory xaqueue url=ssl://7243This creates a new XAQueueConnectionFactory that establishes SSL connections.
>setprop factory SSLXAQueueConnectionFactory ssl_verify_host=disabledThis turns off host verification for connections created by this connection factory. This is the simplest SSL configuration.
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:7222These lines explicitly set the
tcp
andssl
listen ports and specify the three required server-side SSL parameters: identity, private key, and password.Save the file, stop and restart the TIBCO Enterprise Message Service server. When it restarts you should see messages like the following in the console window confirming SSL is enabled:
2002-03-19 13:48:34 Secure Socket Layer is enabled. 2002-03-19 13:48:34 Accepting connections on ssl://localhost:7243. 2002-03-19 13:48:34 Accepting connections on tcp://localhost:7222.
There are two aspects to SSL communications between JBoss and the TIBCO EMS server. The first is for messaging between the JBoss and TIBCO servers to occur over SSL. The second is for JNDI lookups from JBoss to the TIBCO JNDI provider to occur over SSL. The following two sections separately describe the required steps for each.
jms-service.xml
in the previous section which specifies the QueueFactoryRef
attribute of the JMS Provider Loader to be the be the new connection factory you just created that establishes SSL connections:jms-service.xml
in the previous section to create the JNDI LinkRef ToName
to the new connection factory:%JBOSS_CONF%\jndi.properties
, add the following line: com.tibco.tibjms.naming.security_protocol=sslThis property specifies that the "SSL" protocol should be used for JNDI lookups.
JMSProviderLoader
mbean in jms-service.xml
:<attribute name="ProviderUrl"> tibjmsnaming://localhost:7243</attribute>The new line creates an additional attribute
ProviderUrl
, that explicitly states the JNDI provider URL (rather than using the default built into the TIBCO Enterprise Message Service JBoss adapter class) with a port number of 7243 for SSL. Note that attribute names are case sensitive and must be entered exactly as shown above.
jms-service.xml
to explicitly specify the SSL port of 7243 in the JNDI LinkRef ToName
:You should see the same messages in the JBoss console during startup that you saw in the previous section.
The following JAR files, distributed with TIBCO Enterprise Message Service, must be added to the CLASSPATH
of the client program, in the same manner that you added the non-SSL jar files to the CLASSPATH
in the previous example:
The following changes must be made to the file %JBOSS_CLIENT%\jndi.properties
that you modified in the previous section for the client:
Modify the client program (SendRecvClient
) to look up SSLXAQueueConnectionFactory
instead of QueueConnectionFactory
. Rebuild the program.
Run the client program as you did in the previous section. You should see the same output.
To prove that SSL communications are occurring, you could remove the SSL settings you added to tibemsd.conf
in Configuring the TIBCO Enterprise Message Service Server for SSL, and restart the TIBCO Enterprise Message Service server. Then stop and restart JBoss. You should see the following exception in the JBoss console:
If you now run the test program again, you should see that it throws the same exception. This shows that when the TIBCO Enterprise Message Service server was set up to accept SSL connections, both clients successfully connected and communicated using SSL.
Alternatively, you could start the TIBCO Enterprise Message Service server from a command prompt window and turn SSL debug tracing on, as follows:
Then when you restart JBoss and re-run the client 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 |