You can use the Tracer to monitor any active requestor
session. However, a service usually runs in a new requestor
session with a requestor ID that is not created until the
service begins processing. At that point, the processing a
service performs occurs so quickly (less than one second) it
can be hard to catch the event to trace it. Therefore, use the
Trace Open Rule feature to trace service rules.
The Tracer offers the following trace options for
services:
- Services — the Tracer adds
steps for when the service invocation begins and ends. Nested
within those steps are entries that show when the inbound
data mapping begins and ends, and when the outbound data
mapping begins and ends.
- Parse Rules — The Tracer
adds steps when a parse rule (delimited, structured, or XML)
begins and ends processing.
- Stream Rules — The Tracer
adds steps when an HTML rule or XML Stream rule begins and ends
processing.
You can use the Trace Open Rule feature while unit testing
the rule and to trace a service request that is invoked from
the external client application.
- Open the service rule. Note which RuleSet it belongs to.
- Select Run > Trace Open Rule. The Tracer
tool window opens.
- Click
to open the Options
panel.
- Select Services in the Rule
Types area.
- In the RuleSets to Trace section, select
the RuleSets that contain the service rule and service
activity.
- Click OK to
close the Options panel.
- Run the rule.
- Watch the Tracer as the rule runs. The window includes
lines for the start and end of each service rule execution,
lines for the start and end of request mapping, lines for the
start and end of response mapping, and (if selected) lines
for the start and end of parse rules, XML Stream rules, and HTML
rules.
For more information about tracing and testing services, see
Testing Services and Connectors, a
document posted on the Integration section of the Pega
Developer Network.
Setting Tracer options
Unit testing a rule with the
Run Rule feature
Debugging with the
Tracer
Tracer tool