Scheduling a Measurement: The ABAP User Trace
By scheduling a measurement, you tell the Runtime Analysis to start the measurement automatically, when the conditions that you specify are met.
Here is the procedure:
On the For User/Service screen area, choose For User/Service.
A dialog box appears containing all the scheduled measurements.
Measurements that have not been finished yet have the status In Process. Completed measurements have the status Executed.
By default, you see only measurements scheduled on the local server. Choose Server Selection from the tool bar to see scheduled measurements from other or all servers in the system.
Choose (Schedule Measurement).
The Schedule Measurement dialog box appears.
Enter all required information (see below). You can leave fields like User blank if you are not sure which user will start the activity you want to trace. Be as specific as you can so that you catch the activity that you want to measure.
If a measurement is not executed as planned, repeat the scheduling and set the scheduling parameters External Mode, Process Type, and Object Type to the value Any.
Choose Schedule (Measurement) to confirm the scheduling request.
The system schedules a measurement for the specified external mode, process type, object type, object name, time, and date.
The request appears in the Overview of Scheduled Measurements with the Status In Process and the value 0 in the Started column.
When the trace or traces have been made, the Status changes to Executed. The Started column shows the number of traces that have been made. You must refresh the display to see changes in the Overview.
If an application server is shut down, then any scheduled measurements In Process (not yet completed) are lost.
You can also manage scheduled measurements actively. If a measurement is not needed, you can delete it in the Schedule Measurement dialog box.
Enter service paths to measure BSP and Web Dynpro applications, as well as Web services.
You can measure specific types of HTTP requests by selecting URL as Object Type. You can then enter the path of the service in the Object Name field.
You need only enter the URI, the path of a service in the Object Name field, not a complete URL. Start the path with the '/' character.
Using URL paths to schedule a BSP or Web Dynpro application or Web Service for runtime analysis.
You can display the path of a Web Dynpro application in the ABAP Object Navigator (SE80) or in transaction SICF (Services Maintenance).
You find the path of ABAP Web Services in the Enterprise Services Browser in the ABAP Object Navigator (SE80) or in transaction SICF (Services Maintenance).
You find the path of a BSP application in transaction SICF (Services Maintenance).
Starting HTTP measurements from transaction SICF
You can also start the runtime analysis for processing an HTTP request directly from transaction SICF (Services Maintenance):
In the Service Name field, enter the name of the service.
Display the service using Execute.
Select the service name and choose.
The system displays the scheduling window for the runtime analysis.
Further Information on the Scheduling Fields
In the User field, enter the user under whose name the event to be measured will run.
The name specification is optional. If no user is entered, then the scheduled measurement ignores the user. The measurement is made for any user action that meets the other criteria.
The specification of the client is also optional and serves to uniquely identify the user. (users MAIER/000 and MAIER/100 may possibly be assigned to different persons).
Leave Client blank to capture activity in any client. Note that you must log on in the client in which a measurement was made to display the measurement.
Example: Assume that you schedule a measurement while you are logged in on client 100 and that a measurement is made on client 000. The Scheduled Measurements display in client 100 shows in the Started column that a measurement has been made. But you must log on to client 000 to see the measurement in transaction SAT on the Evaluate tab.
To make a measurement in another external session of your log on or another user's logon, specify the number of the session.
Example: to trace activity in another user's external session (SAP window) number 2, enter the user name, client (if needed) and External Session 2. When the user starts the activity in that session, the Runtime Analysis records it.
Otherwise, leave the field set to Any.
In addition to the ANY option, you can specify the following types of processes:
Shared Objects Area Constructor
The object to be measured can also be arbitrary, or one of the following types. Remember, however, that only certain combinations of Process Type and Object make sense.
Transaction (starting a transaction) – suits dialog, background processing
Report (calling a program) – suits dialog, update, background processing
Function module (calling a function module / RFC) – suits dialog, update, background processing, RFC
Shared Objects Area Constructor (setting up a shared objects area) - suits Shared Objects Area Constructor
URL (calling a URL through ITS or HTTP) – suits HTTP, SMTP, ITS
The object name is also optional and specifies the name of an object of the selected type.
Here you need only enter a prefix – that is, the specification F1 for a report would mean that each execution of a report whose name begins with F1 can be measured.
To capture an HTTP request, only the path of the request is needed. (See the note above).
Expiration Date and Expiration Time
The maximum number of planned measurements specifies how many measurements are to be created. The expiry date and time serve to limit the validity of the planned measurement. As soon as the maximum number of measurements of the expiry time has been reached, the status for planning is set to "finished".
Try to avoid setting the expiry date for a planned measurement far into the future and choosing too large a number of executions. This could have a negative influence on system performance. This is particularly true when the measurement parameters are generic (arbitrary user, arbitrary process type).
Make sure that each started measurement is also finished. One common reason why a planned execution does not seem to be functioning is because a previous measurement is still active. You can check this by displaying the external processes, for example (using the function Switch On/Off in a parallel session).End of the note.
Was this page helpful to you?
Do you have any additional feedback?
The following content is not part of SAP product documentation. For more information, see the following disclaimer .