Products | Versions |
---|---|
TIBCO Web Messaging for TIBCO Enterprise Message Service | - |
Not Applicable | - |
Resolution:
Resolution:
============
In the "stomp.jms service" section in gateway-configy.xml, add the following:
---------
<env.java.naming.factory.initial>com.tibco.tibjms.naming.TibjmsInitialContextFactory</env.java.naming.factory.initial>
<env.com.tibco.tibjms.naming.security_protocol>ssl</env.com.tibco.tibjms.naming.security_protocol>
<env.java.naming.provider.url>ssl://localhost:7243</env.java.naming.provider.url>
<!-- Server authentication -->
<env.com.tibco.tibjms.naming.ssl_enable_verify_host>true</env.com.tibco.tibjms.naming.ssl_enable_verify_host>
<env.com.tibco.tibjms.naming.ssl_trusted_certs>c:\tibco\ems\5.0\samples\certs\server_root.cert.pem</env.com.tibco.tibjms.naming.ssl_trusted_certs>
<!-- Use a name other than the EMS server host name -->
<env.com.tibco.tibjms.naming.ssl_enable_verify_hostname>
true</env.com.tibco.tibjms.naming.ssl_enable_verify_hostname>
<env.com.tibco.tibjms.naming.ssl_expected_hostname>server</env.com.tibco.tibjms.naming.ssl_expected_hostname>
<!-- Client authentication -->
<env.com.tibco.tibjms.naming.ssl_identity>
c:\tibco\ems\5.0\samples\certs\client_identity.p12</env.com.tibco.tibjms.naming.ssl_identity>
<env.com.tibco.tibjms.naming.ssl_password>password</env.com.tibco.tibjms.naming.ssl_password>
<env.com.tibco.tibjms.naming.ssl_trace>true</env.com.tibco.tibjms.naming.ssl_trace>
---------
The above configuration is based on sample certificates which can be found under <ems_home>/samples/certs and the sample tibemsdssl.conf under <ems_home>/samples/config.
All SSL properties for JNDI can be found in class "com.tibco.tibjms.naming.TibjmsContext" in EMS java API.
===========
Environments:
============
All