About JMS MDB Listener data instances
About JMS Producer Model data instances
About JNDI Server data instances
About Service Package data instances
About the System Management application
More about Service JMS rules
|
|
When Requires authentication? is specified in the service package instance, the JMS service must run as an authenticated user. To implement this, provide the name and password of a valid Pega 7 Platform operator on the JMS Properties tab of the JMS or JMS MDB listener that manages this rule.
Optionally, you can configure the client application to provide values with the Pega 7 Platform JMS message properties PegaRULES_UserID and PegaRULES_Password. If a request message contains values for these properties, they override the values specified on the JMS Properties tab of the listener.
When the Processing mode on the service package is set to Stateful, and a JMS service sends a reply in response to a message, the listener uses the Pega 7 Platform JMS message property named PegaRULES_SessionID 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 is to be used to process this message. This mechanism allows the sending application and the JMS service to conduct stateful sessions.
If authorized, you can start and stop listener requestors and observe their operations using the Listener Management menu of the System Management application.
Through changes the prlogging.xml file, you can obtain performance statistics on the execution of services. See Performance tool — Statistics for services.
Through changes to the prconfig.xml file, you can be alerted to unusually long service operations. See How to detect lengthy service operations.
As an alternative to the prconfig.xml file, you can use Dynamic System Settings to configure your application.
See How to create or update a prconfig setting.
About Service JMS rules