Table of Contents

Tracer best practices


Only available versions of this content are shown in the dropdown

Use Tracer best practices to make tracing easier and more efficient.

Trace only one requestor session per operator and node

Do not attempt to start the Tracer when another requestor session on the same Pega Platform node is using the same Operator ID, or is running the Tracer.

Turn off HTTP compression

Ordinarily, Pega Platform uses HTTP compression to reduce the length of text messages sent to Internet Explorer. HTTP compression is also used in SOAP messages. This might complicate Tracer debugging because compression makes it difficult to interpret the messages.

To disable HTTP compression, edit the prconfig.xml file or dynamic system setting and set the value of the Tracer setting enable-compression setting to "false." This change takes effect the next time your system starts.

Reset this value to enable compression when debugging is complete.

Domain Name System lookups required

In some Pega Platform installations, the ClientHostName value appears only as a numeric Internet Protocol (IP) address. The true ClientHostName is visible only when the application server is enabled to perform Domain Name System lookups:

  • For Tomcat-based systems, set the parameter enableLookups (in the server.xml file) to "true" to allow DNS lookups.
  • For Oracle Weblogic, add the parameter ReverseDNSAllowed="true" to the config.xml file to allow DNS lookups.
  • Duplicate trace error

    If the node hosting your trace session fails and you attempt to trace the same service again, you might encounter a duplicate trace error. Clear stale trace sessions using Admin Studio.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.