Enabling and viewing trace logs

Configure trace logging to collect and record information about application failures in test or production environments.

Enabling trace logging

After you enable trace logging for a subsystem, you can use the log files to troubleshoot any traced problems that occur on either the server or the client.

Procedure

To enable trace logging for selected subsystems:

  1. In the domain navigation pane in the administration console, select the server hierarchy object. For example, if you want to enable trace logging at the site level, expand the Sites folder and select a site.
  2. On the Trace Subsystem tab, go to the Log Files sub-tab and modify the log file properties.
    You can specify the properties like the number of log files that you want to keep, the log file rollover size and the location of the log file.
  3. Enable Content Engine tracing.
    1. On the Trace Subsystem tab, select Enable trace logging.
    2. Select Trace Subsystem > Trace Flags to indicate the Content Engine subsystems you want to trace.
  4. Enable Process Engine tracing.
    1. Go to the Workflow Subsystem tab and select Enable Workflow trace logging.
    2. Select Trace Options to indicate the Process Engine trace options that you want to trace.

Viewing trace logs

You can view and delete the trace log file that is created by trace logging.

Procedure

Navigate to the location of the trace log file.
The location of the trace log file is specified on the Trace Subsystem tab of the domain properties.
The file name for the trace log, for example, ce_trace0.log, has the following format:
<component_name>_trace<file_number>.log
where <component_name> is ce for Content Engine and pe for Process Engine. The <file_number> for the trace log starts with 0 and is incremented when a trace log file rollover is required. The most recent trace log has the lowest <file_number> and the oldest trace log having the highest <file_number>. If the maximum number of log files is reached, the oldest log file is deleted.