Question
Prime Therapeutics
US
Last activity: 7 Aug 2018 8:10 EDT
JMS over TLS / SSL
We are planning to integrate with Solace EMS.As per my knowledge Pega won't support TLS/SSL for JMS. I want to know is there any work around for this. We are on Pega 7.2.1 version deployed on WebSphere.
Pegasystems Inc.
IN
Hi,
To make secure while Configuring messaging with JMS, below procedure is taken care.
Ensure that your connectors are secure for the type of integration and for the data that is being transmitted. Security measures include:
- Using a secure tunnel to provide data transport encryption. You can create a secure tunnel by using the following methods:
- Use a VPN connection. On Pega Cloud, this method is available for every provisioned environment.
- Use Amazon Web Services Direct Connect. This method is appropriate if you utilize dedicated carrier networks.
- Full details are available in below link:
Pegasystems Inc.
IN
JMS provider should have TLS/SSL support and all ssl/tls details(e.g. installed certificates, keystore/truststore location) are configured in the app server environment, not Pega.
Need to provide required JNDI properties when integrate with SOlace under custom properties tab in JNDI server rule in pega.
ex:
Solace_JMS_SSL_TrustStoreFormat
Solace_JMS_SSL_TrustStorePassword
Solace_JMS_SSL_TrustStore
you can find the more information of above properties in below link.
https://dev.solace.com/uncategorized/jboss-eap-v6/
Prime Therapeutics
US
Thank you for the details. Then why pega added cert configuration only for Connect-MQ, version 7.2.2 onwards. I have seen some other pdn articles stated that Pega 7 doesn't support JMS over SSL. That is why I got confused. I hope pega will publish good article on this to avoid these confusions. If possible can you please provide configuration steps for WebSphere.