Testing and debugging email listeners

Test connectivity

Use the  Test Connectivity   button (on the Email Account tab of the EmailAccount rule) to ping the email server.

Use authentication and the Tracer tool

If your email listener uses authentication, the Tracer tool can trace the requestor it uses. If your email listener does not require authentication, you can add authentication temporarily so you can use the Tracer to track it.

1. Define an Operator ID that has access to all needed RuleSets. For ease in debugging, choose an Operator ID not intended to be used by a human operator.
2. Complete the Requestor User ID and Password fields on the Properties tab and click Save.
3. Start the System Management application. Select the node and select Logging and Tracing.
4. Select the listener. Click  Start   at the top of the panel. Enter a requestor ID and password.
5. Click Requestor Management to see a list of active requestors on this node. Look for the Operator ID of the listener. Select the row corresponding to the listener requestor session and click  Tracer  .

Remote logging

Use the remote logging feature to debug email listeners:

1. On the Properties tab, identify a workstation to receive logging output.
2. Use the System Management application to start the listener.
3. Optionally, use the System Management application to filter which console output messages are sent to the server.

Debugging

To produce detailed output from an email listener, use the Set Logging Level tool the set logging for the following class to DEBUG:

com.pega.pegarules.services.emaillistener

	listener, prconfig.xml file, remote logging
	About the System Management application About Service Email rules How to install and use remote logging

About Email Listener data instances