Configuring a shared "JNDI Configuration" activity using SSL for all "JMS Connection".
Article ID: KB0093197
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix BusinessWorks | - |
| Not Applicable | - |
Description
Description:
If a "JMS Connection" uses both JNDI and SSL, copying its "JNDI Context URL" to use in "JNDI Configuration" activity would fail with the error, "Failed to query JNDI: Failed to connect to the server at tcp://localhost:7243". The address should be "ssl://localhost:7243". To use SSL in "JNDI Configuration", you need to add "Optional JNDI Properties" in the "Advanced" tab .
If a "JMS Connection" uses both JNDI and SSL, copying its "JNDI Context URL" to use in "JNDI Configuration" activity would fail with the error, "Failed to query JNDI: Failed to connect to the server at tcp://localhost:7243". The address should be "ssl://localhost:7243". To use SSL in "JNDI Configuration", you need to add "Optional JNDI Properties" in the "Advanced" tab .
Issue/Introduction
Configuring a shared "JNDI Configuration" activity using SSL for all "JMS Connection".
Resolution
In the "Optional JNDI property", in the "Advanced" tab of the shared "JNDI Configuration", set the following properties.
com.tibco.tibjms.naming.security_protocol -> ssl
com.tibco.tibjms.naming.ssl_enable_verify_host -> false
com.tibco.tibjms.naming.ssl_trusted_certs -> <Full path of the trusted certificate>
com.tibco.tibjms.naming.security_protocol -> ssl
com.tibco.tibjms.naming.ssl_enable_verify_host -> false
com.tibco.tibjms.naming.ssl_trusted_certs -> <Full path of the trusted certificate>
Feedback
Yes
No
Powered by
