About JMS Listener data instances
|
|
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.
PRPC JMS listeners can be implemented in one of two ways:
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.
To review or create JMS Listener data instances, use the Records Explorer, or
You can create a JMS Listener data instance with the Service accelerator when creating JMS service rules. See About the Service accelerator.
The Data-Admin-Connect-JMSListener class holds JMS Listener data instances. They are part of the Integration-Resources category.
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.