JMS MDB Listener form
Completing the Listener Properties tab

Field

Description

Use the Service Package, Service Class, and Service Method fields to identify which JMS service rules (Rule-Service-JMS) are to process the messages this listener retrieves. Use the Service Package field to specify the first key part — the Customer Package Name — of the rule.

Optional. Select the second key part — Customer Class Name — of one or more Service JMS rules within the package identified. This listener ignores messages that reference other classes within the package.

If this field is blank, the listener uses the PegaRULES_ServiceClass property in the request message as the second key part.

Optional. Enter the third key part — Customer Method Name — of the Service JMS rule that will process the requests. This listener ignores messages that reference other methods within the Service Class and Service Package.

If this field is blank, the listener uses the PegaRULES_ServiceMethod property in the request message as the third key part.

If selected, and a processing error occurs that is not handled by a configured response message, the listener responds with a text message that contains the error message.

Error messages can be sent only if the sender of the message identified a Reply To queue in the JMSReplyTo header field of the message. The queue specified in the header field must be located on the server specified in the JNDI Server field on the JMS Properties tab of this listener.

This option is disabled if you select No Reply as the Preference on the JMS Properties tab.

Select to generate the MDB deployment descriptor with transaction attributes that cause message redelivery in the case of processing failure. This allows the PRPC service to re-process the message.

Optional. If the service rule is to run as an authenticated user, specify the name of an Operator ID record to use for authentication.

Optional, but required if an Operator ID is specified in the Requestor User ID field. Enter the password for the operator specified in the Requestor User ID field.

The remote logging feature streams the contents of the Pega log file to the LogFactor5 application installed on your workstation. For information about this feature, see How to install and use remote logging.

To view only those log messages that are about the service rule this listener listens for, complete the fields in this section. Remember to start the LogFactor5 application on your workstation before updating this form to identify your workstation as a logger.

Optional. To use the remote logging feature, specify the server name of your workstation.

Optional. To use the remote logging feature, specify the TCP/IP port number of the port where the log4j Socket Server applet listens. The default port is 8887.