About MQ Listener data instances

MQ listeners provide the information needed 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.

The following tabs are available on this form:

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 Pega Platform is deployed as a Web application. When Pega Platform 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. 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 Pega Platform is deployed as an enterprise application.

Unlike other listeners, you cannot manage JMS MQ listeners from Admin Studio. You can manage JMS MQ listeners only through the local Admin Console.

For more information about differences in the way listeners, see the Pega Community article Using MQ and JMS services with Enterprise Application deployment.


You can use the Records Explorer to review or create MQ Listeners. Because the first key part of an MQ listener is the name of an MQ server data instance, create an MQ server instance first.


The Data-Admin-Connect-MQListener class contains MQ listener data instances. This class is part of the Integration-Resources category.