Enable and Configure Tracing for Web Applications 

Purpose

You can configure the J2EE Engine to generate debugging information about Web applications that are deployed on it, which you can use to troubleshoot errors that occur. The corresponding traces are saved to the \usr\sap\<SID>\<instance_name>\j2ee\cluster\dispatcher\log\services\http\req-resp.trc file.

Web Container traces should be used for debugging purposes on non-productive systems, or on debug nodes if the system is productive! Bear in mind that using this function can result in printing security-sensitive data to the trace files on your file system. For more information see Security Aspects When Using HTTP and Web Container Tracing.

Process Flow

Configuring tracing for Web applications is a two-phase process:

...

       1.      Enable traces using the TraveLevel property of the Web Container Service.

You must specify a positive integer value for this property. If the value is 0 or negative, no tracing information will be generated.

       2.      Increase the severity of the Web Container-related trace locations to generate detailed information about the error that occurred.

By default, the severity of the Web Container-related trace locations is set to Error.

To configure the generation of excessive information that is necessary for debugging, you need to increase the severity of the locations to All. The Web Container-related trace locations appear under the following path in the Locations tree in the Log Configurator service in the Visual Administrator: ROOT_LOCATION  → com  → sap  → engine  → services  →  servlets_jsp.

For more information about changing the log severity, see Adding, Editing, and Removing Log Controllers.

For more information about the semantics of log severity levels, see Log Severities.