efficient monitoring for sap netweaverbw-alm270

8/10/2019 Efficient Monitoring for SAP NetWeaverBW-ALM270

http://slidepdf.com/reader/full/efficient-monitoring-for-sap-netweaverbw-alm270 1/95

Mathias Bley and Janko Budzisch / SAP Active Global SupportSeptember, 2011

ALM270

Efficient Monitoring for SAP NetWeaveand SAP BusinessObjects



© 2011 SAP AG. All rights reserved.

Disclaimer

This presentation outlines our general product direction and should not be relied on

purchase decision. This presentation is not subject to your license agreement or anywith SAP. SAP has no obligation to pursue any course of business outlined in this pr

develop or release any functionality mentioned in this presentation. This presentation

strategy and possible future developments are subject to change and may be chang

time for any reason without notice. This document is provided without a warranty of a

express or implied, including but not limited to, the implied warranties of merchantab

particular purpose, or non-infringement. SAP assumes no responsibility for errors or

document, except if such damages were caused by SAP intentionally or grossly neg




Agenda

Technical Operations

Monitoring and Alerting Infrastructure

Business Intelligence Monitoring

Introduction

Configuration

Monitoring

Alerting

Supportability for Business Objects



Technical Operations


http://slidepdf.com/reader/full/efficient-monitoring-for-sap-netweaverbw-alm270 5/95© 2011 SAP AG. All rights reserved.

Orchestrated Accelerated Innovation

Run SAP Like

A Factory

ApplicationLifecycle

Management

Accelerated

Innovation

Orchestration

Cloud

New DB technologies

(ASE; SAP HANA)

Integrated M

Next Genera

Intelligence &

Integration

Validation

• Single sou

• Total Cost

• Protection

• Business Continuity

• Total Cost of Operations • Quality



Orchestrate Your Solution with SAP Solution Manager

Run SAP

like a

Factory M

SingleSourceof Truth

Integration

Validation



Scope of technical operations

IT I nfrastructureOperat ions

Appl icat ion

Operat ions

BusinessProcess

Operat ions

ABAP J2EE

SolutionsBusiness Processes

Business Process Steps

End-Users & Technical Scenario

Products & Product Instances

Interfaces & Jobs

Applications & SystemsDatabases & Operating Systems

Physical & Virtual Hosts

Printers

Disks & Storage

Network devices



Process behind technical operations

Monitor

Proactive real-time monitoring

Opt

O

Analyze

Lower mean time to problem

resolution

Notify

Reactive handling of critical

events

Report

Prove value to business



Capabilities of technical operations

Technical Monitoring and

Alerting

One infrastructure for all monitoring and

alerting covering SAP & non-SAP

Root-cause Analysis

Analyize issues in heterogeneous landscapeswith one look-and-feel

Technical Administration

Optimize operation of your IT and application

landscape

Technical Analy

From technical reporting to man

reporting, out-of-the-box and ex

Change Diagno

Ensure that your landscape is ccompliant to your policy and re

Data Volume Ma

Manage data growth and data

measures in your landscape

http://imagedirectory.wdf.sap.corp:6085/ImageLibrary/ImageDetailsView?imageId=575da6e7-86fa-4bc3-b967-cdd22416f02b

http://imagedirectory.wdf.sap.corp:6085/ImageLibrary/ImageDetailsView?imageId=01000b93-612f-41c9-b85a-885e15a2ba06

http://imagedirectory.wdf.sap.corp:6085/ImageLibrary/ImageDetailsView?imageId=47bc4ddd-5e3e-4b03-bdc1-2db095f5c066



Monitoring and Alerting

Infrastructure




Monitoring and Alerting Infrastructure – Some facts

New Infrastructure for Technical Monitoring and

Alerting Introduced with SAP Solution Manager 7.1

Based on E2E Diagnostics architecture

SAP’s new standard for central Monitoring and Alerting

―Old‖ System Monitoring work center based on central CCMS

still available

New work center ―Technical Monitoring‖ has been introduced

which contains the new applications




