Portlet Factory, Version 6.1.2
About using system tracing
Use the system tracing feature to store the WebApp execution path and the execution time for each action (Page or Method).
The stored information is written to the console upon completion of the request. It can also be written to an event log file found in the MyApp\logs directory. When you activate system tracing and run a model, system trace control records the amount of time it took to run through each of the action builders in a model.
Use system tracing to trace only one model at a time. This will help you to narrow down performance problems within a model. You can also use Log4j tracing.
The system can only perform tracing on actions that are called through the WebAppAccess methods callMethod() and processPage(). If you call a method directly from another method, the tracing is bypassed and cannot be automatically tracked. You can add tracing manually to an internal web application method or a linked Java object method. To manually do this, use the WebAppAccess method addSystemTrace() to add the start of a trace.
{ SystemTrace trace = webAppAccess.addSystemTrace(SystemTrace.METHOD, "in My Method"); ... do some work; trace.endTrace(); }And to end the trace, use the SystemTrace endTrace() method. To determine which event log contains the tracing information, look at the file name of the event log. The file name contains the date and the time it was created. For example, the following file was created at 10:29 P.M. (22.29) on November 22, 2001.
event_11.22.2001.22.29.29.699.logNotice the time is based on the 24-hour clock.
Parent topic: Overview: debugging an application
- Deciphering error logging displayed in the command prompt window: example
This topic represents log output that shows a list of actions performed and the milliseconds used for those actions.
- Starting system tracing
Follow these steps to start system tracing.
Library | Support |