Logging and Tracing

The portal is logged using the standard central logging system of the AS Java. The Log Viewer tool in SAP NetWeaver Administrator allows you to view all logs and traces that are generated from the portal.

To ensure stable and error-free operation of the portal, you should check the logs regularly for error messages. If required, you can also configure the default logging settings to best meet your requirements.

Log and trace files contain information about the system execution:

• Log files are mainly used by administrators to monitor the system operation and to perform error analysis. Therefore, logs are always switched on and get written automatically. They have predefined granularity (severity) that can be modified at runtime. Logs are typically written to categories specific to problem areas.

• Trace files are mainly used by developers or support (engineers) to record and analyze the occurrence of certain events at runtime. Therefore, tracing is normally turned off. Traces can be switched on if a problem has occurred and a detailed analysis of a distinct aspect of the portal is necessary. Traces are typically written to locations that originate from specific source code areas.

For more information about log and trace files, how to view them, log configuration, and the log categories and trace locations specific to the portal, see Monitoring and Displaying Log Files .

Logging Changes Made to PCD Objects

You can log and view changes made to objects in the PCD. This includes changes made by the Transport mechanism, by the Generic Creator service (which automates content creation via XML), by content administration editors, as well as any changes made by users.

For more information, see Logging Changes Made to PCD Objects .