About JMS Listener data instances

JMS listeners provide the information needed to route Java Message Service (JMS) messages from a specific topic or queue to a JMS service rule. 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.

The following tabs are available on this form:

Both JMS messaging domains are supported: publish-and-subscribe (including durable subscriptions) and point-to-point.

Listener types

JMS listeners can be implemented in one of two ways:

  • When your system is deployed as a Web application, the listener runs as a Java thread, created when the system 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 the system issued a request for it to stop running. If your system is deployed as a Web application, configure JMS listeners with this JMS Listener form.
  • When your system is deployed as an enterprise application, the listener is a message-driven bean (MDB) deployed inside your PegaRULES application. The MDB routes messages to the JMS service rule. If your system is deployed as an enterprise application, configure your JMS listeners with the JMS MDB Listener form ( Data-Admin-Connect-JMSMDBListener ). 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 EJB deployment descriptor file. For deployment instructions, see the PDN article How to deploy a JMS Listener as a message-driven bean.

For more information, see PDN article Using MQ and JMS services with Enterprise Application deployment.


To review or create JMS Listener data instances, use the Records Explorer.


You can create a JMS Listener data instance with the Service Wizard when creating JMS service rules.


The Data-Admin-Connect-JMSListener class holds JMS Listener data instances. They are part of the Integration-Resources category.

Associated ruelset

When you save a JMS Listener data instance, the system automatically associates ("tags") it with the ruleset of the Application rule for the current application. This association assists with application packaging. You can update the associated ruleset using the field in the upper right corner of the form. See Identifying parts of rule and data forms.

When you open the form for an existing instance that has not been previously associated with a ruleset, the system automatically displays an associated ruleset in the form; however, the rulesetinformation is not saved with the instance until you manually save the form.