You are on page 1of 67

SAP EarlyWatch Alert

SAP Active Global Support SAP AG

Agenda

EarlyWatch

Alert und EarlyWatch Alert for Solutions

EarlyWatch

Alert in your Solution Manager

Chapter

by Chapter

How to get to the EWA Configuration: Alternative 1

Transaction SOLMAN_WORKCENTER: Tab SAP Solution Manger Administration

How to get to the EWA Configuration: Alternative 2

2 3

Transaction SOLMAN_WORKCENTER: Tab SAP Solution Manger Administration

EWA Administration

Checkbox does not work, see SAP Note 1362950. Fixed with ST 400 SP 21.

Default will be changed to yes in ST 400 SP23.

Find EWA Reports in Solution Manager Alternative I


Transaction SOLMAN_WORKCENTER: System Monitoring

2 3

Find EWA Reports in Solution Manager Alternative II


Transaction SOLMAN_WORKCENTER: Tab SAP Engagement and Service Delivery

2 3

Monitoring in Solution Manager


SAP Solution Manager
Business Process Monitoring
Business Processes Repository

SAP EarlyWatch Alert for Solutions

System Monitoring

SAP EarlyWatch Alerts

Satellite Systems

Real-time Monitoring: CCMS Monitoring Infrastructure (RZ20)

Weekly Evaluation: Service Data Download (SDCC), E2E Diagnostics

Next Generation: SAP EarlyWatch Alert for Solutions


SAP EarlyWatch Alert

SAP EarlyWatch Alert for Solutions

Pro-active System evaluation at SAP or in Solution Manager Based on a single system Gives System KPIs Statistics on single transactions/reports Raises System Alerts Shows long-term histories of KPIs

is powered by SAP Solution Manager including Diagnostics Based on system landscape Gives aggregated Solution KPIs Performance of core business processes Classifies alerts in areas for improvement Shows trends and correlation Tracks changes in the landscape

In Solution Manager or @SAP

Monitored System

CUSTOMER
SAP Solution Manager Service Marketplace

Monitored System

RFC Data transfer

Monitored System

Alternative RFC Data transfer

Service Tools and Plug-ins

Monitored System
ST-PI ST-A/PI

CUSTOMER
SAP Solution Manager
RFC Data transfer
SolMan Tool: ST 400 SP

Service Marketplace

Monitored System
ST-PI ST-A/PI

Service Tools: ST-SER 701_2008_2 SP

Monitored System
ST-PI ST-A/PI

Alternative RFC Data transfer

*described in SAP Note 1143775

New concept: Service Content Update

Monitored System
ST-PI ST-A/PI

CUSTOMER
SAP Solution Manager
RFC Data transfer
SolMan Tool: ST 400 SP >15

Service Marketplace

Monitored System
ST-PI ST-A/PI

Service Tools: ST-SER 701_2010_1 + Service Content Update*

Monitored System
ST-PI ST-A/PI

Alternative RFC Data transfer

*described in SAP Note 1143775

In Solution Manager or @SAP

You should use your local Solution Manager for EWA, because:

Content about Java components is only available there. Prerequisites is Solution Manager Diagnostics. New EWA content for CRM systems is read from Solution Manager BI More checks are currently developed to read from SolMan BI, e.g. for ABAP Workload Analysis Prerequisite for EarlyWatch Alert for Solutions.

Data sources for EWA


CUSTOMER
SAP Inst Customer System

Solution Manager
Diagnostic Agent Wily IntroScope SM Diagnostics CCDB
Configuration and Change DB

EWA
local report

EWA
processed by SAP

Solution Manager

BI Statistics
Service Data Control Center

SDCCN

SDCCN

The EWA report in your local Solution Manager has additional data sources from Solution Manager Diagnostics.

Integration of Solution Manager and EarlyWatch Alert


Data Basis used for Solution Manager Diagnostics is now integrated into the EarlyWatch Alert Detailed time profile, peak workload and error analysis is now possible!
CRM: SAP Solution Manager

SMD BI

History of max. & avg. number of BDocs and qRFC and R&R* queue entries History of CRM Mobile Synchronizations History of ICM Load Day of highest Load: 24-hour time profiles of CRM Mobile synchronizations, qRFC and R&R Queues and BDocs

New Content in EWA due to Integration

EWA

*Replication and Realignment Queue

The Report: Chapter by Chapter

Determined automatically from table T000: If there is any client with field CCCATEGORY containing the value 'P then Productive, else Non-Productive.

From which rating does the overall rating get the red rating?

