Show TOC

Procedure documentationAdjusting Parameters Locate this document in the navigation structure


End User Experience Monitoring (EEMon) is delivered with a root configuration containing suitable values for all EEMon parameters. You can adjust these parameters for particular applications.

You can control the behavior of the EEMon robot at various levels. These levels go hierarchically from the general to the particular, and pass their attributes to the hierarchically lower levels.

  • You can leave the delivered root configuration unchanged, and get meaningful results.

  • You can adjust the values of the root configuration organization-specifically, and create a global configuration.

  • You can adjust the global configuration settings at EEMon robot level. You can take the particular geographical location into account. You can, for example, monitor particularly business-critical locations more intensively than less business-critical ones. It can, for example, be important to monitor a location of sales staff who need smooth access to CRM data, more intensively.

  • You can adjust EEMon script parameters at technical scenario level to the relevant underlying technical system.

  • You can adjust the EEMon robot settings at the level of the EEMon scripts that are executed by the EEMon robots. You can then monitor business processes which are performed frequently, and are therefore business-critical, e.g. creating sales orders, more intensively than less often performed transactions, e.g. monthly payroll calculation.

  • You can change EEMon script parameters temporarily. If. for example, you want to identify the cause of performance bottlenecks, change the resolution of the trace data temporarily. For more information, see Changing Parameters Temporarily for Error Analysis.

Typically, you adjust the following behavior of the EEMon robot at various levels of the configuration:

  • Measurement intervals

  • Trace data resolution

  • How various EEMon robots or EEMon scripts are synchronized

Make these behavior adjustments with the following parameters:





Specifies a start delay with which you can specify an EEMon robot start sequence. You must specify a start sequence for EEMon scripts that, when executed, lock the relevant business process for other users, for example, changing database entries when booking a flight. A start sequence can prevent the EEMon robots from executing an EEMon script simultaneously and blocking each other.

The start delay must be at least the time it takes to execute the EEMon script. Typically it will be a factor of several times the runtime.

You have several robots with the same script, which runs for about 40 seconds. Retain the default setting “0” for the EEMon robot that is to be run first. To delay the next EEMon robot for 300 seconds, enter the value 300. The third EEMon robot is assigned the value 600, and so on.


The measurement interval, that is, how often an EEMon robot is to run an EEMon script.

To prevent EEMon robots from blocking each other, the measurement interval must be longer than the duration of all executions of the EEMon script by all EEMon robots.

You specify that you monitor a business process which runs on a particularly sensitive system, more frequently than the default interval of 600 seconds. The EEMon script runs for one minute. It is executed by five EEMon robots. You specify an interval of at least 300 seconds.


Specifies a fixed starting time for EEMon robots. You specify the local time of the host. The accuracy depends on the accuracy of the host's system clock.

Enter the time in the format HHMM, e.g. 1530.

You know the time at which a specified business process is performed. You can, for example, with a default measurement interval of 10 minutes, start the EEMon robot five minutes earlier to compare the behavior of the systems five minutes before and after starting the business process.


Specifies the resolution of the trace data logged by an EEMon robot.

The resolution value is coded as a four-digit number.

To generate this type of code for a specific trace level, you can use the administration dialog box in EEMon monitoring and copy the code manually. For more information about generating the code, see Changing Parameters Temporarily for Error Analysis.

You can, for example, choose the trace level Medium for a performance trace. For further information about the meaning of the various trace levels, see Trace Analysis.


  • You have administrator authorization.

  • You are currently performing the Monitoring step of the guided procedure for setting up End User Experience Monitoring in the SAP Solution Manager: Configuration work center.


  1. Choose the level at which you want to adjust the parameters:

    • To configure parameters globally, choose the Global tab.

    • To configure EEMon robots running at specific locations, for example, choose the Robots tab.

  2. Choose Edit.

  3. Select the relevant object and enter the required values in the Parameter Value column.

  4. Optional: You can download configuration files, e.g. to answer support queries.

    1. Select the relevant tab.

    2. Select the object.

    3. Select the configuration type in the Resource field.

      The link Download Resource is displayed.

    4. Choose Download Resource to download the configuration file.

  5. Save your entries.