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

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

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

Determine which of two listener types is appropriate

JMS listeners can be implemented in two ways:

• When PRPC is deployed as an enterprise application, the listener is a message-driven bean (MDB) deployed inside your PRPC application. The MDB routes messages to the JMS service rule. If your PRPC 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 PRPC EJB deployment descriptor file. For deployment instructions, see PDN article How to deploy a JMS Listener as a message-driven bean.
• 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 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 PRPC is deployed, see PDN article Using MQ and JMS services with Enterprise Application deployment.

Access

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

Category

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

Associated RuleSet

When you save a JMS MDB listener data instance, if the Associated RuleSet is [none], the system completes this field with a RuleSet from 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.

If there is no RuleSet associated with the data instance (for example, for existing instances not previously associated with a RuleSet), the Associated RuleSet displays [none].

Integration-Resources category
Help Home