JMS Listener in Tomcat using ActiveMQ jars
Our existing application servers are moving out from websphere to Tomcat.
We do have JMS Listeners that are communicating with ibm mqs using JNDI reference in webshphere.
Once we move to Tomcat, JNDI reference will not be a liable option anymore. We have to use the 'Resource Reference' option. I do see the pdn ref article (https://collaborate.pega.com/question/understand-process-integrate-ibm-websphere-mq-tomcat) where as they are using ibm.mq jars.
Question -
Can't we able to achieve the same using ActiveMQ jar classes? Does Pega supports it?
***Edited by Moderator Marije to add Capability tags***
@KiranR20
Yes, it is possible to integrate ActiveMQ with Pega using the ActiveMQ JMS client libraries. ActiveMQ is a popular open-source message broker that provides JMS (Java Message Service) support, and it can be used to replace IBM MQ as the messaging platform for your Pega application.
To integrate ActiveMQ with Pega, you will need to configure a JMS resource using the Resource Reference option in Tomcat. This resource will include the connection factory and destination information needed to establish a connection to ActiveMQ.
You can then use the JMS Listeners feature in Pega to create JMS listeners that listen for messages on the ActiveMQ destination. These listeners can be configured to process messages using Pega activities, allowing you to easily integrate ActiveMQ messages with your Pega application.
To use the ActiveMQ JMS client libraries in your Pega application, you will need to add the necessary JAR files to your classpath. You can do this by adding the JAR files to your application's lib directory or by configuring your application server to include the JAR files in its classpath.
Overall, Pega supports integration with a wide range of messaging platforms, including IBM MQ, ActiveMQ, and others. The specific steps and requirements for integrating with each platform may vary, but Pega provides a variety of tools and features to help you configure and manage these integrations.