SAP BW:

Java:

KPI's Query Performance Minimum SPS BWA Memory Usage

Garbage Collection Performance and Fill Level Old Space Usage Request Bottleneck

SAP CRM:

Database:

Unprocessed BDoc messages BDocs in error status BDocs waiting for external receivers Replication and Realignment Queues Mobile Client Message Recovery unextracted messages

Database Performance Missing indexes SQL Server with outdated DLL

General:

SAP PI / XI :

Performance Message Errors

System Performance (Performance Evaluation, DB Profile, HW Capacity) Problems in qRFC queue Different Kernel Version or Patch Kernel needs Updating MDMP Support

Report Chapters

Service Summary Performance Indicators System Configuration Performance Overview Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Service Summary Performance Indicators System Configuration Performance Overview Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Reason for red report

Critical area, but not decisive for report rating

Alert propagation

Critical issues

Service Summary Performance Indicators System Configuration Performance Overview Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Key Performance Indicators (KPIs)

General tendency compared to the last SAP EWA Report.

Key Performance Indicators (KPIs)


< 500 users: 500-2000 users: > 2000 users: small system medium-sized system large system

should be < 1 sec, depends on customer requirements

should be 100% < 5.000 DS/h: small system 5.000-100.000 DS/hmedium-sized system > 100.000 DS/h: large system

Performance Indicators and their trend

< 1000ms

< 50% of 1

Response time is high due to high DB times for sequential reads.

< 2 ms <10 ms < 25 ms

Service Summary Performance Indicators System Configuration Performance Overview Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

For information on database and operating system platforms, see Databases and OS on SDN. To verify this information in your system, choose System -> Status.

Information taken from transaction ST06.

System Configuration

SAP 2007 / Page 28

Kernel check decisive for report red


To verify which SAP Kernel Release is installed in your system, in your SAP System, call transaction SM51 and choose Release Notes. The release is indicated in the row Kernel Patch number.

Service Summary Performance Indicators System Configuration Performance Overview Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Summary: Response Time Components


Presentation Layer Network = LAN / WAN
Wait queue (memory)

Dispatcher Wait time


Work process
Roll memory

Application Layer

Roll buffer Extended memory Roll file Network = LAN

Response time
Shared Pool Buffers

Roll-in time. . .
Database Interface

Database time Database process Database Layer

Database buffers

Workload Statistics (I)

CPU time

Network

Wait time

Roll in

Load time

Processing time

Network

Database time

Response time

Presentation Server

Application Server

Database Server

Response time: Start: User request enters dispatcher queue; End: Next screen is returned to the user. Wait time: Request is waiting in dispatcher queue for a free work process. Roll-in time: User context information is rolled into the work process. Load time: Load from the database and generate objects like ABAP source code, CUA, and screen information. Database request time: Starts in database interface on application server; ends when database has delivered resu Processing time = Response time (wait time + database time + load time + roll time + enqueue time) CPU time: This is the CPU time used by the R/3 work process.

Workload Monitor points us to the cause of the performance problem (I)


Problem symptoms: Large roll-wait time Performance problem? Check: Workload on all servers

Large load time Large database request times


(Cont.)

Yes All transactions affected? No Program analysis

Large CPU times (Average)

Processing time much larger than CPU time

Workload Monitor points us to the cause of the performance problem (II)

May be caused by:


Large roll-wait time Communication problem with GUI or external system

Large load time Large database request times

Program buffer, CUA buffer, or screen buffer too small CPU/memory bottleneck on database server, network problems, expensive SQL statements, database locks, missing indexes, missing statistics, small buffers Expensive ABAP processing, for example, processing large tables, frequent accessing of R/3 buffers CPU bottlenecks, network problems, communication problems

Large CPU times (Average)

Processing time much larger than CPU time

Workload Statistics by Task Type

Should be < 1000ms

Should be < 50% of response time

Rating details for Performance Evaluation


-RED if at least three time ranges are rated RED - YELLOW if at least two time ranges are rated RED or at least three time ranges are rated YELLOW - Otherwise, GREEN

Transaction Profile I

The Transaction Profile shows the statistical data aggregated by transaction

Display variant 1: sorted by total response time (= load caused on the system by this transaction)

Transaction Profile II

The Transaction Profile shows the statistical data aggregated by transaction

Display variant 2: sorted by DB time (= load caused on the DB by this transaction)

Service Summary Performance Indicators System Configuration Performance Overview Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Workload by Application Module

CPU

load and DB load are displayed in a pie chart and table. Rating is always green.

DB Load Profile

