Logging services

WebSphere Commerce provides facilities for logging. For existing customers, ECTrace and ECMessage are still supported. For new implementations, use the WebSphere Application Server recommendation for logging and tracing.

The purpose of logging messages in the Transaction Server is to record unexpected errors or abnormal conditions within the WebSphere Commerce application. (For information about recording commands and tasks that are executed during a WebSphere Commerce operation, refer to
business auditing.) Message logs and traces are important diagnostic tools that aid the Site Administrator in determining the source of problems. Tracing is a problem-determination mechanism. Tracing assists developers in debugging the code during the development stage and assists the technical support team in solving customer problems. The Log and Trace Analyzer tool for Eclipse in the WebSphere Application Server Toolkit can be used. The Log and Trace Analyzer tool for Eclipse is installable from the WebSphere Application Server Toolkit launchpad console. It provides interactive viewing and analysis capability that is helpful in identifying problems.

Review the following WebSphere Commerce Log APIs:

Logging file location

We can find the default output files in the following directory:

In the directory, we can find the following default output files:

Logging levels

There are three logging levels, or severities, in the WebSphere Commerce logging system:

Note: Although the WebSphere Application Server logging facility also uses the status and debug logging levels, WebSphere Commerce uses and maps to the error, warning, and informational logging levels.

Since WebSphere Commerce uses the WebSphere Application Server logging facility, refer to the following table to learn about how the WebSphere Commerce logging levels are mapped to the WebSphere Application Server as follows:

Logging levels in WebSphere Commerce Logging levels in WebSphere Application Server

The WebSphere Application Server user interface is used to control the enablement of the logging level or severity type. Site Administrators can specify which logging severities to record in the WebSphere Application Server Administration Console.

Viewing log files

We can view log files in various ways. Typically, depending on the type of log file, there are suggested methods to view as follows:

The following diagram illustrates these suggested view methods: