Skip to end of metadata
Go to start of metadata

Overview

This scenario can be used to report values and trends for “Average Response time per Dialog Step” (ABAP) or “WebDynpro/Servlet Response Time” (Java) to make it easier to assess performance degradation in technical systems.

The source for ABAP performance metrics can be either ASR Statistical Records (mainly ST03N data) or Technical Monitoring Response Time (R3DialogResponseTime metric), depending on the configuration. In the first case, the source of information is the managed system's Statistical Records MONI tables data (ST03N). In the second case the (instance level) Metric is retrieved from the CCMS MTE class "R3DialogResponseTime" of each application server (RZ20). 

Main Tile

The Detailed View

In the detail view, four different periods can be selected, for the upper graph, with different granularities:

  • Last 24 hours
  • Last 7 Days
  • Last 30 Days
  • Last 12 Months.

The lowest graph always keeps the data of the last 8 weeks with weekly granularity.

Technical info

The following information are only valid for 7.1 ST-OST SP4 or 7.2 ST-OST SP1 systems where all the notes up to 2525702 (Focused Insights ST-OST Wave 2.2) are installed.

STDF Metrics


  • PERFORMANCE_ABAP
  • PERFORMANCE_JAVA
  • TRANS_PERF
  • TRANS_NB_CALL 

InfoProvider


  • 0CCMPDATA  (PERFORMANCE_ABAP)
  • 0SMD_MPEH (PERFORMANCE_JAVA)
  • 0CCMAW (TRANS_PERF)
  • 0CCMAW (TRANS_NB_CALL)


Bex Queries

PERFORMANCE_ABAP

  • 0CCMPDATA//STDF/QD_PERF_ABAP_H
  • 0CCMPDATA//STDF/QD_PERF_ABAP_D
  • 0CCMPDATA//STDF/QD_PERF_ABAP_W
  • 0CCMPDATA//STDF/QD_PERF_ABAP_M


PERFORMANCE_JAVA

  • 0SMD_MPEH//STDF/QD_PERF_JAVA_H
  • 0SMD_MPEH//STDF/QD_PERF_JAVA_D
  • 0SMD_MPEH//STDF/QD_PERF_JAVA_W
  • 0SMD_MPEH//STDF/QD_PERF_JAVA_M
  • 0SMD_MPEH//STDF/QD_PERF_JAVA_HH


TRANS_PERF

  • 0CCMAW//STDF/QD_TRANS_PERF_H
  • 0CCMAW//STDF/QD_TRANS_PERF_D
  • 0CCMAW//STDF/QD_TRANS_PERF_W
  • 0CCMAW//STDF/QD_TRANS_PERF_M


TRANS_NB_CALL

  • 0CCMAW//STDF/QD_TRANS_NB_CALL_H
  • 0CCMAW//STDF/QD_TRANS_NB_CALL_D
  • 0CCMAW//STDF/QD_TRANS_NB_CALL_W
  • 0CCMAW//STDF/QD_TRANS_NB_CALL_M


ABAP Performance Data Validation

  • Case 1: when using ''Technical Monitoring'' as a source for performance data

  • Main tile validation data :

For ABAP Systems, you can see this kind of information in Interactive Reporting  (Select System ID) System Reports Performance System Performance

  • Case 2 : when using ''Statistical Records'' as a source for the data


For ABAP Systems, you can see this kind of information in Root Cause Analysis (Select System ID) End-to-End-Analysis Workload Analysis




Java Performance Data Validation

The Java Performance data are collected by RCA extractors which are activated as soon as the system is connected to Solution Manager. Hence, to validate the data, the RCA Workload Analysis can be used.

For the detailed view, it is sufficient to select an appropriate time frame (e.g. This Month), filter for the displayed metric types and drill down by calendar day.



  • No labels