Skip to end of metadata
Go to start of metadata

Purpose

The purpose of this page is to clarify the understanding of the ICM Trace.

Overview

When developing a Web application, you will want to test parts of your application and analyze the coding dynamic behaviour. Occasionally this will result in errors that cannot be solved even with the help of the Debugger.

You can analyze the cause further, you need to be able to record the datastreams to and from the SAP Web Application Server. The SAP Web Application Server enables you to do this in the form of tracing.

The component that regulates HTTP data traffic is the Internet Communication Manager, (ICM). You can use Transaction SMICM to manage and trace this SAP kernel component.

Activities

There are several levels for a trace. The trace level is set to 1 by default. This setting creates a short log of only the most important system events and errors. This level is not usually sufficient to find out the precise cause of the error, however, which is why you can change the trace level interactively

1.      Call Transaction SMICM

2.      Choose GotoTrace file Display File or Display Start.

This displays the trace file. Here is an extract from a trace file

 
 

There are several levels for a trace. The trace level is set to 1 by default. This setting creates a short log of only the most important system events and errors. This level is not usually sufficient to find out the precise cause of the error, however, which is why you can change the trace level interactively.

3.      To increase the trace level, on the initial screen of Transaction SMICM choose GotoTrace level Increase.

You have the option of setting the level directly, or increasing or reducing it by one level. 1 is the lowest level, 3 is the highest level with the greatest level of detail for the trace entries. All data traffic, amongst other things, is recorded in the highest level.

Related Content

  • No labels