0% found this document useful (0 votes)
4 views19 pages

Setup Guide - PerfMon

Uploaded by

Vladimir Valov
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views19 pages

Setup Guide - PerfMon

Uploaded by

Vladimir Valov
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 19

BPMon PerfMon: Techn.

Performance for Reporting -


Setup Guide

PerfMon: Techn.
Performance for
Reporting

with SAP Solution


Manager 7.0

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.

ORACLE® is a registered trademark of ORACLE Corporation. Disclaimer


Some components of this product are based on Java™. Any code
® ® ® ®
UNIX , X/Open , OSF/1 , and Motif are registered trademarks of change in these components may cause unpredictable and severe
the Open Group. malfunctions and is therefore expressively prohibited, as is any
decompilation of these components.
Citrix®, the Citrix logo, ICA®, Program Neighborhood ®, MetaFrame®,
WinFrame®, VideoFrame®, MultiWin® and other Citrix product names Any Java™ Source Code delivered with this product is only to be used
referenced herein are trademarks of Citrix Systems, Inc. by SAP’s Support Services and may not be modified or altered in any
way.
HTML, DHTML, XML, XHTML are trademarks or registered
trademarks of W3C®, World Wide Web Consortium, Massachusetts
Institute of Technology. Documentation in the SAP Service Marketplace
You can find this documentation at the following address:
http://service.sap.com/bpm
BPMon Analytics with SAP Solution Manager

Table of Contents
1 INTRODUCTION AND MOTIVATION ................................................................................................... 4
1.1 Monitoring Objects using Statistical Records for Performance .................................................... 4
1.2 Further Setup Guides....................................................................................................................... 5

2 TECHNICAL PREREQUISITES FOR EXTRACTION OF PERFORMANCE STATISTICS ..................... 6


2.1 Required Software Components ..................................................................................................... 6
2.2 Implement Business Process Analytics ......................................................................................... 6
2.3 Required SAP Notes ........................................................................................................................ 6
2.4 Activate BADI implementation ........................................................................................................ 6
2.5 Schedule report /SDF/BPM_REORG_TSTAD .................................................................................. 7

3 SETUP DATA COLLECTION IN BPMON SETUP SESSION ................................................................ 8


3.1 Update Repository and Select Systems.......................................................................................... 8
3.2 Select Performance Monitor ............................................................................................................ 9
3.3 Select Key Figures ........................................................................................................................... 9
3.4 Enter Selection Criterias.................................................................................................................12
3.5 Set Monitoring Schedule ................................................................................................................12
3.6 Activate Monitoring.........................................................................................................................13
3.7 Master Data Load ............................................................................................................................13
3.8 Trend Analysis with Business Process Analytics .........................................................................14
3.9 Housekeeping of Data Storage in BPMon Analytics .....................................................................15

4 SETUP ALERTING IN BPMON SETUP SESSION ..............................................................................16


4.1 Select Business Process and Step ................................................................................................16
4.2 Create Application Monitor with Reference ...................................................................................16
4.3 Select Key Figure and Transaction for Alerting ............................................................................17
4.4 Define Thresholds ...........................................................................................................................18
4.5 Generate and Activate Customizing...............................................................................................18
4.6 Check Performance Key Figures in Alert Inbox ............................................................................18

May 2011 3
Trend Analysis Reporting with SAP Solution Manager

1 Introduction and Motivation

The performance of the main business transactions is most crucial for the daily operations. Bad performance
of main business transactions can cause that

• dialog user have to wait for system response,


• business is delayed or even can't be performed,
• system load is increased and leads to hardware bottlenecks, so that the overall system slows down.

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.

1.1 Monitoring Objects using Statistical Records for Performance


The SAP Solution Manager collects specified data from managed systems and makes it centrally available
for alerting and reporting. With Business Process Monitoring (BPMon) different kinds of monitoring objects
are offered, to retrieve technical and business data.

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:

Monitor Name Monitoring Type / Advantages Disadvantages


Techn. Name

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

1.2 Further Setup Guides


In this setup guide we will explain how to set up the application monitor 'PerfMon: Techn. Performance for
Reporting'. This setup guide will not explain the general procedure for using and setting up BPMon and BP
Analytics. The setup guides for BPMon and BP Analytics are available at http://www.service.sap.com/bpm in
the “Media Library” under “Technical Information” and should be regarded as basis documents for this setup
guide.

May 2011 5
Trend Analysis Reporting with SAP Solution Manager

2 Technical Prerequisites for Extraction of Performance Statistics


As technical precondition for performance monitoring with the monitoring object monitor 'PerfMon: Techn.
Performance for Reporting' the statistical performance data extraction from the managed system into the
SAP Solutions Manager's BW has to be set up. For this the infrastructure provided by Business Process
Analytics is used. Additionally a BADI has to be activated in the managed system.

2.1 Required Software Components


In order to setup and use the monitoring object 'PerfMon: Techn. Performance for Reporting', the following
releases of software components are necessary:
Solution Manager 7.0 SPS 23 (ST 400 SP23, BI_CONT 7.04 SP6, ST A/PI Type M)
Each connected managed system must have at least installed
o SAP_BASIS 700,
o ST-PI 2008_1_700 SP4
o ST-A/PI 01M* SP1

2.2 Implement Business Process Analytics

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

2.3 Required SAP Notes


