|
|
MQ listeners provide PRPC with the information it needs to route WebSphere MQ messages from a specific queue to an MQ service rule. An MQ listener specifies which queue contains the messages to be consumed and which MQ service rule(s) are to process the messages.
When a message is delivered to the queue, the listener forwards the message to a Service MQ rule. After the corresponding service activity runs, the listener may send a response message to a specified response queue. If the listener is configured to use transacted messaging and the MQ service fails to process the message successfully, the listener requeues the message for another attempt at processing or routes the message to a backout queue.
You can use MQ listeners with MQ services only when PRPC is deployed as a Web application. When PRPC is deployed as an enterprise application, you use a message-driven bean (MDB) as the listener for message-based services — that is, JMS and MQ. So although you can use WebSphere MQ as a JMS service provider, use only JMS MDB listeners with JMS service rules, rather than MQ listeners with MQ services, when PRPC is deployed as an enterprise application.
Note: JMS MQ listeners, unlike other listeners, cannot be managed using the remote System Management Application, but only through the local Admin Console.
For more information about differences in the way listeners work based on how PRPC is deployed, see PDN article Using MQ and JMS services with Enterprise Application deployment.
Because the first key part of an MQ listener is the name of an MQ server data instance, be sure to create an MQ server instance first.
Select 
> Integration > Resources and select the MQ Listeners link to access the MQ Listeners in your system. Or, you can use the Records Explorer to review or create MQ Listeners.
The Data-Admin-Connect-MQListener class contains MQ listener data instances. This class is part of the Integration-Resources category.
When you save an MQ listener, 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.
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.
About MQ Listener data instances
Integration-Resources category
Help Home