Tracing Single User Sessions

If a user working with your system encounters a problem related to HTTP requests that he or she can reproduce, you can easily investigate this problem using the single user tracing functionality. The only information the user needs to provide is the user ID. Afterwards, he or she has to reproduce the problem while you search the trace files for the particular user session. The single user tracing functionality enables you to customize a set of traces related only to this user session. This saves you time and effort by excluding the information that is not related to the problem.

You have two possible cases:

When the user has already been logged in the system. To investigate the HTTP request problem, you use the root context ID of the particular user session.
When the user has not been logged in the system yet. In this case you have to create your own rule, a five digit number, to filter the required information.

Note Note

The procedures described below start the tracing activity only for the specified locations. If you do not perform any requests to the trace files, the tracing activity will expire in 30 minutes.

End of the note.

Procedure

Tracing User Sessions

In this case the user has already been logged in the system.

To configure the trace files so that only information about the related problem in a particular user session appears, use the following Telnet commands:
Syntax
1. ```
>add servlet_jsp
```
2. ```
>user_tracing -start <user_ID> com.sap.engine.services.servlets_jsp
```
End of the code.
where <user_ID> is the ID of the logged user and com.sap.engine.services.servlets_jsp is the location related to the Web Container service. You have to specify the appropriate location(s) related to the problem. If you need to specify a set of locations, use the absolute path name of the file where you have listed each and every location on a new line.
Copy the generated root context ID and use it to search in the trace files of the particular service.
Ask the user to reproduce the HTTP request and afterwards use the generated root context ID to find more information about the problem in the trace files.
(Optional) To stop the trace files filtering, use the following Telnet command:
Syntax
1. ```
>user_tracing -stop
```
End of the code.
(Optional) To check the current state of the single user tracing, use this command:
Syntax
1. ```
>user_tracing -status
```
End of the code.

Tracing HTTP Sessions

In this case the user has not been logged in the system yet.

Open the SAP NetWeaver Administrator.
Choose Problem Management Java AS Java Statistics .
In the context menu of the Show section, choose Configure activity tracing.
Enter the appropriate location in the corresponding field and choose Add. For example, if the problem is related to the Web Container service, enter com.sap.engine.services.servlets_jsp. For a problem related to the HTTP Provider service, enter com.sap.engine.services.httpserver.
Choose Start and then Close.
To search the trace files without having the user ID of a particular session, you need to create a unique identifier. Ask the user to add the following string in the URL: &dsr_trace=<five_digit_number>&dsr_session_trace=1, where you specify your own <five_digit_number>, and to reproduce the HTTP request.
In the Common section, choose Go.
Choose Availability and Performance Management Resource Monitoring Log Viewer .
Use your number to find information in the trace files about the specific problem.
Choose Show advanced filter.
From the Filter by Content dropdown list, choose DSR Root Context ID.
Enter your number in the appropriate field to find information in the trace files about the specific problem.