Show TOC

Procedure documentationAdjusting Parameters

 

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

You can control the behavior of the UXMon 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 UXMon 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 UXMon script parameters at technical scenario level to the relevant underlying technical system.

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

  • You can change UXMon 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 UXMon robot at various levels of the configuration:

  • Measurement intervals

  • Trace data resolution

  • How various UXMon robots or UXMon scripts are synchronized

Make these behavior adjustments with the following parameters:

Parameter

Function

Example

schedule.offset.seconds

Specifies a start delay with which you can specify an UXMon robot start sequence. You must specify a start sequence for UXMon 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 UXMon robots from executing an UXMon script simultaneously and blocking each other.

The start delay must be at least the time it takes to execute the UXMon 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 UXMon robot that is to be run first. To delay the next UXMon robot for 300 seconds, enter the value 300. The third UXMon robot is assigned the value 600, and so on.

schedule.period.seconds

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

To prevent UXMon robots from blocking each other, the measurement interval must be longer than the duration of all executions of the UXMon script by all UXMon 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 UXMon script runs for one minute. It is executed by five UXMon robots. You specify an interval of at least 300 seconds.

schedule.starttime

Specifies a fixed starting time for UXMon 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, 1530, for example.

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 UXMon robot five minutes earlier to compare the behavior of the systems five minutes before and after starting the business process.

trace.e2etracelevel

Specifies the resolution of the trace data logged by an UXMon 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 UXMon 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 more information about the meaning of the various trace levels, see Trace Analysis.

Prerequisites

  • You have administrator authorization.

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

Procedure

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

    • To configure parameters globally, choose the Global tab.

    • To configure UXMon 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, to answer support queries, for example.

    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.