Monitoring and Alerting Infrastructure - Why a new infra

Advantages of new Monitoring and Alerting Infrastructure

in SAP Solution Manager 7.1 Prevent alert flooding by grouping metrics and alerts

Landscape awareness

Easier integration of new technologies

Different alert consumers can be configured

Central configuration which is automatically distributed

Central administration and self-monitoring of infrastructure

Mass configuration by using templates

Integrated reporting capabilities

Collaboration features

Graphical overview of landscape status



Business Intelligence

Monitoring - Introduction





What scenario is in scope …

SAP BusinessObjects Enterprise XI Web Application Java

Pioneer

Viewer

Crystal

Viewer

WEBI

Viewer

Platform SDKs

Web

Services

CrystalServices

Multidim. Analy. Serv.

WebIServices

CMSOthers

…..

SAP

BW

CRYSTAL XCelsius Live OfficeWEBI

HTTP

CORBA

ODBO, MDX, R

SAP Business Objects

Enterprise XI

SAP Business Warehouse

http://www.discoveractenergy.com/images/ie-icon.gif





What are the use cases to be covered …

Do the most important BW Process Chains run with good

finish successfully?

Are my Business Objects jobs executed as planned and a

with good performance?

Do I have somewhere a delay in my Business Warehouse

processing which hinders right in time delivery of business

Do I have a resource bottleneck somewhere in my Busine

solution? Am I automatically informed about it?

Did the process chain process too few records?

Were too many data packages processed in process chain

