Enabling SSL for MQ using JMS MDB Listener
Hi,
we are trying to enable SSL for MQ connection.
JMS MDB listener is used to connect to queues via JNDI server.
Any pointers please.
Ratna.
***Edited by Moderator Marije to add Support Case tags***
Pegasystems Inc.
GB
@Ratna To enable SSL for an MQ connection using JMS MDB listener, you need to configure the SSL settings in your application server and JNDI server. Follow these steps: Configure the SSL settings in your application server, such as WebSphere, WebLogic, or JBoss. This typically involves setting up a keystore and truststore, importing the required certificates, and configuring the SSL protocol and cipher suites. Update the JNDI server configuration in Pega Platform to include the necessary SSL properties. You can do this by adding the SSL-related properties to the 'Additional JNDI Properties' section of the JNDI server data instance (Data-Admin-Connect-JNDI class). Update the JMS MDB listener configuration to use the SSL-enabled JNDI server. Make sure the JNDI server field in the JMS MDB listener data instance (Data-Admin-Connect-JMSMDBListener class) points to the updated JNDI server. After completing these steps, your JMS MDB listener should be able to connect to the MQ server using SSL.
Scotia Bank
CA
@MarijeSchillern we are using binding file to connect to MQ.
I have tried the customer properties option but no success.
Could you please share any thoughts on how we can achieve with binding file.
Ratna.
Pegasystems Inc.
GB
@Ratna I am not an SME - did you check other posts such as this one and this one?
I also found that you already logged a support incident INC-A2691 for this with our Global Client Support team: (MQ SSL connection with JNDI connectivity).
In June our team assessed your question. Closure info provided:
"During the screen share client has showed the configurations which are take place for the new change for JMS lookup with JNDI and having security SSL .
As mentioned in the call the MQ definition file and .bindings file is used to contain information on connection factories, queues and topics configuration those ae not managed and not in the scope of platform .
Next Steps:Clients should contact their MQ team for more assistance with updating MQ definitions and bindings"
Did you get any help from the third party vendor?