Learn about the ways in which you can monitor the performance of your Service SOAP rules and debug these rules if necessary. By understanding how to debug your Service SOAP rules, you can troubleshoot errors and improve performance.
Debugging with TCPMon
Use the Tracer to debug Service SOAP rules. A proxy server such as TCPMon, part of the Apache Axis toolkit, shows you the content of the SOAP messages.
HTTP messages sent by Pega Platform might be compressed and difficult to review in Tracer and TCPMon displays. You can turn off data compression. For more information, see Tracer best practices.
To start TCPMon, install Axis on your workstation and create a Windows BAT file similar to the following:
User instructions are available on the Apache Axis site. You can run TCPMon on any computer and modify the SOAP client to send the SOAP request to the host and port on which TCPmon runs. After TCPMon receives the request message, it forwards the message to the endpoint that you specify to TCPMon.
To see the full text of the request and response messages, use the Set Logging Levels
tool to set logging for this Java class to
INFO. For more
information, see Log levels for log categories.
Through changes to the
prlog4j2.xml file, you can obtain
performance statistics on the execution of services. See Performance tool — Statistics for services in the SERVICES-PAL log.
Through changes to the prconfig.xml file, you can be alerted to unusually long SOAP service operations. See How to detect lengthy service operations.
As an alternative to updating the prconfig.xml file, you can use dynamic system settings to configure your application. See Configuring dynamic system settings.