Show TOC

Procedure documentationConfiguring SAP NetWeaver BW Reporting

 

To comply with reporting requirements (for example, for production-relevant systems) or execute trend analyses, you can define which data on the execution of UXMon scripts is to be used for reporting in SAP NetWeaver Business Warehouse. You can also control which UXMon data is to be used for SLA reporting.

You can configure reporting in the following ways:

  • You specify which UXMon data is:

    • Relevant for reporting

    • To be used in SLA reporting to measure the availability of business processes

    • To be used in SLA reporting to measure the performance of business processes. You specify threshold values for SLA reporting for performance data.

  • You specify the method that the system uses to determine the percentage key figures for SLA reporting.

    In SLA reporting, you use the following percentage key figures for measuring availability and performance. You can calculate the key figures for UXMon scripts and individual steps and create corresponding reports. The following table explains the meaning of the three percentage key figures for both aspects of SLA reporting (the technical name of the key figure is indicated in parentheses):

    Key Figure

    Availability

    Performance

    Proportion of green SLA executions

    UXMon script or step for each monitoring period (0EEMSRNSL)

    Proportion of executions of an UXMon script or step for each monitoring period for which the execution time is below the threshold value for SLA reporting (0EEMSSLG)

    Proportion of red SLA executions

    Proportion of erroneous executions of an UXMon script or step for each monitoring period (0EEMERNSL)

    Proportion of executions of an UXMon script or step for each monitoring period for which the execution time is above the threshold value for SLA reporting (0EEMSSLR)

    Proportion of planned SLA executions canceled

    Proportion of executions canceled due to planned downtime

    (0EEMDRNSL)

    Proportion of executions canceled due to planned downtime (0EEMDSLP)

    During a monitoring period, it is possible that:

    • An UXMon script step is executed successfully or canceled for a specific UXMon robot at different times

    • An UXMon script step is executed successfully or canceled at a specific time for different UXMon robots

    To obtain an overall view, the reports must be aggregated based on an evaluation method. SAP provides two evaluation methods that the system can use to calculate the aggregated percentage key figures:

    • The Standard method works at step level. It examines the worst case and determines the proportions of executions that are green, red, or have been canceled due to planned downtime in relation to the total number of executions. The Standard method encompasses the following steps:

      1. The system calculates for each UXMon script and UXMon robot the proportion of UXMon script step executions that are red, green, or have been canceled due to planned downtime.

      2. The system determines for each UXMon robot whether the overall rating for an UXMon script is to be green, red, or canceled due to planned downtime. The system processes the evaluation rules in the following sequence:

        Status of UXMon Script Steps for Each UXMon Robot

        Rating for UXMon Script for Each UXMon Robot

        A step is red.

        The UXMon script is rated as red.

        A step is canceled due to planned downtime.

        The UXMon script is rated as canceled due to planned downtime.

        All steps are green.

        The UXMon script is rated as green.

      3. The system calculates for each UXMon robot the proportions of UXMon script executions that are green, red, or canceled due to planned downtime.

    • The Best Child method works at UXMon robot level. It examines the best case. It determines the proportions of green, red, or undefined periods of time for each UXMon robot in relation to the overall duration of the monitoring period. The Best Child method encompasses the following steps:

      1. The system breaks down the monitoring period for each UXMon robot into time periods that each span the period from when a script or step is executed until the next execution or the next planned execution for an UXMon script or step. The planned execution time depends on the length of the measurement interval that specifies how often an UXMon robot is to execute an UXMon script. For more information about specifying the measurement interval, see Adjusting Parameters.

      2. The system evaluates the time period for each UXMon robot and UXMon script:

        Status of UXMon Script or Step for Each UXMon Robot

        Rating of Time Period for Each UXMon Script and UXMon Robot

        Execution was canceled.

        The time period is rated as red.

        Execution was successful.

        The time period is rated as green.

        The execution was canceled due to planned downtime.

        The time period is rated as canceled due to planned downtime.

        The execution has no status.

        The time period is rated as undefined.

      3. The system compares for each step the executions on the various UXMon robots and determines for each UXMon script or step whether the time period is to be rated as green, red, undefined, or canceled due to planned downtime. The system processes the evaluation rules in the following sequence:

        Comparison of UXMon Robots for Each Time Period

        Rating for UXMon Script or Step for Each Time Period

        The time period was green for at least one UXMon robot.

        The time period is rated as green.

        The time period was red for all UXMon robots.

        The time period is rated as red.

        The time period was canceled on all UXMon robots due to planned downtime.

        The time period is rated as canceled due to planned downtime.

        The time period was undefined for all UXMon robots.

        The time period is rated as undefined.

      4. The system calculates the following percentage key figures for each script and step:

        • Proportion of green time periods for each monitoring period

        • Proportion of red time periods for each monitoring period

        • Proportion of time periods for each monitoring period in which the UXMon scripts were canceled due to planned downtime

        The proportion of undefined time periods for each monitoring period is not saved as a key figure in SAP NetWeaver BI.

      Note Note

      You can create a customer-specific evaluation method for your SLA reporting (based on percentage threshold values, for example). For more information, see SAP Note 1516204Information published on SAP site.

      End of the note.

Prerequisites

  • You have administrator authorization.

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

Procedure

  1. To specify the method you want to use to evaluate performance and availability data in SLA reporting, choose the Select SLA Method substep.

  2. To specify which UXMon data is to be used in reporting, and specify threshold values for performance data, choose the Configure BI Extraction substep.

    Note Note

    The threshold values for SLA reporting are calculated in the same way as threshold values for alerts. For more information, see Specify Alert Thresholds.

    End of the note.

  3. Choose Edit.

  4. Follow the instructions in the guided procedure.

  5. Save your entries.

More Information

To ensure that only SLA-relevant data is collected, UXMon allows you to define local work modes. This is useful if, for example, end users perform business scenarios in different time zones. For more information, see Defining Local Work Modes for SLA Reporting.