Following corrections should be implemented (in addition to the SAP Notes mentioned in the 'Setup Guide -
Business Process Analytics'):

SAP Note Corrected with


1494650 BPMon: Wrong Alerting Values in new Performance Monitoring ST 400 SAPKITL435
1598647 BPMon: PerfMon: Reorganization of Table /sdf/bpm_tstad ST-PI 2008_1_700 SP5

2.4 Activate BADI implementation


In the managed system activate the implementation /SDF/BPM_STORE_STAD of the BADI
“WORKLOAD_STATISTIC”.
This BADI is called during the run of the report SWNCColl which is triggered by the RSColl00 mechanism.
The report SWNCColl is reading the STAD records from the application server instances. The task of the
BADI implementation is to store the STAD records for the transactions for which BPMon is activated into the
table /SDF/BPM_TSTAD.
Details how to activate the classic BAdI implementations in a SAP system:

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.

2.5 Schedule report /SDF/BPM_REORG_TSTAD


Schedule a daily job executing report /SDF/BPM_REORG_TSTAD with an appropriate variant to delete data
from the /SDF/BPM_TSTAD table. E.g. you can delete the statistical records that are older than 24 hours.
The BPMon Data Collector, that is normally scheduled hourly, has then already extracted the statistical data
to the Solution Manager BW.

May 2011 7
Trend Analysis Reporting with SAP Solution Manager

3 Setup Data Collection in BPMon Setup Session

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.

3.1 Update Repository and Select Systems


The application monitor 'PerfMon: Techn. Performance for Reporting' is delivered with add-on ST-A/PI on the
managed systems. To make the monitor available in the SAP Solution Manager, the monitor definition need
to be transferred from the managed system to a central repository in the SAP Solution Manager System. As
a sub-node within the Basis Settings an update of Central Application Monitoring Repository is offered. To
get the monitors available it is required to select the managed system first and then to click the button “Load
Monitors”.

8 May 2011
BPMon Analytics with SAP Solution Manager

The logical components (i.e. system and client combination


in the leading role for the solution) from which data should be
collected for reporting have to be selected.

3.2 Select Performance Monitor

The node "Application Monitors" below the


selected logical component allows to select the
monitors for data collection. Select Monitoring
Type "Application Monitors: Cross Application".

Select the monitor 'PerfMon: Techn. Performance for Reporting' from F4-Help. You can define your own
Monitoring Object Name.

3.3 Select Key Figures


On tab “Key Figures” you define, which key figures to be evaluated.

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'.

Key Figure Description

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.

3.4 Enter Selection Criterias


On the "Detail Information" tab page, double-click the field in the "Counter" column. In the pop-up, enter the
transaction(s) that you want to monitor, select the "Group by" checkbox for the transaction parameter, and
press F8 (execute).

You can also use the following parameters:


Report: Name of the ABAP report
Function code: The function code can be used to monitor separate steps of a transaction. The
function code is also known as the "CUA internal command".
Call type: Type of statistical record such as DIA, BTC, RFC, or UPD
Instance: Application server instance
Threshold for Degr.: This parameter is valid only if you want to use one of the following key figures:
"Total Runtime of Records Above Threshold", "Total DB Time of Records Above Threshold", or
"Total CPI Time of Records Above Threshold". With these key figures, you can monitor the
performance of dialog steps that have a runtime above the degradation threshold that you maintain
using this parameter.

3.5 Set Monitoring Schedule


Within the tab “Monitoring Schedule” the user can decide how often a data collection should run.

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.

3.6 Activate Monitoring


After you have set the sub checks of the monitor to 'Done' (green hook), generate and activate the
monitoring.

The extractor for the transactional data is started.

3.7 Master Data Load


A second extractor is needed for extracting the transaction related master data. The master data contains in
this case the transaction names in different languages.
Flag the line with Semantic ID 'BC_TCODE' and press button "Load BW Master Data". The status of the
Master Data Load will be set to 'Scheduled'. After some minutes after pressing "Refresh" the status will
change to 'Loaded'.

May 2011 13
Trend Analysis Reporting with SAP Solution Manager

3.8 Trend Analysis with Business Process Analytics


After the data collection has been set up and the data
extraction took place, you can evaluate the measured key
figures with Business Process Analytics. This is available via
a link under 'Common Tasks' in the left navigation area in the
BPO work center. In case performance problems with a
monitored transaction occur, you can check if there is a trend
with increasing response times of a transaction, or if there
are peaks depending of the weekday or seasons.

To display performance history:


1. Select a time frame (where data was already extracted).
2. Select the relevant application monitor.
3. Select transaction.
4. Press button Trend Analysis.

14 May 2011
BPMon Analytics with SAP Solution Manager

3.9 Housekeeping of Data Storage in BPMon Analytics

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

4 Setup Alerting in BPMon Setup Session

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.

4.1 Select Business Process and Step


Access the BPMon Setup session via the SAP Solution Manager Workcenter for Business Process
Operations and start the BPMon setup. Within the node of business processes select first the relevant
business process, then in the subtree the relevant business process step(s).

For the process step select "Application Monitors: Cross Application" and save.

4.2 Create Application Monitor with Reference


In the check "Applications Monitors" choose pushbutton "Create with Reference". Now the available
monitoring objects for BW data are shown and can be selected. Select the monitoring object defined for
collecting performance data.

16 May 2011
BPMon Analytics with SAP Solution Manager

4.3 Select Key Figure and Transaction for Alerting


Select the key figures you want to configure alerting for.

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

4.4 Define Thresholds


Enter the thresholds for yellow and red alerts.

Proceed with defining Analysis & Monitoring Tools, Monitoring Activities and Notifications & Service Desk as
for non BW based alerting.

4.5 Generate and Activate Customizing


To finalize the BPMon process generate and activate the customizing.

4.6 Check Performance Key Figures in Alert Inbox


The Alert Inbox is in SAP Solution Manager the central point for Alert handling. If set up, email notifications
on alerts can be can be sent out with customized messages to the operator automatically. From the email
the operator has direct access to the alert inbox.
Below is a screenshot of the Alert Inbox that shows alerts regarding performance.

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

You might also like