You are here: Reference > Data classes > JMS Listener data instances > More about JMS Listener data instances

More about JMS Listener data instances

  1. About 
  2. New 
  3. Listener Properties 
  4. JMS Properties 
  5. History 
  6. More... 

EAR versus WAR deployment

JMS listeners operations depend on whether Pega Platform is deployed as an Enterprise application (EAR file) or a Web application (WAR file). See PDN article Using MQ and JMS Services with Enterprise Application deployment, regarding EAR deployment and polling.

When and how JMS listeners run

Three settings affect how email listener requestors run. If your listener is not behaving the way you expect, examine the following:

Application Properties for Request Messages

Pega Platform provides four application-specific JMS properties that the sender can use to provide information about the messages that are consumed by Pega Platform JMS services.


This JMS property identifies the third key part of a JMS service rule. You can use this property in the following two ways:

PegaRULES_UserID and PegaRULES_Password

These properties identify the user name and password of a valid user.

Typically, if the message-driven bean and the service rule are to run as an authenticated user, you specify the appropriate user on the JMS Properties tab of the JMS Listener form. Values provided in the message with the PegaRULES_UserID and PegaRULES_Password properties override the values specified on the JMS Properties tab.


When a JMS service sends a reply in response to a message, the listener uses this property to specify the ID of the session used by the requestor that processed the original message. If the sending application sends a reply in response to the service's response, it can use this property to specify that the same session be used to process this message. This mechanism allows the sending application and the JMS service to conduct stateful sessions.

Application Properties for Response Messages

When the service rule is configured to send a response, the listener adds property values for the following Pega Platform application-specific JMS properties to the message:

The listener also sets a value in the JMSCorrelationID message header. By default, this value is copied from the JMSMessageID field from the request message.

About JMS Listener data instances