ICM Tracing 
Use
When developing a Web application, you will want to test parts of your application and analyze the coding’s dynamic behavior. Occasionally this will result in errors that cannot be solved even with the help of the Debugger.
So that 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.
For more information about the ICM, see 
Internet Communication
Manager (ICM).
The following information explains how you can use ICM tracing.
Prerequisites
You have basic knowledge about creating Web applications and the Internet Communication Manager.
Activities
...
1. Call Transaction SMICM.
2. Choose Goto ® Trace file ® Display File or Display Start.
This displays the trace file. Here is an extract from a trace file:
ICM Tracefile (dev_icm)
trc file: "dev_icm", trc level: 1, release: "700"
[Thr 1] Mon Oct 27 17:19:11 2003 [Thr 1] systemid: 324 (IBM RS/6000 with AIX) [Thr 1] version: 7000 [Thr 1] patchlevel: 0 (server: 0) [Thr 1] patchno: 0 (server: 0) [Thr 1] intno 20034400 (server: 20034400) [Thr 1] make: multithreaded, Unicode, 64 BIT [Thr 1] pid: 720906 [Thr 1] Mon Oct 27 17:19:12 2003 [Thr 1] *** WARNING => maximum number of sockets supported on this host (1993) less than parameter icm/max_sockets (2048) [icxxman_mt.c 2349] [Thr 1] ICM running on: is0206.wdf.sap-ag.de [Thr 1] MtxInit: -2 0 0 [Thr 1] IcmInit: listening to admin port: 65000 [Thr 1] DpSysAdmExtCreate: ABAP is active [Thr 1] DpSysAdmExtCreate: JAVA is not active [Thr 1] DpShMCreate: sizeof(wp_adm)##9240#(1320) [Thr 1] DpShMCreate: sizeof(tm_adm)##3159720#(15720) [Thr 1] DpShMCreate: sizeof(wp_ca_adm)##8000#(80) [Thr 1] DpShMCreate: sizeof(appc_ca_adm)#8000#(80) [Thr 1] DpShMCreate: sizeof(comm_adm)##126400#(632) [Thr 1] DpShMCreate: sizeof(vmc_adm)##0#(592) [Thr 1] DpShMCreate: sizeof(wall_adm)##(40056/36728/64/192) [Thr 1] DpShMCreate: SHM_DP_ADM_KEY##(addr: 0x7000000000f0000, size: 3395432) [Thr 1] DpShMCreate: allocated sys_adm at 0x7000000000f0000 [Thr 1] DpShMCreate: allocated wp_adm at 0x7000000000f1bc8 [Thr 1] DpShMCreate: allocated tm_adm_list at 0x7000000000f3fe0 [Thr 1] DpShMCreate: allocated tm_adm at 0x7000000000f4008 [Thr 1] DpShMCreate: allocated wp_ca_adm at 0x7000000003f76b0 |
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 Goto ® Trace 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.
Since trace level 3 records all data traffic, you must make sure that you set this level to trace
an error situation only and that you reset it to the default value
1 immediately after you have finished the trace.
If you do not do this, very large data volumes will be written to the file
system, which could cause your hard disk partition to overrun.
For
more information about managing the ICM process, see Monitoring the ICM
with the ICM Monitor.