The Internet Transaction Server (ITS) has standard procedures for handling trace files, but you can customize this behavior.
To minimize resource requirements and optimize performance, the default behavior for trace file handling is to record only errors and always append new records to the same trace file, but you can modify this in ITS Administration by changing the parameter values.
The table below lists trace file parameters and their possible values:
Parameter |
Description |
Value |
Meaning |
TraceLevel |
Specifies amount of information written to trace file. |
1 |
Record errors only (default). |
2 |
Record errors and warnings. | ||
3 |
Displays errors, warnings and information entries. | ||
TraceAppend |
Toggle switch to select one or more trace files. |
0 |
New trace file starts with each ITS restart; a timestamp is added to the old trace file name. |
1 |
Only one trace file is used; additional records are always appended to this file. |
The default value of
TraceAppend depends on the component:Component |
Default |
AGate |
0 |
MManager |
1 |
SAPirf |
1 |
SAPjulep |
1 |
SAPxgdk |
0 |
WGate |
1 |
Basis Component Traces
To enable the creation of trace file entries for Basis components like the network interface (NI) and the RFC library, there is an additional parameter called
BasisTraceLevel for the AGate component.This registry value is not integrated into the ITS setup, so you have to create it explicitly under
HKEY_LOCAL_MACHINE\Software\SAP\ITS\2.0\<ITS instance>\Traces\AGate\
Setting
If you want to perform NI traces, but you are not interested in all ITS traces, you should set
…Traces\AGate\TraceLevel to 1 and …Traces\AGate\BasisTraceLevel to 3 .All Basis traces are written to the file
AGate.trc .You can define trace file handling by setting a trace level with the
TraceLevel parameter and specifying how trace file information is to be recorded with the TraceAppend parameter in ITS Administration. To do this, see Setting Trace File Parameters.