About JMS Listener data instances
 

Purpose

C-605 C-759 R-9128 03-05 JMS listeners provide PRPC with the information it needs 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.

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

Listener Types

PRPC JMS listeners can be implemented in one of two ways:

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

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

Access

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

• Select > Integration > Resources.
• Click the JMS Listeners link

Development

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

Category

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

Associated RuleSet

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 RuleSet information is not saved with the instance until you manually save the form.

Integration-Resources category
Help Home