SAP Basis Tech Supports

Symptom
Sometimes it may be necessary to monitor WBEM requests of client applications that are sent to an SLD system, for example to analyze high load situations or unusual errors. For this purpose, SLD offers a request and session trace.
Other terms
SLD, System Landscape Directory, Tracing
Reason and Prerequisites
To use the request and session trace your SLD must be on release
SAP NetWeaver 7.0 SP14 or higher (or any 7.0 EhP)SAP NetWeaver 7.1 SP07 or higher (or any 7.1 EhP).
Solution
The trace is configured by two SLD parameters, “RequestTrace” and “SessionTrace”, that will be explained in more detail below. If tracing is activated, output is written to a subfolder of the SLD working directory. Typically, you will find the trace files here:
usr\sap\<SID>\SYS\global\sld\trace\OM
If the “trace” or “OM” folder does not exist, it will be created automatically when tracing is activated.
By default, both parameters are not available in the SLD UI to avoid accidental activation. To make them available the attached file can be imported into the SLD settings:
1. Save the attached “sld_req_trace_params.zip” file locally.2. In the SLD UI, go to “Administration” -> “Settings” (7.1) or “Profile” (7.0).3. Use “Upload” to import the file.Do not activate the “Overwrite”checkbox because this would delete all existing settings.

!!!!! WARNING !!!!!

Activating these parameters can generate large trace files which can fill up your file system. Therefore you must activate theses traces only while trying to reproduce and analyze a problematic situation.
Afterwards, the parameters should be deleted to prevent accidental
activation in the future. Deletion of these parameters will automatically deactivate the trace. (A deletion is equivalent to selecting the parameters’ default values.)

Request Trace

The request trace can be used to get an overview of requests sent to the SLD. To activate it, set the value of parameter “RequestTrace” to “true”.
Output is written to a fileWBEM_<RandomNumber>.trcand contains a single line for each request processed by the SLD including details like
start timetype of requesttarget namespaceprocessing time (of the WBEM request)total time (of the whole HTTP request)user name and IP address of the clientsession ID.

Session Trace

In addition to or instead of a request trace, a session trace can be used. The session trace is controlled by parameter “SessionTrace”. If activated, an individual trace file is written for each HTTP session. These trace files contain the complete XML definition of remote WBEM requests/responses and can become quite large.
Possible values for parameter “SessionTrace” are:
0 – No traces are written.1 – Only requests are traced.2 – Requests and responses are traced.If any other value is specified, default behavior (no trace) will be used.
Output is written to filesSession_<SessionIDHash>.trc. Unless the unlikely event occurs that two different sessions have the same hash code, each file contains traces for one individual HTTP session. The hash collision can be detected because the full session ID is included in the trace file for each request and response.