Setup Guide - PerfMon
Setup Guide - PerfMon
PerfMon: Techn.
Performance for
Reporting
July 2011
SAP AG
Neurottstraße 16
69190 Walldorf
Germany
T +49/18 05/34 34 24
F +49/18 05/34 34 20
www.sap.com
© Copyright 2011 SAP AG. All rights reserved. JAVA® is a registered trademark of Sun Microsystems, Inc.
No part of this publication may be reproduced or transmitted in any J2EE™ is a registered trademark of Sun Microsystems, Inc.
form or for any purpose without the express permission of SAP AG.
The information contained herein may be changed without prior JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc.,
notice. used under license for technology invented and implemented by
Netscape.
Some software products marketed by SAP AG and its distributors
contain proprietary software components of other software vendors. SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business
Workflow, WebFlow, SAP EarlyWatch, BAPI, SAPPHIRE,
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and Management Cockpit, mySAP, mySAP.com, and other SAP products
®
SQL Server are registered trademarks of Microsoft Corporation. and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in
® ® ® ®
IBM , DB2 , DB2 Universal Database, OS/2 , Parallel Sysplex , several other countries all over the world. MarketSet and Enterprise
MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, Buyer are jointly owned trademarks of SAP Markets and Commerce
®
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere , One. All other product and service names mentioned are the
TM
Netfinity®, Tivoli®, Informix and Informix® Dynamic Server are trademarks of their respective owners.
trademarks of IBM Corp. in USA and/or other countries.
Table of Contents
1 INTRODUCTION AND MOTIVATION ................................................................................................... 4
1.1 Monitoring Objects using Statistical Records for Performance .................................................... 4
1.2 Further Setup Guides....................................................................................................................... 5
May 2011 3
Trend Analysis Reporting with SAP Solution Manager
The performance of the main business transactions is most crucial for the daily operations. Bad performance
of main business transactions can cause that
Therefore SAP recommends defining KPIs and thresholds for transaction performance. Required monitoring
activities should be defined including procedures to measure the KPIs on a regular basis. The expectations
have to be part of a service level agreement between the business units and the operation center.
Performance Monitoring within Business Process Operations Work Center in SAP Solution Manager assists
you to check these defined KPIs and to react on exceeded thresholds in time: Performance data of
transactions to be monitored are extracted from the managed system into SAP Solution Manager's BW.
Monitoring of transactions with specified key figures is defined, so that alerting on performance critical
situations is enabled, when the runtime related thresholds are reached.
Furthermore you can investigate if there is a trend with increasing response times of a transaction, or if there
are peaks depending of the weekday or seasons.
In this guide we will describe the setup of monitoring object 'PerfMon: Techn. Performance for Reporting'.
This monitor retrieves statistical performance data of the business transactions (like you can see it with
transaction STAD). It offers different key figures like average response time, average DB time, etc. and
different select options like transaction, function code, user, etc. The data is saved in Solution Manger BW's
Info Cubes and functions can be used provided with Business Process Analytics (BP Analytics).
4 May 2011
BPMon Analytics with SAP Solution Manager
There are some other monitoring objects in BPMon, which can be used for retrieving statistical performance
data, too. We want to give an overview with advantages and disadvantages of each of these performance
monitors:
Dialog Dialog Performance - Very low impact on workload since CCMS - Selection with function code and user not
Performance infrastructure is used available
- Only dialog transactions can be
monitored
Dialog Application Monitor / - Selection possible with function code and - High workload on the managed system, if
Performance BOPERFMO user many statistics are collected, especially if
Monitor - Background, RFC and HTTP monitoring there are many applications servers and if
possible many dialog steps are executed
PerfMon: Application Monitor / - Selection possible with function code and - Delay of at least 2 hours until the data
Techn. PETPERF1 user gets visible in Business Process
Performance for - Background and HTTP monitoring Monitoring
Reporting possible - RFC monitoring not yet possible
- Impact on workload is low, since the data
collection takes place via basis workload
collector RSCOLL00
- Provides data in BP Analytics
May 2011 5
Trend Analysis Reporting with SAP Solution Manager
Business Process Analytics has to be implemented, see 'Setup Guide - Business Process Analytics' (at
http://www.service.sap.com/bpm in the “Media Library” under “Technical Information”).
This comprises:
Activation of Info Cube 0SM_BPMRH from BI Content in Solution Manager
Activation of the HTTP Services for Web Dynpro components
Activation of Solution Manager Diagnostics Extractor Framework (EFWK)
Authorizations for Business Process Analytics
Solution with defined systems and business processes
6 May 2011
BPMon Analytics with SAP Solution Manager
(1) Start transaction SE18, choose the radio button 'BAdI Name' and enter WORKLOAD_STATISTIC. Press
Display button.
(2) In menu 'Implementation' choose 'Change' and select /SDF/BPM_TSTAD by double click. Then activate
this implementation.
May 2011 7
Trend Analysis Reporting with SAP Solution Manager
In Business Process Monitoring you define, for which systems and for which transactions statistical
performance data are transferred into SAP Solution Manager's BPMon BW Info Cube. The Data Collection
can be set up in the Business Process Monitoring Setup Session, which you can enter via Solution Manager
Workcenter.
8 May 2011
BPMon Analytics with SAP Solution Manager
Select the monitor 'PerfMon: Techn. Performance for Reporting' from F4-Help. You can define your own
Monitoring Object Name.
May 2011 9
Trend Analysis Reporting with SAP Solution Manager
For some of the key figures a threshold parameter has to be set. This allows monitoring the performance of
dialog steps that have a runtime above the degradation threshold that you maintain using this parameter.
Creating key figures for statistical records above a threshold makes sense in cases where transaction
runtime is regularly having runaway values, i.e. the transaction runtime regularly exceeds the average
runtime highly. It is not possible to monitor these sporadic increases in response time by only looking at the
average values. By using key figures with defined thresholds you can monitor the number and total runtimes
of these regularly runaways. In this way you can later set up alerting for the average response time values of
the transaction and for the runaway values, too.
Below pictures illustrate the necessity for using a degradation threshold. Although in both cases the average
response time is equal for the measured dialog steps, we have in the 2nd picture long running dialog steps,
which should be monitored.
Let's build a business example: The save operation of transaction VA01 - 'Create Sales Order' should be
monitored. In most executions (99%) the number of line items is very low. However there are some few big
customers ordering a lot and the response time for these orders is much higher. Because big orders have a
10 May 2011
BPMon Analytics with SAP Solution Manager
high value, they should be processed quickly. So you want to monitor the total runtime of these big orders.
With using a degradation threshold this is possible.
Below is the list of the performance monitoring related key figures (alert types) of Application Monitor
'PerfMon: Techn. Performance for Reporting'.
Avg. Runtime The "Avg. Runtime" key figure measures the average response time of the
monitored transaction(s) within the penultimate full hour.
Avg. Database Time The "Avg. Database Time" key figure measures the average database time (part
of the response time) of the monitored transaction(s) within the penultimate full
hour.
Avg. CPU Time The "Avg. CPU Time" key figure measures the average CPU time of the
monitored transaction(s) within the penultimate full hour.
Avg. GUI Time The "Avg. GUI Time" key figure measures the average GUI time (part of the
response time) of the monitored transaction(s) during the penultimate full hour
Avg. Frontend Network The "Avg. Frontend Network Time" key figure measures the average front end
Time network time of the monitored transaction(s) during the penultimate full hour.
Total Runtime The "Total Runtime" key figure measures the total runtime of the monitored
transaction(s) during the penultimate full hour.
Total Database Time The "Total Database Time" key figure measures the total database time of the
monitored transaction(s) during the penultimate full hour.
Total CPU Time The "Total CPU Time" key figure measures the total CPU time of the monitored
transaction(s) during the penultimate full hour.
Total GUI Time The "Total GUI Time" key figure measures the total GUI time of the monitored
transaction(s) during the penultimate full hour.
Total Frontend Network The "Total Frontend Network Time" key figure measures the total front end
Time network time of the monitored transaction(s) during the penultimate full hour.
Number of Records The "Number of records" key figure measures the number of statistical records (=
number of dialog steps) of the monitored transaction(s) during the penultimate
full hour.
Number of Records The key figure "Number of Records Above Threshold" measures the number of
above Threshold statistical records (= number of dialog steps) in the monitored transaction(s)
during the penultimate full hour that have a longer runtime than the specified
degradation threshold.
Total Runtime of The key figure "Total Runtime of Records Above Threshold" measures the total
Records above runtime for statistical records (= number of dialog steps) in the monitored
Threshold transaction(s) during the penultimate full hour that have a longer runtime than the
specified degradation threshold.
Total DB Time of The key figure "Total DB Time of Records Above Threshold" measures the total
Records above database time for statistical records (= number of dialog steps) in the monitored
Threshold transaction(s) during the penultimate full hour that have a longer runtime than the
specified degradation threshold.
May 2011 11
Trend Analysis Reporting with SAP Solution Manager
Total CPU Time of The key figure "Total CPU Time of Records Above Threshold" measures the total
Records above CPU time for statistical records (= number of dialog steps) in the monitored
Threshold transaction(s) during the penultimate full hour that have a longer runtime than the
specified degradation threshold.
12 May 2011
BPMon Analytics with SAP Solution Manager
Normally you will want to monitor transactions during business hours. As period we suggest to enter 60
minutes. It does not make sense to decrease the period, as the data that is extracted from the managed
system is created hourly by basis report RSColl00.
May 2011 13
Trend Analysis Reporting with SAP Solution Manager
14 May 2011
BPMon Analytics with SAP Solution Manager
To avoid problems during usage of BPMon Analytics with increasing response times of the BPMon Analytics
UI or with increasing growth of data storage use of Info Cube 0SM_BPMRH, especially its fact table
/BI0/F0SM_BPMRH, we recommend to activate a housekeeping for the Info Cube in BW according to SAP
Note 1514022 (BPMon Analytics - BW Housekeeping for Info Cube).
May 2011 15
Trend Analysis Reporting with SAP Solution Manager
In order to use Alerting based on the performance data available in the SAP Solution Manager's BPMon BW
Info Cube, the data collection had to be configured and activated before on the level of logical components in
the BPMon Setup session as described above.
For the process step select "Application Monitors: Cross Application" and save.
16 May 2011
BPMon Analytics with SAP Solution Manager
You may have configured to collect the performance data of several transactions into the SAP Solution
Manager's BW. On business step level you can filter for specific transactions now.
May 2011 17
Trend Analysis Reporting with SAP Solution Manager
Proceed with defining Analysis & Monitoring Tools, Monitoring Activities and Notifications & Service Desk as
for non BW based alerting.
The alert message contains information about the measured value of the key figure, e.g. the average
response time of a transaction of the penultimate hour. With the alert list you can see the measured values
of all preceding hours.
18 May 2011
BPMon Analytics with SAP Solution Manager
For details on the Alert Inbox see the corresponding chapter in the “Setup Guide - Business Process
Monitoring”, that is available at http://www.service.sap.com/bpm in the “Media Library” under “Technical
Information”.
May 2011 19