Listeners operate as Java threads rather than as full requestors, and so cannot be accessed with the Tracer. Accordingly, use logs to debug listeners.
You can examine the log files by clicking Designer Studio> System >Operations> Logs> Log Files, or by using the Remote Logging feature to stream the contents of the log file to your workstation. You can watch the log as it grows while running a service rather than opening the log repeatedly.
Follow the steps in the following procedures to configure a listener or service requestor to send log messages to your workstation. Then, using a modified version of the LogFactor5 log analysis module, you can review detailed or filtered messages. (LogFactor5 was an open source project of the Apache Software Foundation.)
To install remote logging client software on your workstation:
startSocketServer.cmd
file. This file starts the LogFactor5 window that displays the contents of the log.startSocketServer.cmd
file and then place it on your desktop. You then can start LogFactor5 with a mouse click.To start the LogFactor5 viewer applet on your workstation, use the startSocketServer.cmd
file on your computer. If you created a Windows shortcut for it, double-click the shortcut. Otherwise, open a Windows command line session, navigate to the directory where you installed it, and double-click the file. The LogFactor5 window appears.
After starting the LogFactor5 viewer, identify your workstation to the system:
Now, run the service, examine the system log file in the LogFactor5 window, and look for messages about the service. If too much information appears, consider using the Filter String field in the Logging and Tracing page.
To capture messages about specific email, file, JMS, or MQ services only, identify yourself as an active logger through the listener form of the listener that listens for that service rule.
If not enough information appears in your LogFactor5 window, add more severity levels in the prlogging.xml file.
The prlogging.xml configuration file defines the levels of logging events. In a multinode system, you can create separate prlogging.xml files for each node.
When you testing services, enable logging for the com.pega.pegarules.services Java package, or use the Logging Level tool to enable logging for this package temporarily.