The

diagram shows how many DB processes are used in parallel in a certain time frame on a weekly average. The check rating can indicate a DB bottleneck by comparing the used DB processes with the number of CPUs in the DB Server:
A YELLOW rating is set if in at least two time periods ("DB Load DIA" + "DB Load RFC" + "DB Load BTC") is larger than (3 x no. CPUs on the database server). A RED rating is set if in at least five time periods ("DB Load DIA" + "DB Load RFC" + "DB Load BTC") is larger than (3 x No CPUs on the database server).

Service Summary Performance Indicators System Configuration Performance Overview Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

SAP System Operating


Users Green <5 <25 <50 Yellow 5-20 25-100 50-200 Red >20 >100 >200

Update Errors:

<100 100-1000 >1000

Rating Scheme: Info from SM13

Table Reorganizations:

Top 20 tables and indexes (by size) are checked for their size and monthly growth. For known issues SAP Notes for reorganization are recommended. No rating propagation to chapter level.

Transports

Number of transported objects and programs in the last week are shown (SAP, Customer or in SP). Rating is always green

Program Errors (ABAP Dumps)

Rating Scheme:

Green <30

Yellow >30

Service Summary Performance Indicators System Configuration Performance Overview Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Hardware Capacity

ST06: User avg + Sys avg

CPU load thresholds: yellow 75 %, red 90% Paging thresholds depend on components, e.g. Java and Database server more sensible

EW Report I

CPU utilization < 75% No CPU bottleneck


Avg. Paging/h < 20% of RAM No Memory bottleneck

EW Report II

CPU utilization > 75% Temporary CPU bottleneck Avg. Paging/h > 20% of RAM Temporary Memory bottleneck

Key Performance Indicators (KPIs)

Consequences

Hardware bottlenecks (especially long-lasting ones) harm the performance of all users on this one machine This is especially critical on the DB server, since here a hardware bottleneck will harm the overall system performance

The

database server is a unique resource in the R/3 system All users suffer from increased response times !
Ensure that there never is a CPU bottleneck on the database server (!)

Service Summary Performance Indicators System Configuration Performance Overview Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Unsuccessful Security Check

Security Checks are described in SAP Note 863362.

Successful Security Check

User Authorizations

Yellow alert, if: More than 10% of the users (but at least 10) of a client. or More than 75 users of a client have the authorization. No red alert!

Service Summary Performance Indicators System Configuration Performance Overview Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

SAP 2007 / Page 56

Failed Changes

SAP 2007 / Page 57

Service Summary Performance Indicators System Configuration Performance Overview


Chapter content is DB vendor specific and will not be covered in this presentation.

Workload Distribution SAP System Operating Hardware Capacity Security Software Change Management Database Performance Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Service Summary Service Summary Performance Indicators Performance Indicators System Configuration System Configuration Performance Overview
Chapter content is DB vendor specific and will only be covered in an overview.

Performance Overview Workload Distribution Workload Distribution SAP System Operating SAP System Operating Hardware Capacity Security HardwareChange Software Capacity Management Database Settings Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Database Administration

Database

Growth and Free Space Development are shown

Backup

and Archive Frequency is checked

Free

Space in tablespaces and space critical objects are investigated

DB

Release is checked

Service Summary Service Summary Performance Indicators Performance Indicators System Configuration System Configuration Performance Overview Performance Overview Workload Distribution Workload Distribution SAP System Operating SAP System Operating Hardware Capacity Security HardwareChange Software Capacity Management Database Settings Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Expensive Statements

DB time in dialog < 400ms or less than 100 mio. reads/day

DB time in dialog > 600ms and more than 500 mio. reads/day

Expensive Statements

Records/Exe. = 3 -> selective!

Buffer gets/ records = 19600 -> inefficient access!

Explain plan and Origin of Coding

Service Summary Service Summary Performance Indicators Performance Indicators System Configuration System Configuration Performance Overview Performance Overview Workload Distribution Workload Distribution SAP System Operating SAP System Operating Hardware Capacity Security HardwareChange Software Capacity Management Database Settings Database Administration Database Server Load from Expensive SQL Statements Trend Analysis

Trends in Activity and Performance

Top 5 Transactions by total load

System Operating

Availability in EWA is based on Collector protocols only. It is an hourly "life sign monitoring" of the ABAP stack central instance. In Solution Manager the CCMSPING-based availability measurement allows you to monitor the central instances (ABAP and JAVA), instance availability, instance logon availability, and the SAP logon groups by the minute. For details see SAP Note 1332677.

You might also like