Question

6
Replies
686
Views
 Abhijith Kolanakuduru (EatDrinkBreathePega)
Telstra
Abhijith Kolanakuduru
Telstra
AU
EatDrinkBreathePega Member since 2016 15 posts
Telstra
Posted: May 15, 2017
Last activity: May 21, 2017
Posted: 15 May 2017 22:41 EDT
Last activity: 21 May 2017 22:17 EDT
Closed

JMS on Tomcat with SSL

We are using JMS on Tomcat. Everything works fine with tcp but listeners won’t work with SSL. Any thoughts on crucial steps what we might be missing? Appreciate your help.

***Updated by moderator: Lochan to add Categories***

Data Integration System Administration
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.
Posted: 4 years ago
Posted: 16 May 2017 23:11 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Software Solutions Engineering
Pegasystems Inc.
US

What is your JMS provider? What is your pega version? What type of listeners are you using? (e.g., MQ listener, or ActiveMQ JMS listener?)
Posted: 4 years ago
Posted: 17 May 2017 20:51 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Software Solutions Engineering
Pegasystems Inc.
US

Can you attach the complete logs what kinds of SSL errors you are seeing? I wonder if it has to do with generic SSL truststore setup errors.
Posted: 4 years ago
Posted: 21 May 2017 20:22 EDT
Abhijith Kolanakuduru (EatDrinkBreathePega)
Telstra
Abhijith Kolanakuduru
Telstra
AU

Quick update on this. Following changes fixed our issue.


  1. Following custom properties on JNDI Server rule
    1. com.tibco.tibjms.naming.security_protocol = ssl

    2. com.tibco.tibjms.naming.ssl_enable_verify_host = false

    3. com.tibco.tibjms.ssl.enable_verify_hostname = false

    4. com.tibco.tibjms.ssl.vendor = entrust

  2. Earlier we have imported the vendor JAR files to DB using import wizard, prior to placing them under /opt/apache-tomcat/webapps/prweb/WEB-INF/lib (our path, this may vary for others), we had to remove these records in the DB from pr_engine_classes table.
Posted: 4 years ago
Posted: 21 May 2017 22:17 EDT
Kevin Zheng (KevinZheng_GCS)
PEGA
Director, Software Solutions Engineering
Pegasystems Inc.
US

Thanks for sharing this. Looks like you got all the info from Tibco docs, right? e.g., the javadoc: https://docs.tibco.com/pub/enterprise_message_service/7.0.1-march-2013/doc/html/tib_ems_api_reference/api/javadoc/com/tibco/tibjms/naming/TibjmsContext.html. Also the reason you had to pull the jars out of pega database is due to some conflicts?