Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

About JMS MDB Listener data instances (Data-Admin-Connect-JMSMDBListener)

Updated on April 6, 2022

JMS listeners provide Pega Platform with the information it needs to route Java Message Service (JMS) messages from a specific topic or queue to a Pega Platform JMS service ( Rule-Service-JMS rule type). A JMS listener or JMS MDB listener data instance specifies which queue or topic contains the messages to be consumed and which JMS service rule(s) will process the messages.

Note: Beginning in Pega Platform 8.6, EAR deployments of Pega Platform are deprecated. In the upcoming 8.7 release, EAR deployments will not be supported. As a result, in Pega Platform 8.7, JMS MDB Listener data instances will also no longer be supported. For more information on the alternatives for EAR-related rules, see Deprecation of EAR deployments in Pega Platform 8.6.

The following tabs are available on this form:

Pega Platform supports both JMS messaging domains: publish-and-subscribe (including durable subscriptions) and point-to-point.

Determining the appropriate listener type

JMS listeners can be implemented in two ways:

  • When Pega Platform is deployed as an Enterprise application, the listener is a message-driven bean (MDB) deployed inside your Pega Platform application. The MDB routes messages to the JMS service rule. If your Pega Platform system is deployed as an enterprise application, configure JMS MDBs with this JMS MDB Listener form. You use the form to configure the listener and to generate a fragment of the EJB deployment descriptor file that describes the MDB. Insert the fragment into the message-driven beans subsection of the Pega Platform EJB deployment descriptor file. For deployment instructions, see the Pega Community article How to deploy a JMS Listener as a message-driven bean.
  • When Pega Platform is deployed as a Web application, the listener runs as a Java thread created when Pega Platform starts. The listener waits for incoming messages on the JMS destination (queue or topic). At regular intervals (as specified on the listener form), the listener checks to see if Pega Platform has issued a request for it to stop running. If your Pega Platform system is deployed as a Web application, configure JMS listeners with the JMS Listener form ( Data-Admin-Connect-JMSListener ), not this form.

For more information about the differences in the way listeners work based on how Pega Platform is deployed, see the Pega Community article Using MQ and JMS services with Enterprise Application deployment.


Use the Records Explorer to review or create JMS MDB listener data instances.


The Data-Admin-Connect-JMSMDBListener class contains JMS MDB listener data instances. They are part of the Integration-Resources category.

  • Previous topic More about JMS Listener data instances
  • Next topic JMS MDB Listener data instances - Completing the New or Save As form

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us