Show TOC

Procedure documentationChanging Parameters Temporarily for Error Analysis

 

You can change parameters temporarily, to analyze irregularities which cannot be reliably reproduced. If, for example, performance bottlenecks occur irregularly during a specific business process, you can increase the resolution of the recorded trace data, in which an event will occur, for as long as you like. In this way, you can identify the cause of the bottleneck. You record the trace data, for example, for 10 hours, and then return automatically to the intervals you specified.

Prerequisites

  • You have administrator authorization.

  • You have started the end user experience monitor.

Procedure

Caution Caution

High trace-levels can impair the performance of the simulated users. Alerts could be generated although the performance of the system is not really impaired.

  • Only use the trace for error handling and problem analysis.

  • Increase the trace level for as short a time as possible.

End of the caution.

Caution Caution

A trace level higher than 0 makes SLA reporting invalid, due to the impaired performance.

Ensure that the trace level is set to 0 again, after the error is resolved.

End of the caution.

  1. Choose Administration.

  2. Choose Temporary Configuration.

  3. Specify in the field Time (in seconds), for how long the changed setting is to apply. The default value is 3.600 seconds.

  4. Specify the resolution of the trace data in the field Trace Level.

    For more information about the meaning of the various trace levels, see Start of the navigation path http://service.sap.com/diagnostics Next navigation step E2E Trace Analysis - User Guide End of the navigation path.

    The selected resolution of the trace data is displayed in the parameter trace.e2etracelevel, in the area Temporary Parameters. The value is a four-digit code that is updated upon saving.

    Note Note

    You use the four-digit code for the resolution of the trace data when you set up the resolution of the trace data in the global configuration or at EEMon robot or EEMon script level.

    For further information, see Adjusting Parameters.

    End of the note.

  5. Optional: Specify the types of traces to be activated in the called system:

    1. Select the trace type. For more information, see the documentation of the transaction.

      • SQL Trace, Table Buffer Trace, Enqueue Trace, RFC Trace, Authorization Trace: Transaction ST05 and ST01.

      • Single Activity Trace: For further information, see under Start of the navigation path http://service.sap.com/diagnostics Next navigation step E2E Trace Analysis - User Guide End of the navigation path, chapter Specify trace locations for tracing with level high.

      • Web Service Trace: Transaction SRT_UTIL.

    2. Specify the aggregation of the ABAP runtime analysis in the area ABAP Trace Aggregation.

      For more information, see the documentation of transaction SAT.

  6. Optional: To change other parameters temporarily, in the area Temporary Parameters, choose Add.

  7. Save your entries.

  8. Start the script with the temporary configuration:

    1. Choose the EEMon script of the EEMon robot.

    2. You can:

      • To run the EEMon script with the temporary trace level for the specified time, choose Set Temporary Configuration in the context menu.

      • To run the EEMon script once with the temporary trace level, choose Run Script with Trace in the context menu.

  9. Analyze the performance of the EEMon script in the End User Experience Monitor.