Skip to end of metadata
Go to start of metadata

Overview

This scenario can be used to evaluate, in every ABAP system, if the average number of connected users per hour is increasing over time or if there are peaks that need to be evaluated.

For Java systems, http sessions are used to display similar information.

Main Tile

The main tile shows two information: a number representing the average number of users per hour (last hour, today, yesterday or last 7 days depending on the configuration) and a trend. The average number of users is calculated adding the number of HTTP and Dialog users displayed in the Root Cause Analysis ==> ABAP Basis ==> Users Load. The trend compares last week (or last month depending on the configuration) with the last 8 weeks (or 12 months). In case the System has multiple instances, the number is calculated adding the average number of users for each instance.

The Detailed View

The trend on top shows the average (and maximum) number of connected users in different timeframes: last 24 hours with hourly granularity, last 30 days with daily granularity, and Last 12 month or ”this year” with monthly granularity. The lower graph shows the distribution of the hourly-connected users during the 24 hours or the days of the week. The distribution is calculated considering the last 60 days. This allows to answer questions like “What is the hour of the day in which more users are connected?” Which day of the week has been busier in the last 60 days? Additionally, another trend is showed in the same graph, the Response Time per dialog Step (for ABAP) or the Servlet/WebDynpro Response time (for Java). This allows correlating the number of connected users (or HTTP sessions) to possible performance issue.

Technical info

The following information are only valid for 7.1 ST-OST SP4 or 7.2 ST-OST SP0 systems where all the notes up to 2415611 - Focused Insights ST-OST Wave 1.3 are installed.

STDF Metrics


  • NB_HTTP_SESSIONS (Java)
  • USERS_LOAD (ABAP)
  • RFC_USERS (ABAP)
  • HTTP_USERS (ABAP)

InfoProvider


  • 0SMD_MPEH (USERS_LOAD, RFC_USERS and HTTP_USERS)
  • 0CCMPCURR (NB_HTTP_SESSIONS)
  • 0SMD_MPEH (NB_HTTP_SESSIONS)


Queries


USERS_LOAD, RFC and HTTP_USERS

  • 0SMD_MPEH//STDF/QM_USR_LOAD
  • 0SMD_MPEH//STDF/QD_USR_LOAD_HH
  • 0SMD_MPEH//STDF/QD_USR_LOAD_H
  • 0SMD_MPEH//STDF/QD_USR_LOAD_D
  • 0SMD_MPEH//STDF/QD_USR_LOAD_W
  • 0SMD_MPEH//STDF/QD_USR_LOAD_M


NB_HTTP_SESSIONS (Java)

  • 0CCMPCURR//STDF/QM_HTTP_SESSIONS
  • 0SMD_MPEH//STDF/QM_AVG_HTTP_SESSIONS
  • 0CCMPCURR//STDF/QD_HTTP_SESSIONS_MIN
  • 0SMD_MPEH//STDF/QD_AVG_HTTP_SESSI_H
  • 0SMD_MPEH//STDF/QD_AVG_HTTP_SESSI_D
  • 0SMD_MPEH//STDF/QD_AVG_HTTP_SESSI_W
  • 0SMD_MPEH//STDF/QD_AVG_HTTP_SESSI_M


Data Validation

For ABAP Systems, you can see this kind of information in Root Cause Analysis E2E Analysis (Select System ID) Workload Analysis ABAP Basis User Load


  • NB_HTTP_SESSIONS:

For Java systems,  using the transaction code RSRT1 and the /STDF/QM_HTTP_SESSIONS



  • RFC_USERS (Max Number of Logged on RFC Users):

For ABAP Systems, you can see this kind of information in Root Cause Analysis E2E Analysis (Select System ID) Workload Analysis ABAP Basis User Load


  • User Type : RFC Users


  • No labels