Did the BO jobs start or finish on time (start delay and end

Are BO jobs running outside a definite time window?

Are BO jobs running into a status indicating an error or wa





What is in for you ...

SA

Central system status overview for all tech

involved in SAP Business Intelligence Solu

Capability to monitor cross-system SAP Bu

process chains and single process chain s

Central monitoring of Business Objects spe

correlation to system specific metrics

Central monitoring of SAP BW queries and

Integration of Business Intelligence specific

Inbox including Notification Management, I

Management, Task Assignment and forwar

Reduce the TCO by providing one central e

combining monitors for overall status

BI Overview Monitor

System Monitor

BI Detail Monitors



DemoBrowse through Business Intelligence Monitoring




Monitoring - Configuration




BI Monitoring Configuration – SolMan Setup Work Cente

Accessible via item ―Technical Monitoring‖ within the work center ―SAP Solution Manager C

(transaction code SOLMAN_SETUP)

Allows an easy, fast and step-by-step configuration workflow / guided procedure




BI Monitoring Configuration – Configure infrastructure (

Step 2 Configure Infrastructure: Covers the sub-steps required to prepare the managed

monitoring scenario as well as generic preparation steps for enabling the monitoring infrast

‒ Step 2.1. Check Prerequisites: Includes and infrastructure prerequisites check that widetect missing steps in general infrastructure setup (e.g. not yet executed Basic Setup o

Manager).

‒ Step 2.2. Configure Manually: Contains manual activities as Agent Management, Extr

Alerting Framework and Content Customization

‒ Step 2.3. Configure Automatically: Contains automatic activities as scheduling of jobs

Connector, Event Calculation Engine, Reorganization Jobs and Content delivery




BI Monitoring Configuration – Configure infrastructure (

Step 2.4. Default Settings: Allows to customize general behavior on how to react on alerts

monitoring scenario. You can enable automatic creation of incidents and notifications and d

and persons to be informed via notifications.

Step 2.5. Work Mode Setting: Allows to customize so-called work mode settings. BI moni

enabled or disabled under certain work mode conditions. By default the BI monitoring will b

times except for ―Planned Downtimes‖.

Step 3 Update Content: Only in exceptional cases relevant for BI Monitoring.




BI Monitoring Configuration – Define Scope (1/2)

Step 4 Define Scope: Allows you to define the scope to be covered by a BI monitoring sce

monitoring scenario is defined via a guided procedure. It can contain BOE Web System La

System Layer and BW System Layer.

In the first screen you have to enter a unique name for the BI monitoring scenario and

The scenario name will be converted to upper-case.




BI Monitoring Configuration – Define Scope (2/2)

In the next screen you can select technical systems for the different layers that shall be inc

monitoring scenario

Only objects from selected technical systems can be monitored in a BI monitoring scenario (example:

monitor a process chain defined within a SAP BW system you have to include that SAP BW system in

monitoring scenario)

BO Web Application

servers may be selected

of type Tomcat, SAP J2EE,

WebSphere

S(

Any layers system list may remain empty if no such systems exist or shall not be monitored

with SolMan 7.1 SP01

only Tomcat is supported

SAP J2EE and WebSphere

are planned for SP02




BI Monitoring Configuration – Monitoring & Alerting

Step 5 Monitoring & Alerting: consists of the detailed sub-steps for the configuration of a

to be monitored (BO jobs, BW process chains, BW queries, BW templates)

The overview screen shows the status information for each sub-step. The last sub-step is activating any changes performed in the configuration sub-steps. You can either go throug

sequentially via Next or directly jump to the sub-check you want to perform.




BI Monitoring Configuration – BO Job Monitoring (1/5)

Step 5.1 Configure BO Job Monitor: Allows to define BO jobs to be monitored and per monito

and thresholds to be checked for alerting. First you have to define the BO jobs which you want

Jobs from Managed System. Available BO jobs are retrieve from the BO system matching giv

Select the BO server

system in the scenario

from which you want to

monitor jobs

You can reduce the

retrieved job list by job

name (wildcard * allowed),

BO job type and

user name of the job

owner

You can execute the

„Get Jobs...― function

multiple times with

different filter criteria

to build up the monitored

job list step by step





After BO jobs have been assigned for monitoring you can configure details per monitored j

settings (switch on/off data collection and/or alerting), thresholds or the available four metr

execution status, start time delay, execution time window and duration.

Switch on/off metric

data collection

Switch on/off alerting

Switch on/off

monitoring of job

return status (default

= on).Unsuccessful job

execution will result

in red alert.

Only finished jobs

are taken into

account.

Expected job start time

(UTC).

Not started on timethresholds

are measured

against this reference

timestamp.

Expected time

window (UTC) for the

job to start and finishwithin.

Out of time window

thresholds are

meassured against

this reference time

frame.

Thresholds in

minutes for job

start delay. No jobstart event found

within „Not started

on time― timestamp

+ threshold raises

alert.

Threshminute

startedor finis

late

Leaving yellow and red thresholds blank disables the related metric to be monitored (e.g. start

delay will not be monitored if all „Not started on time...― fields are empty. Inconsistent threshold

values or invalid time settings will not be accepted. Details can be found in the log section.





Per job you can define data collection details (after selection the job) as Collection interval

Via the Advanced flag you can flexibly define a time interval when data collection shall be

By default it will be active all the time. Setting up a flexible data collection time interval mak

recommended for any jobs that run only once per day of even less frequent to avoid data c

Keep in mind that the data collection time frame may need to be adjusted if the job

changed





Per job you can define how to react on alerts produced for BO job monitoring as Creation

or Notification of persons or groups

Default settings are inherited from the global settings as defined in Step 2.4

Incidents settings that can be adjusted:

Automatic creation of incidents (on/off)

Support component to assign the ticket to

SAP CRM type for the ticket

Automatically close alert when ticket is confirmed (on/off)

Notification settings that can be adj

Automatically notify recipients on

Recipients can be added/remove




BI Monitoring Configuration – BW Process Chains Moni

Step 5.2 Configure BW Process Chain Monitor: Allows to define SAP BW Process Chai

and per monitored process chain the metrics and thresholds to be checked for alerting. Firs

the BW process chains which you want to monitor via Get Process Chains & Steps from

matching given filter criteria.

Select the BW ABAP



monitor process chains

You can reduce the

retrieved process chain list

by chain name pattern

(wildcard * allowed),

step job type andvariant name pattern

You can execute the

„Get Jobs...― function

multiple times with



job list step by step





After BW process chains/steps have been assigned for monitoring you can configure detailprocess chain/step as general settings (switch on/off data collection and/or alerting), threshwhich can be monitored per process chain/step: execution status, execution time window, s

duration, min processed records and max processed data packages


data collection

Switch on/off alerting

Expected time window

(UTC) for the process

chain/step to start and

finish within.

Out of time window

thresholds are

meassured against this

reference time frame.

Metric value is the sum

of minutes started

before and finished after

time window.

Expected start time

window (UTC) for the

process chain/step to

start.

Out of time window

thresholds are

meassured against this

reference time frame.

• Last 24 hour executions are taken into account

• For status and records/data packages processed only

finished executions are taken into account

By default you need to scroll th

columns

Thresholds in

minutes for prochain/step run

duration





Not started on Time: If a process chain must not start later than a fixed point in time. Can be used for daily / lessscheduled on fixed time basis where the start time is always the same. Not to be used in other situations. Alert: You can specify the latest point in time of a day and the max. number of minutes allowed to be late for the s

Example: Defined time is 14:00, if the process chain has not started until 14:05 you get an alert

Out of time Window: If a process chain has to run in a fixed time window. Can be used for daily or less frequenttime based schedule (event based) where the expected time window is always the same. Not to be used in other Alert: You can specify the time window in which the process chain has to run and the max. number of minutes alloExample: Time frame 04:00 – 07:00, max 10 min, if the process chain starts before 3:50 or after 7:10 you get an a

Duration: If a process chain must not run longer than a dedicated time period Alert: You can specify the number of minutes the process chain can runExample: Time period 120 minutes, if the process chain runs longer than 2 hours you get an alert

Status: If a process chain must not run into an error Alert: You can specify, if you want to get an alert if the process chain runs into an error Example: Defined value is TRUE, if the process chain has status RED you get an alert

Records processed: If a process chain must process at least a number of records. Typically used to detect if inp(0 records). Alert: You can specify the minimum number of records you expectExample: Defined value is 1, if the process chain returns 0 records you get an alert

Data packages processed: If a process chain should not exceed a f ixed number of data packages. Typically useadjustment of package size when total volume increases (too many parallel packages may cause performance de Alert: You can specify the maximum number of data packages you expectExample: Defined value is 100, if the process chain processes 101 data packages you get an alert




BI Monitoring Configuration – BW Query Monitoring (1/2

Select the SAP BW ABAP



monitor BW queries

You can reduce the

retrieved query list by

query name (wildcard *

allowed)

You can execute the

„Get Queries...― function

multiple times with



query list step by step

Step 5.3 Configure BW Query Monitor: Allows to define SAP BW Queries to be monitore

monitored query the metrics and thresholds to be checked for alerting. BW queries which y

are selected via Get Queries from Managed System matching given filter criteria.

BI M it i C fi ti BW Q M it i (2/2




BI Monitoring Configuration – BW Query Monitoring (2/2

After BW queries have been assigned for monitoring you can configure details per monitored

Define general settings (switch on/off data collection and/or alerting)

Define thresholds for duration (in seconds)

Switch on/offmetric

data

collection

Switch on/off

alerting

Thresholds in squery run durat

duration is the a

runtime of the la

minutes.

BI M it i C fi ti BW T l t M it i




BI Monitoring Configuration – BW Template Monitoring

Select the SAP BW ABAP



monitor BW templates

You can reduce the

retrieved template list by

template name (wildcard

* allowed)

If

te

fo

te

B

as

th

fr

You can execute the

„Get Templates...― function

multiple times with



template list step by step

Step 5.4 Configure BW Template Monitor: Allows to define SAP BW Templates to be mo

monitored template the metrics and thresholds to be checked for alerting. BW templates w

monitor are selected via Get Templates from Managed System matching given filter crite

BI M it i C fi ti BW T l t M it i




BI Monitoring Configuration – BW Template Monitoring

After BW templates have been assigned for monitoring you can configure details per monitore

Define general settings (switch on/off data collection and/or alerting)

Define thresholds for duration


data collectionSwitch on/off

alerting

Thresholds in

minutes for templa

run duration

BI M it i C fi ti A ti ti




BI Monitoring Configuration – Activation

Step 5.5 Activate BI Monitoring: All changes made to the different BI monitoring areas (BO

chains, BW queries, BW templates) are listed. Changes may be added / removed objects or

The Activate BI Monitoring button will make all changes effective.

Per activated monitored object

a log message is created.

BI Monitoring Configuration Complete




BI Monitoring Configuration – Complete

Step 6 Complete: Gives an overview on the success status of each step and sub-step of th

Configuration. All steps and sub-steps should have a green status.



Demo and ExerciseConfiguration of Business Intelligence Monitoring




Monitoring - Monitoring

BI Monitoring as part of Technical Monitoring Work Cent




BI Monitoring as part of Technical Monitoring Work Cent

BI Monitoring Application is integrated in the

Technical Monitoring Work Center

BI Monitoring Scenario needs to be

and BI Monitoring application can

times Embedded or in New Windo

BI Monitoring – BI Overview Monitor (graphical view)




BI Monitoring – BI Overview Monitor (graphical view)

The BI Overview Monitor shows at a glance the summary of the current status and the op

components that are included in your technical scenario.

Summary of alerts and status worst case of all systems in the BO Web Application Layer

and BW System Layer

Alert (summary)

Technical instances status (wor

BI monitored objects status (sum

System + host level status (wor

BI Monitoring – BI Overview Monitor (tabular view)




BI Monitoring – BI Overview Monitor (tabular view)

Allows comprehensive overview for large number of instances. Switch between graphical

is always possible.

BI Monitoring – System Monitor for BO WebApps System




BI Monitoring System Monitor for BO WebApps System

Drill down to

monitoring appli

hierarchy by click

of a System Moni

you are inte

The BO Web Applications System Monitor shows each single instance of a BO Web com

details like number of alerts, availability status, performance status and exception status.

Direct start of the system monitoring application for each BO Web instance is provided.






The performance category

and its subcategories are

shown

In the d

inves

perform

By changing the view category you can

directly switch between the single

categories to Performance…






Availability of BOE InfoView

web application (HTTP ping

from SMD agent)

Average Response time of

open session action

Exceptions in BI launchpad

(InfoView) application or in

Query As a Web Service

QaaWS calls

BO Enterprise System Model




B

BOE Server

Intelligence Agent

BOE Server Process

BOEService

BOEService

BOE Server Process

BOE

Service

BOE

Service

BOE node

BO Enterprise System Model

BOE Server

Intelligence Agent

BOE Server Process

BOEService

BOEService

BOE Server Process

BOE

Service

BOE

Service

BOE node

BOE Cluster C

m

B

mod

pro

no

Technical instances: Many types

of BO server processes exist.

Different types correspond to

different BO product instances.

Software component: Monitoring

templates per software component

defined on technical instance level

(corresponds to BO server types)

BI Monitoring – System Monitor for BO Server Systems




o to g Syste o to o O Se e Syste s

Metrics and alerts for BO

system wide jobs

BO servers are modelled as

technical instances.

For scrolling

server p

Navigatio

between Band BW





g y y

For BO s

represenach tech

its ow

Choose the category that you

are interested in – like Availability, Performance,

Configuration and Exceptions.

.





g y y

Example: Central Mana

Average ResponsCMS queries and

Example: File Repos Average Read and Wr

time

BI Monitoring – BO Job Monitor (1/2)




g ( )

Monitored jobs are grouped by

the BO system they belong to

For each job y

status of eame

- Not Started o

- Out of Time W

- Duration

- Status

The BO Job M

a sepa



BI Monitoring - BO Job Monitor - Out of time window cal




time

yesterday tomorrowtoday

now

J1

W1 W2 W3

J2

J3

J4

J5

0

Daily time window

Job runs

Closest window

Reported metric value

J

6

BI Monitoring - BO Job Monitor – Check configuration




How to

your tec

the S

Config

Ch

scenaConf

Choose the job that you are

interested in and check the

thresholds …

BI Monitoring - BO Job Monitor - Check job details (1/2)




Select Navigate to Central

Management Console (CMC)for detailed analysis of a job in

the BOE system.

Log o

Instan

the se

job of

BI Monitoring - BO Job Monitor - Check job details (2/2)




Right click the job you are

interested in and select

―Instance Details‖ to see moredetails of this instance.

Check th

detail inform

you are inv

case: check

to find the r



BI Monitoring – BW Process Chain Monitor (2/2)




The analysis transaction

RSPC is started by default

showing the previously chosenprocess chain...

You can use the SAP WebGUI

session also for calling other

analysis tools like ST13 (BW-

TOOLS) …

… or analysis transaction

ST03N

BI Monitoring – BW Reporting Monitor (1/2)




Monitored queries / template

are grouped by the BW

system they belong to

For e

Tem

Averag

seco

In the BI Overview Monitor

choose the BW Server

Systems box …

… and click then on the traffic

light in the section Reporting

BI Monitoring – BW Reporting Monitor (2/2)




Mark the BW Query or

Template you want to

investigate …

Start the BW AnalysisTransaction by choosing

Navigate to Analysis

Transaction

Choose section Queries: Bex

Web (ABAP) …

Check the details

want to inve



Demo and ExerciseBusiness Intelligence Monitoring Application




Monitoring - Alerting

Runtime Architecture




Managed Object

SAP Solution Manager

AlertingMonitoringReporting

BW

Store

Alert

Store

Event + Metric

Store

Metric

values

Events

Metric

values

Metric

values

Alerts

EventsEvent

Calculation

Engine

Data

Provider

Connector

Directory (Configuration)

Rated

Metrics

Data

Provider

Data

Provider

Alert

Consumer

Connector

Data Provider Connector




The Data Provider Connector receives me

the Data Providers

Provides a web service to receive error m

Data Providers

Gatekeeper: Checks if retrieved metrics a

metrics which are not known in central co

Decides where the metric values have to based on the central configuration

Metric is reporting relevant Send to BW Sto

Metric is relevant for Monitoring and Alerting

Calculation Engine

BW

Store

Metric

values

Metric

valuesDataProvider

Connector

Metricvalues

Event Calculation Engine



© 2011 SAP AG All rights reserved

Calculates the current status based on ce

configuration

Calculate rating for metrics based on the metri Calculates the event rating based on the contri

event rules

Writes the current status of metrics and e

Event + Metric Store

Provides the events to the Alert Consume

Event + Metric

Store

Events

Metric

values EventsEventCalculation

Engine

Rated

Metrics

Alert Consumer connector



© 2011 SAP AG All rights reserved

Receives new alerts from Event Calculatio

Decides if new alert has to be generated oexisting alert has to be updated (Alert Gro

Writes new or updated alerts to the Alert S

Forwards alerts to additional alert consum

central alert configuration

Create automatic notifications (e-mail or SMS) Create automatic incidents (Service Desk)

Forward to 3rd party BAdI implementations

Forward to customer BAdI implementations

Alert

Store

Alerts

Events

AlertConsumer

Connector

BI Monitoring - Alert Inbox in general (1/4)




Central access point to handle alerts for Systems,

DBMS and Hosts

Efficient alert handling based on consolidation of

single alerts to alert groups Integration of most common alert handling

mechanism as status tracking, incidents,

notifications and 3rd party integration

Drill down from alert type to alert groups and single

metrics and events

Integration of analysis capabilities as problem

context and monitoring

Alert Typ

Alert Grou

Metric Viewer Alert Deta





Allows to confirm all alert

groups belonging to one alert

type and managed object

Shows log of actions whichhappened per alert type and

managed object

Allows postponement ofcertain alert type so that it

disappears from alert inbox

Pre-defined POWL queries

per category and managed

object type

Configure and display

problems context to identify

root-cause of certain

symptom

Navigate to System

Monitoring, Landscape

Browser and System Login





Allows to confirm all selected

alert groups belonging to one

alert type and managed

object

Create context sensitively an

incident out of an alert group

Create Alert Analysis Report

which could be sent to

persons w/o access to Alert

Inbox

Assign certain user for

further follow-up of the

symptom

Show alert details for deep

dive analysis of certain

symptom





Confirm, Incident, Notification and Analysis

Report as for alert group tableNavigate to System Monitoring, Landscape

browser, System Login and Problem

Context as for alert type table

Alert details inc

status and

inform

Alert texts as d

and/or by

Alert details

assigned metr

Metric and events details

including single values,

thresholds and texts

Metric viewer to plot a certain

metric over time

BI Monitoring – Alert Inbox for BI (1/2)




Select the aler

interested in - fo

Process Chain

PackagSelect the alert group that you want

to investigate in greater …

Choose the Show Details button

BI Monitoring – Alert Inbox for BI (2/2)




Check the details of th

alert - like minimum, m

last measured value o



Demo and Exercise Alert Inbox for Business Intelligence Monitoring



Supportability for Busines

Objects

Supportability for Business ObjectsOverview




Remote Debugging

Root Cause Analysis

Remote Support Component SAP Solution Manag

Remote Access

SAP Router Line Opener Progra

Remote Access: SAP Router and Line Opener Program




SAProuter

Line OpenerProgram

(LOP)

Client + TCP ProxySAP Logon

Web Ap

Bac

Ser

SAProuter

https

SAP BusinessObjects

components

Other components

Root Cause Analysis: Options for SAP Customers




Remote Support Component

Recommended for SAP Business Objects

landscape only

Limited functionality

Upgrade path to SAP Solution Manager in Q3 2011

SAP Solution Manager

Supports mixed landscapes

(SBOP & other SAP products)

Full blow functionality

Complete integration in ALM pro

Single systems / For BO only shops Full blow functionality / For BO a

Customer

Landscape

Management

Platform

Business

Objects

Business

Intelligence

Remote Support

ComponentUpgrade ( Q3 2011)

Business

Objects

Business

Intelligence

ERP

Root Cause Analysis with Remote Support ComponentOverview




Root Cause Analysis platform

Specifically for SAP customers who do not have a significant

SAP landscape SAP BusinessObjects Enterprise XI 3.1 SP2 and future

versions are supported

No additional fee with a valid SAP maintenance contract

Allows customers to better analyse their SAP

BusinessObjects Enterprise systems

Reduces time to resolve messages

Less total cost of ownership (TCO) compared to Solution

Manager

Root Cause Analysis with Remote Support ComponentArchitecture




Development

system

Web

Application

Server

BusinessObjects

Enterprise

P

Web

Applicatio

Server

EarlyWatch Alert

report in the Service Marketplace

Monitoring

system

CA Wily

IntroscopeAnalysis

Analysis

Root Cause Analysis

by customer or

Managing

Agent

C o n n e c t i o n t o

Analysis

Operating System Data

Application Specific Data

Managed

Agent

Managed

Agent

Managed

Agent

Root Cause Analysis with SAP Solution Manager Overview




End-To-End Workload AnalysisGeneral performance overview for heterogeneous solution landscape

Review of most important KPI’s cross all technologies and drill down to product specific KPI’s

End-To-End Change AnalysisStatistical change data cross all technologies based on daily configuration snapshots

Compare configurations between systems and drill down to change reporting for change history

End-To-End Exception AnalysisStatistical exception data cross all technologies for exception trend analysis or review exception

Jump to component specific exception analysis (ST22, NWA,…)

End-To-End Trace Analysis

Single user request tracing in a complex system landscapes Identify the problem causing component (performance and functional) and jump-in to detailed component

specific trace analysis (SQL, ABAP, J2EE trace,…)

System, Host & Database AnalysisCentral, safe and remote access to file system, OS and DB

Links to read-only monitoring and administration tools like Wily Introscope for performance analysis and monitoring

Root Cause Analysis with SAP Solution ManagerEnd-to-End Change Analysis




BO Web Layer

Web Applic

specific con

(e.g. ApachIBM Web S

SAP J2EE

BO Server Lay

Platform SD

Platform Se

Configuratio

WEBI Proce

Configuratio

SAP BW Layer

Parameters

Transports

SAP Notes

Root Cause Analysis with SAP Solution ManagerE2E Workload Analysis




BO Web Layer

Average Re

Number of

Calls to BI P CPU & Mem

BO Server Lay

Average Re

Number of

Calls to Dat

CPU & Mem

SAP BW Layer

Reporting P

Process Ch

Upload Perf

Root-cause Analysis for Business IntelligenceEnd-to-End Exception Analysis




BO Web Layer

Java Applic

Web Applic

Event Log Eonly)

BO Server Lay

Services er

written by s

Event Log E

only)

SAP BW Layer ABAP Syslo

ABAP Dum

ABAP Upda

Root-cause Analysis for Business IntelligenceEnd-to-End Trace Analysis




BO Web Lay

HTTP Req

Server Ana

Introscope

Log Viewe

BO Server La

Server Ana

Introscope

Log Viewe

SAP BW Lay

ABAP Trac

ABAP SQ

BI Runtime



Remote Services: EarlyWatch Alert report

Sample EWA report (click

http://service.sap.com/~sapidb/011000358700001309482010E





Sample EWA report (click

Remote Debugging: Architecture overview






TCP ProxyJava Debugger

Native Debugger

Java Source Code

C++ Source Code

D e b u g g e r

I n t

e r f a c e

Web Ap

Bac

Ser

SAP Logon

SAP BusinessObjectscomponents

Other components

Debugger

Interface

SAProuter SAProuter

https



Summary

Summary




SAP Business Intelligence Monitoring

Provides visibility in SAP Business Warehouse aswell as BusinessObjects Environment XI

Is completely integrated in SAP End-to-End

Monitoring and Alerting Infrastructure

Is available with SAP Solution Manager 7.1 Support

Package 1

Supports BusinessObjects Environment XI 3.1 as

well as 4.0 Is completely integrated with Root Cause Analysis

capabilities provided by SAP Solution Manager

Further Information




SAP Public Web:

SAP Developer Network (SDN): http://wiki.sdn.sap.com/wiki/display/TechOps/H

Related SAP Education and Certification Opportunities

http://www.sap.com/education/

Related Workshops/Lectures at SAP TechEd 2011

ALM217 Run SAP Like a Factory - Technical Operations, Lecture

ALM271 From End-User Experience Monitoring to Management Dashboards and R ALM272 Customizing and enhancement of System Monitoring and Reporting, Hand





FeedbackPlease complete your session evaluation.

Be courteous — deposit your trash,

and do not take the handouts for the following session.



Thank You!

Contact information:

Janko Budzisch Mathias Bley

Chief Service Architect Service Architect

[email protected] [email protected]


mailto:[email protected]







No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP AG. The information contained herein may be

changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary

software components of other software vendors.

Microsoft, Windows, Excel, Outlook, and PowerPoint are registered t rademarks of Microsoft

Corporation.

IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,

System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,

z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server,

PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER,

OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP,

RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,

Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered

trademarks of IBM Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks orregistered trademarks of Adobe Systems Incorporated in the United States and/or other

countries.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are

trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registe

Wide Web Consortium, Massachusetts Institute of Techno

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign

StreamWork, and other SAP products and services ment

respective logos are trademarks or registered trademarks

countries.

Business Objects and the Business Objects logo, Busines

Crystal Decisions, Web Intelligence, Xcelsius, and other B

services mentioned herein as well as their respective logo

trademarks of Business Objects Software Ltd. Business O

SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQ

products and services mentioned herein as well as their r

registered trademarks of Sybase, Inc. Sybase is an SAP c

All other product and service names mentioned are the tr

companies. Data contained in this document serves infor

product specifications may vary.

The information in this document is proprietary to SAP. N

reproduced, copied, or transmitted in any form or for any

written permission of SAP AG.

efficient monitoring for sap netweaverbw-alm270

Documents