global performance analysis bernd f. lober sap ag

Global Performance Analysis

Bernd F. Lober SAP AG

SAP AG 2003, Global Performance Analysis / 2

Agenda

Introducing Global Performance Analysis

Understanding Global Performance Analysis

Conducting a Manual Analysis

Possibilities for Automatic Analysis

Summary


Introducing the Global Performance Analysis (1)

Motivation As system landscapes become increasingly complex, it is

necessary to monitor performance across system boundaries Deliver performance results of all (possibly unknown)

application/system components covered by a specific business process

Automatic performance analysis, for example: For pre-defined scenarios For regression tests

Global Performance Analysis (GPA) Transaction code ST30 Available since

4.6C for SAP Basis 6.10 for SAP Web Application Server


Introducing the Global Performance Analysis (2)

Provide an overview of complex system landscapes For performance analysis across different system components To analyze possible performance bottlenecks that may occur in a system

landscape To collect performance figures across system borders in one centrally located

system Trace data and statistical records are saved to this centrally located system

Collect performance figures Trace data (compare transaction ST05) Statistical records (compare transactions STAD, ST03, ST03N, ST03G,

STATTRACE) Only those figures that belong to the same logical entity are selected

Saving log data on database

Automatic performance analysis uses remotely controlled test cases (CATTs) and test configurations (eCATT)


Agenda





Summary


Functions of the Global Performance Analysis

Central monitoring and test tool across system components To analyze performance in a complex SAP system landscape To collect performance figures across system boundaries In a central system

Trace data (compare ST05) and Statistical records (compare STAD)

Collect performance data on a database for later comparison and statistical evaluation

System performance figures that belong together are tied together logically

That is: GPA only considers data concerning the business processes that are to be examined


More Functions: Global Performance Analysis

Automatic performance analysis In an SAP system landscape Transaction ST30

Automatic performance analysis for "single" transactions and business processes in a SAP system landscape

Using remotely controlled eCATT test configurations eCATT is a tool for cross component testing in a system landscape The eCATT functionality is available from Web Application Server (Web

AS) 6.20 on but tests can be done down to release 4.6C


eCATT – Overview

eCATT Is a test execution and comparison tool for functional testing Is suited for

Unit tests Integration testsSystem testsAcceptance testsVerification tests

Compares and protocols test results with expected outcomes Designed as a central test system

Integrated into the Test OrganizerTests local and remote systemsParameterization of commands and test casesScripting language for controlling test execution flow


Features of the Global Performance Analysis

Within GPA, performance figures are Collected automatically on the central system‘s database Presented as average values resulting from multiple runs of the

scenarios that are to evaluate As of WAS 6.20 SP23

Presented using evaluation patterns to get an individual overview that is: performance data are filtered as you like

As of WAS 6.20 SP23

Compared automatically between different test runs As of WAS 6.20 SP23

Evaluated automatically against the performance checklist conditions with result „conditions met“ or not (including description why)

As of WAS 6.20 SP23


Positioning the Global Performance Analysis

Automatic

testing

Hands-on

testing

Single

systems

Multiple

systems

SE30

ST05

ST30

SCI


Understanding the Global Performance Analysis

The GPA is a tool to help you evaluate the SAP product standard "Performance"

Appropriate Indexes

No identical selects

SAP bufferComplete WHERE clauses

Parallel processing

enabled

Linear depen-dency

Two commu-nication steps per

dialog step

Average dialog time

below 2 seconds

SCI x x x x

ST05 x x x x x x

ST30 x x x x

ST03N x

SE30 x

x

x

Database Application Frontend


Example of a Business Process Across Different Components and Systems

Internet Pricing

& Configurator

SAP CRM

Internet Sales

mySAP CRM Internet Sales Scenario (CRM ISA) A sales order is created using SAP GUI for HTML (component SAP ITS) Processed in SAP Internet Sales (component ISA) A financial document is created in SAP R/3 The selling information is sent to BW and APO for further analysis

SAP R/3 Text Retrieval

& Information

SAP BW SAP APO

Internet Transaction

Server

User

Request


Example: System Landscape Process

User

Request


Server

SAP BW SAP APO

Internet Pricing

& Configurator

Text Retrieval

& Information

SAP CRM

Internet Sales

SAP R/3


Server

Internet Pricing

& Configurator

Text Retrieval

& Information

SAP CRM

Internet Sales

SAP R/3

SAP BW SAP APOSAP BW SAP APO

Internet Pricing

& Configurator

Text Retrieval

& Information

SAP CRM

Internet Sales

SAP R/3


Server


Example: System Landscape Process


Server

SAP BW SAP APO

Internet Pricing

& Configurator

Text Retrieval

& Information

SAP CRM

Internet Sales

SAP R/3


Server

Internet Pricing

& Configurator

Text Retrieval

& Information

SAP CRM

Internet Sales

SAP R/3

SAP BW SAP APOSAP BW SAP APO

Internet Pricing

& Configurator

Text Retrieval

& Information

SAP CRM

Internet Sales

SAP R/3


Server

Central Monitoring System

(ST30, DB, test cases,

test configurations)


Agenda





Summary


Initial Screen for Manual Analysis

Switch traces on and off for remote system

components

Go to other system components for detailed analysis

Enter system components

manually


Manual Analysis: Maintaining Test Data Descriptions

Maintain performance data description.

Request data from system components.

Save data on database.


Agenda





Summary


Automatic Analysis With Test Cases

Do an automatic performance test by

running test cases that are assigned to a log ID


Automatic Analysis With eCATT Test Configurations

Enter a log ID and a text

Run the specified test configuration

Performance figures are automatically collected and stored on the database


Automatic Analysis With eCATT Test Configurations

After starting the eCATT test run you can set its parameters on the following screen

Accept the proposed values


Global Performance Analysis: Comparison

Result screen of a “Test and compare” analysis


Using Global Performance Analysis

Preconditions Test scenario in form of test configurations defined within eCATT

Important for regression testing -> makes life much easier

Profiles S_TOOLS_EX S_ADMI_FCD Profile to run ST05

Authorization To run function groups

ECATT_EXECUTE SSQ0 SAPWL_STAT

To do RFCs


Planned Functions

Trace follow up across system borders over several steps is done automatically

Since the data is retrieved automatically, you do not need to know which systems are actually involved

Integration of non-WebAS components (ITS, IPC, ...)

Integration of Code Inspector functionality to examine trace data Example: According to the Performance Standard there should be

appropriate indexes Note: not only static SQL, which is what the Code Inspector analyzes,

but also dynamic SQL can be analyzed, which is what the Code Inspector cannot do


Agenda





Summary


Global Performance Analysis - Summary

The performance relevant data are

Collected automatically on the central system‘s database

Presented as average values resulting from multiple runs of the szenarios that are to evaluate

Compared automatically between different performance tests

Evaluated automatically against possible performance checklist conditions with result „conditions met“ or not Including a detailed description why


Questions and Answers

global performance analysis bernd f. lober sap ag

Documents

stadcollect performance

system boundariesin

system borders

sap system landscapeusing

complex sap system landscapeto

test tool

central system trace

different system componentsto