011000358700001212912012 e usingsolman-hana-moni

HANA Supportability and Monitoring

Active Global Support

2012

© 2012 SAP AG. All rights reserved. 2

Remote Access

Monitoring

Root Cause Analysis

Remote Services

Summary

1

2

3

4

5


Remote Support Tools to HANA Database

HANA Host

Inte

rnet

SAP Customer

SolMan Host

SolMan 7.1 HANA Database

DBA Cockpit

HANA DB Studio

SAP GUI / Browser

Http Connect

R/3 Support

SAP Router

SSH / telnet / Netviewer

OS Console


Remote Access to Solution Manager

• HANA can be connected to Solution Manager 7.1 >= SP02

• Standard SAPGUI and HTTP connection to Solution Manager has to

be established (see SAP Note 962516)


Remote Connection via saprouter to HANA DB Studio

What is needed to connect from

SAP Network to customer network:

Connection via sapstartsrv

on the HANA Server

to the Master Index Server

SAP HANA

Server

SAP Router

SAP

Network

Customer

Network



• Saprouter installation required at customer side

see also http://service.sap.com/serviceconnection

• Connection to customer HANA DB possible from SAP local HANA DB Studio

• New connection type „SAP HANA database“ in customer system data and STFK

• See note 1592925 (SAP HANA database service connections)

Port of sapstartsrv for HANA

(by default: 5<instno>13)

Port of HANA master indexserver

(by default: 3<instno>15)

http://service.sap.com/serviceconnection



• Specify a certain user which has no administrative roles:

•MONITORING

•Possible to look at historical data

(Schema _SYS_STATISTICS)

•PUBLIC

•Possible to look at Monitoring Views

(Schema SYS)


Remote Access to OS level

• In very hard support cases it might be necessary to have OS level access

For the HANA linux systems a SSH or Telnet remote connection should be

set up (SAP Notes 1275351 + 1327257)

• For Windows based systems (potentially used for Business Objects components)

we therefore recommend to setup a Netviewer connection (SAP Note 1036616)

Netviewer requires the customer to active accept a connection request.

For unattended access a Windows Terminal Server connection can be setup

(SAP Note 605795)


Remote Access to Further Components in HANA

Scenarios

• Business Objects Enterprise / BI Platform 4.0 can be connected to

Solution Manager 7.1 (SAP Note 962516)

R/3 support (SAP Note 812732)

HTTP Connect (SAP Note 592085)

• Business Objects Central Management Console (CMC)

HTTP Connect – URL access

• SAP Backend system and SLT system can be connected to

Solution Manager 7.1

R/3 support

HTTP Connect


Remote Access

Monitoring

Root Cause Analysis

Remote Services

Summary

1

2

3

4

5


The process behind technical operations…

Monitor

Proactive real-time

monitoring

Optimize

Optimize excellence of

technical operations

Analyze

Lower mean time to

problem resolution

Notify

Reactive handling of

critical events

Report

Prove value to business


Technical Monitoring and Alerting Capabilities in Detail

Unified Alert Inbox • Central access point for all alerts coming from the different monitoring scenarios

• Integration of Incident & Notification Management, Root Cause Analysis and collaboration features

System Monitoring • Status overview for technical systems, instances, databases and hosts

• Drill down to single metrics and events, Jump in to metric reporting and landscape information

End User Experience Monitoring • Measurement of availability and response times from an end user perspective

• Deep integration in E2E Trace Analysis for Root Cause Analysis

Process Integration Monitoring • Central entry point for SAP Process Integration specific monitoring for complete PI domains

• Contains central monitors for PI components, PI channels and Message flows

Business Intelligence Monitoring • Central monitoring for SAP Business Intelligence solutions based on SAP BW and BOE XI

• Monitoring of SAP Business Warehouse process chains and Business Objects specific jobs

Connection Monitoring • Active Monitoring of RFC and HTTP connections between SAP Systems

Inte

gra

tio

n o

f a

ll s

ce

na

rio

s in

En

d-t

o-E

nd

Mo

nit

ori

ng

an

d A

lert

ing

Infr

as

tru

ctu

re


System Monitoring

Solution Manager 7.10 SP 02/

SP 03

Availability Monitoring

– Alerts are generated by Hostagent

o Mainly Database Availability

o Host Usage (CPU / Memory

Usage)

HANA Host SolMan Host


DBA Cockpit

Host Agent


System Monitoring

Solution Manager 7.10 SP 04





Usage)

Alerts from the HANA Database

(pre-rated) obtained via

DBAcockpit Framework

HANA Host SolMan Host


DBA Cockpit

Host Agent


System Monitoring

Solution Manager 7.10 SP 05





Usage)

Alerts from the HANA Database

obtained via DBAcockpit

Framework with Metrics (for

HANA SPS 4)

Queues in SLT can be

monitored

HANA Host

SolMan Host

SolMan 7.1

HANA Database DBA Cockpit

Host Agent

SLT System


Monitoring Overview

Solution Manager

Release

HANA

Studio

DBACockpit Monitoring

7.10 SP 2 & 3 yes no yes (System Monitoring->

Availability)

7.10 SP 4 yes yes yes (System Monitoring ->

Availability + Alert Results)

7.10 SP 5 yes yes yes (System Monitoring ->

Availability + Alert Results + Alert

Metrics)


HANA as a Database of an ABAP System

Fully embedded in System Monitoring

HANA appears as any other database

of an ABAP system.


HANA as a Database of an ABAP System – Monitoring

Details

• Important configuration settings are monitored

under Configuration category

• HANA and its services availablilty monitored

under availability category

• Error or exceptional situations monitored under

Exceptions category

• Performance critical situations monitored under

Performance category


HANA as a Database of an ABAP System

Fully embedded in System Monitoring

HANA appears as any other database

of an ABAP system.


HANA as a standalone Database

This HANA standalone systems runs on two

nodes.


Technical Monitoring and Alerting Capabilities in Detail

Unified Alert Inbox • Central access point for all alerts coming from the different monitoring scenarios

• Integration of Incident & Notification Management, Root Cause Analysis and collaboration features

System Monitoring • Status overview for technical systems, instances, databases and hosts

• Drill down to single metrics and events, Jump in to metric reporting and landscape information

End User Experience Monitoring • Measurement of availability and response times from an end user perspective

• Deep integration in E2E Trace Analysis for Root Cause Analysis

Process Integration Monitoring • Central entry point for SAP Process Integration specific monitoring for complete PI domains

• Contains central monitors for PI components, PI channels and Message flows

Business Intelligence Monitoring • Central monitoring for SAP Business Intelligence solutions based on SAP BW and BOE XI

• Monitoring of SAP Business Warehouse process chains and Business Objects specific jobs

Connection Monitoring • Active Monitoring of RFC and HTTP connections between SAP Systems

Inte

gra

tio

n o

f a

ll s

ce

na

rio

s in

En

d-t

o-E

nd

Mo

nit

ori

ng

an

d A

lert

ing

Infr

as

tru

ctu

re


Introduction - Monitoring for Business Intelligence

SAP Solution Manager

BI Overview Monitor

System Monitor

Central system status overview for all

technical components involved in SAP

Business Intelligence Solution

Capability to monitor cross-system

SAP BW process chains and single process

chain steps

Integration of Business Intelligence specific

alerts in Alert Inbox including Notification

Management, Incident Management, Task

Assignment and forwarding to 3rd party

Central monitoring of Business Objects

specific jobs and correlation to system

specific metrics

Central monitoring of SAP BW queries and

templates

BI Detail Monitors


Monitored “classic” BI scenario and objects

Backend Systems

/ Data Sources

e.g. SAP ERP

SAP BI Platform Systems

(BusinessObjects Enterprise)

BO Jobs

Reports

SAP Business

Warehouse

Systems

(SAP BW)

Process Chains

Queries /

Templates

Info

objects

BO Web Application

Server Systems

BOE Web

Application

BI monitoring scenario

Monitored systems in BI scenario – grouped by BI component type (BW systems, BO server systems, BO web app server systems).

Monitored BI objects (process chains, queries and templates in SAP BW system; jobs in BO system)

End user

This picture shows a typical BI scenario (between backend systems and end user). Two monitoring levels are provided:

• System level monitoring for the involved technical systems

• Monitoring of important BI objects (process chains, queries, templates, BO jobs)

SAP Business

Warehouse

Accelerators

(SAP BWA)

Info

provider


BI Monitoring – BI Overview Monitor (graphical view)

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

alerts of all BI components that are included in your technical scenario.

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

Server Layer and BW System Layer

Alert (summary)

Technical instances status (worst case)

BI monitored objects status (summary)

System + host level status (worst case)


Monitored “modern” BI scenario and objects

SAP BI Platform Systems

(BusinessObjects Enterprise)

BO Jobs

Reports

SAP Business

Warehouse Systems

(SAP BW)

Queries /

Templates

Process

Chains

BO Web Application

Server Systems

BOE Web

Application

BI monitoring scenario

Monitored systems in BI scenario – grouped by BI component type.

Monitored BI objects (process chains, queries and templates in SAP BW system; jobs in BO system)

End user

SBOP Data

Services Systems

SBOP DS

SAP ERP Systems

running SLT

Real Time

push - SLT

Backend Systems

/ Data Sources

e.g. SAP ERP

SAP HANA

Databases

(SAP HANA)

Info

provider


BI Overview Monitor - Preview

New Technical System Types in SP5

Hana Systems SLT Systems Data Services

Systems

Replication Jobs

New Technical System Types are introduced: „Hana Systems“,

„SLT Systems“, „Data Services Systems“, „Source Systems“;

they are all covered by the System Monitoring in the first step.


Local Monitoring for SLT (in SLT System)

Configuration / monitoring application

WebDynpro application: http://<host>:<port>/sap/bc/webdynpro/sap/iuuc_repl_mon_powl:

Configuration & Monitoring Dashboard – Transaction LTR

Replication scenarios can be grouped in different configurations with

source (ABAP) and destination (HANA) systems as well as tables

to be replicated

Top level shows worst aggregated worst case status per schema

Important: Remote connection should be R/3 and an http connection !!!


Local Monitoring for SLT (in SLT System)

Example of the Configuration & Monitoring Dashboard

Top level agrregation rating og the configuration: Worst case Status of the configuration.


Local Monitoring for SLT (in SLT System) – per schema

Jobs and Connections

Connectivity status check for source and target connection

Job status monitoring:

Master job regularly checks replication need and starts load jobs if replication is required



Triggers

Checks consistency of trigger definitions



Replication statistics

Checks status and latency (time between request to replicate (source system) and

executed replication)


SLT System Monitoring (Solution Manager 7.10 SP 05)

SLT System monitoring defined on ABAP technical system level

SAP template: SAP SLT ABAP Addon

Is by default assigned if the DMIS ABAP Addon is detected



Availability Monitoring for SLT

Per schema (configuration) the connectivity status from SLT to the source and to the target

system is monitored



Performance Monitoring for SLT

Per schema the worst rating of average latency of the past 24 hours is reported



Exception Monitoring for SLT

Per schema the job status for master and load jobs is monitored



Exception Monitoring for SLT

Per schema the trigger status is monitored (worst case for all table triggers)


Remote Access

Monitoring

Root Cause Analysis

Remote Services

Summary

1

2

3

4

5


The process behind technical operations…

Monitor

Proactive real-time

monitoring

Optimize

Optimize excellence of

technical operations

Analyze

Lower mean time to

problem resolution

Notify

Reactive handling of

critical events

Report

Prove value to business


Monitoring for HANA: Possibilities

Solution

Manager Relase

HANA Studio DBACockpit DB

Performance

Warehouse

7.10 SP 2 & 3 yes no no

7.10 SP 4 and

higher

yes yes yes (with

additional SAP

Note)


HANA DB Studio

DBA Cockpit

SAP Solution Manager 7.1

3.1

3.2

3.3


HANA DB Studio (Overview – Administration View)

• Client tool delivered with HANA installation

• Provides local monitoring and root cause analysis

• Read only role for support / remote access


HANA DB Studio (Overview)

General infos

(version,

uptime,...)

Most important

KPIs

Alerting


HANA DB Studio (Landscape Details)

Name Server

Index Server

Statistic Server

Global operations (like Backup)

Data Container, etc.

Historical Data, Alerting Engine

sapstartsrv Important for general connectivity

to the HANA Database


HANA DB Studio (Landscape Details)

• Status of all HANA services and distribution over Hosts

• Resources consumption per service

• Starting / stopping with admin permission


HANA DB Studio (Alert Details)

• Current and historic reported alerts


HANA DB Studio (Current Activity)

• Current activity on thread level (SM50 like)

• Complete statement + additional detail per thread on request


HANA DB Studio (Current Activity)

To evaluate te problematic Thread Type


HANA DB Studio (Performance Statistics)

Load statistics

per selectable

time frame

Data can be

ex/imported

to/from csv


HANA DB Studio (Configuration)

• Configuration settings

• Change permission for administrator role


HANA DB Studio (Further Detail Views)

• Many additional analysis views for detailed analysis

• Example: expensive statements


HANA DB Studio (Logs and Traces)

Access to

log and

trace files


HANA DB Studio (Trace Settings)

Further Tracing possibilities:


Investigations with HANA DB Studio:

Memory Consumption (very simple view) I

Heap Memory contains

Column Based Tables

Results of Operations (Calc views …)

…

-> Result ‚HEAP_USED_MEMORY‘

Shared Memory conntains

•Row Store Tables

Memory consumption of index server (very simple)



Memory Consumption (very simple view) II

Memory Usage by

Host

Allocated Heap by

Index Server

Used Heap by

Index Server

Memory Usage by

Index Server



Memory Consumption (very simple view) III

•Most of the Used Heap is occupied by Column Based Tables

•Difference of Allocated Heap und Used Heap: Reserved Heap for fast „In Memory Calculations“

•100 Gbyte of Memory: Usage is coming from somewhere else

•Shared Memory does not play any role



Memory Consumption (very simple view) IV

System Table: Index Server memory usage

(as of HANA DB Studio 1.00.21)



Column Based Tables (very simple view) I

Upload Mechanism:

Uploads in Column Based tables are first written in ‚Delta Store‘

– Data in Delta Store are not compressed

– Hugh amount of Data in Delta Store slow down the performance

Data are written in the ‚Main‘ Store according to the ‚Merge‘ Mechanism

---------

---------

---------

---------

Delta Store Main Store Delta Store Main Store

Merge



Column Based Tables (very simple view) II



Column Based Tables (very simple view) III

Number of records

Number of are limited to 2 Billion

Merge mechanism should be activated

Check regarding Number of records in a table


HANA DB Studio

DBA Cockpit


3.1

3.2

3.3


DBAcockpit for HANA DB

DBAcockpit is an ABAP based DB monitoring tool

Exists with SAP GUI or browser UI (WebDynpro) SAPGUI: transaction code DBACOCKPIT

Browser: URL http(s)://<full hostname>:<port>/sap/bc/webdynpro/sap/dba_cockpit

some detailed screens only available via SAP GUI

It is available for HANA in Solution Manager ST 710 SP 04

(containing a special DBACockpit version for SAP HANA, based

on SAP_BASIS 7.02 SP 09)

Allows remote monitoring of HANA DB via Solution Manager

Is also used to collect long term statistic data for HANA in Solution Manager


DBAcockpit for HANA DB

Current Status of HANA (important KPIs)

Historical Data (Statistic Server)

Configuration

Trace Possibilities

Deeper Investigation (e.g. Query Cache,

Largest Tables)


DBAcockpit for HANA DB Overview Screen

• Overview with key metrics and version data


DBAcockpit for HANA Health Checks (Alerts)

• Results of last health checks

Critical Alerts appear a the top.


DBAcockpit for HANA (Current Activity)

• Thread monitor (SM50 like)


DBAcockpit for HANA (Current Activity / Disk usage)

• Session monitor (SM04 like)

• Disk usage


DBAcockpit for HANA (Backup Planning Calendar)

DBA Planning Calendar can be used to

Schedule HANA DB Backups

Check results

Green =

successful


DBAcockpit for HANA (Backup Planning Calendar)

DBA Planning Calendar detail views:

Planned and actual start and end times

Status and location of backup on file system

Job log of ABAP based background job triggering the backup

Program log will show

HANA Backup detail message

in the future


HANA DB Studio (Backup Result Details)

Table SYS.M_BACKUP_CATALOG holds detail information for

database backups as well as log backups


HANA DB Studio

DBA Cockpit


3.1

3.2

3.3


E2E Root Cause Analysis with Solution Manager 7.1

End-To-End Workload Analysis • General performance overview for heterogeneous landscape

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

specific workload KPI’s

End-To-End Change Analysis • Statistical change data cross all technologies based on daily configuration

snapshots

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

End-To-End Exception Analysis • Statistical exception data cross all technologies for exception trend analysis

or review exception after changes

• 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 Analysis • Central, 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


Remote Support with

Solution Manager 7.1 for HANA

HANA Host

Dia

gn

ostics A

ge

nt

SA

P H

ostc

on

trol

CPU

Memory

File

system

Introscope

Enterprise

Manager

IS Server

Browser

access

Inte

rnet

SAP Customer

DB

SolMan Host

SolMan 7.1

Remote DB Monitoring

logs

1 Workload Analysis = Performance Warehouse as of SolMan 7.1 SP04 2 Trace Analysis planned with SolMan 7.1 SP05

TCP/IP:

6001

SQL Port:

3<HANA-InstNo>15

http:

1128

TCP/IP:

6001

P4 Port: 5<InstNo>04

Msgsvr http: 81<InstNo>

http to Webdisp.: 80

http to ICM: 80<InstNo>

E2E Change Analysis

E2E Exception Analysis

E2E Workload Analysis1

Introscope WebView

File System Browser

Log Viewer

E2E Trace Analysis2

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

Change Analysis


Database Changes - Overview

Shows number of HANA DB

parameter changes over time


Database Changes

Shows single

HANA DB parameter

change history

Exception Analysis


HANA indexserver errors - Overview

Shows statistics on errors

reported by HANA

indexserver(s) over time


HANA indexserver errors - Details

Shows statistics per error

type reported by HANA

indexserver(s) over time

with jump in capability.

Workload Analysis (Database Analysis)


Database Analysis for HANA DB in Solution Manager

E2E WorkloadAnalysis for HANA Database Analysis (Performance Warehouse)


Host Memory – Overall HANA Memory Utilization

Shows overall main memory:

• Used by HANA

• Totally used (including non HANA

processes)

• Physical memory limit


HANA Services Memory – Per HANA Service Memory

Utilization

Shows memory utilization

per HANA service


Resource Consumption – CPU Utilization on HANA

system

Shows CPU utilization

on HANA system by

• CPU user time

• CPU system time

• IO wait time


HANA Volume Files – Used Size on Disks

Shows sum of data volume size

• Allocated size

• Used size

Same available for Logs.

Details per single file.


HANA Volume Pages – Statistics on Page Size Utilization

Shows disk utilization

per page block size.


Top Column Table Partitions

Shows top column based

table partitions base on

main memory utilization.

Including main/delta store

size.

Same available by number

of rows.


Top Tables

Shows top tables in memory

by size.

More tables and details available in

tabular format.


Persistence Table Size

Shows top tables by size in disk.


Performance IO statistics

Shows IO frequency and IO

performance per data/log file

and block size.


Remote Access

Monitoring

Root Cause Analysis

Remote Services

Summary

1

2

3

4

5


Going Live Check

SAP EarlyWatch Alert (EWA)

4.1

4.2


GoingLive Check: Landscape – Configuration

The configuration shows the Support Package level (the necessary one)


GoingLive Check: Landscape – Configuration

In addition also the Kernel is taken into account, if a direct connection exists

between HANA Database and the Business Application


GoingLive Check: Load

Asking for the Load produced by Transcations / Background Jobs (and

compare those in the GV Session)


GoingLive Check: Load

Some table properties are collected (and compared later also in the GV

Session)


GoingLive Check: Sizing

Hardware Capacity:

Future Sizing

According to the Sum of Memory

Consumption of Tables to be replicated:

Source SUM of tables (Mbyte) / 2,5

= Memory consumption in the HANA

Database

Concurrent Users: 0,2 CPUs *

concurrent users <= available number

of CPUs


HANA Database Chapter

Settings for HANA Database

Configuration

Traces ON/OFF

SAP Notes for HANA


Going Live Check

SAP EarlyWatch Alert (EWA)

4.1

4.2


System Monitoring (EarlyWatch Alert)

For the currently supported scenarios monitoring for SAP Hana Database can

be included into SAP EarlyWatch Alert (EWA) service for SAP Business Suite

Application (SAP ERP, SAP CRM …), SAP BW on HANA system or SLT

system.

Prerequisites:

SAP Host Agent on SAP HANA Appliance (included by default) needs to be configured and

extended as per SAP Note 1542651

Data collection to the SAP ABAP system (BW on HANA, ERP, SLT, …) is realized via Web

Service call which needs to be set up as outlined in SAP Note 1543278

'SAP Solution Manager Service Tools' (ST-SER) with version 701_2010_1 SP08 or higher

are installed in SAP Solution Manager which is processing the EWA (SAP Note 569116)

Automated Service Content Update activated as per SAP Note 1143775


System Monitoring EWA for HANA Setup Landscape

SolMan 7.0 SAP

„Backend“

System

1. Batchjob triggers data

collection on HANA via Host

Agent

2. Host Agent starts data

collection Skript

3. Information is passed back to

background job (XML-

Format)

4. Results in background job is

collected in sdcc and send to

SolMan

5. EWA session is

executed on SolMan and

EWA report is created

InMemory

Database

Hana 1.0

Host Agent

Skript


EWA for HANA (SPS02): Overview

HANA Checks included in the

EWA report of an ABAP Stack

Overview (beginning of EWA):

• Rating of area which needs further

investigation:

• Overview: All Services are available

• Configuration: Parameters set correctly

• Size and Growth: Host Resource

Utilization (Disk Space, Memory Usage)

• Performance: Workload Statistics from

the In Memory Database and IO

Statistics

• Alerts and Statistics: Summary of

important Alerts and Aggregated

Statistics of the Statisticserver


EWA Content for HANA: Configuration

Configuration:

Overview

• Version

• Landcsape

• Services

Configuration

Parameter:

– lock_waittimeout

– Section mergedog: active

– Log_mode


EarlyWatch Alert: Resource Consumption

Size and Growth

Disk Usage

Separated in Data / Log File /

Trace Files

Size of Volume Files

Size of Volume files

separated by different

services


EarlyWatch Alert: Table Properties

Column Table Size sorted

Regarding Memory Size

Record Counts


EWA content for HANA: Performance

Performance

Memory Utilization

– Utlilization by each service

Available Swap Space

Workload

I/O Performance

Average Volume Statistics (Read / Write

Times

(it is normal that these values are up to

10 times bigger than what you may be

used to on other DBs)


EWA content for HANA: Admininstration 1/3

Administration

Number of Log / Trace Files

(weekly)

– Should be ensured that these are

reorganized regularly

– # of dumps should be observed


EWA content for HANA: Administration 2/3

The settings of the

HANA Database Trace

is checked.


EWA content for HANA: Administration 3/3


EarlyWatch Alert: Alert Monitoring

System Alert status is monitored and reported.


EWA availability in Solution Manager

Requirements / Summary:

•Solution Manager 7.01 / ST_SER 2010 SP 6 o Content Update should be scheduled

• HANA Box: installation of the script enabling the Host Agent for HANA Specific

Webservice Calls.

SAP Note 1542651

• SAP Backend: SAP_BASIS 7.00. The Support Package >= 18.

SAP Note 1543278


Remote Access

Monitoring

Root Cause Analysis

Remote Services

Summary

1

2

3

4

5


SAP Solution Manager Roadmap

How to orchestrate your SAP Solution powered by HANA

System Monitoring for HANA Appliance

File System and Log Browser

SM7.1 SP03 HANA SPS03

DBA Cockpit for HANA

E2E Change Analysis

E2E Workload Analysis


E2E Trace Analysis


Integration with Business Intelligence

Monitoring

CTS+ for HANA studio content

Auto-discovery of HANA systems


1

2

3


Availability Matrix of E2E RCA functions for

HANA and BW on HANA

Functions

Prerequisites HANA

SPS3 (Nov „11)

HANA

SPS4 (April „12)

HDB Studio standard remote standard remote

DBA Cockpit / Remote DB

Monitoring


SP04 (Dec’11)

E2E Trace


SP 05 (May ‘12)

(1) available already with

SP04 (Dec’11)

E2E Exceptions

E2E Change Analysis (1) (1)

E2E Workload Analysis (1) (1)

File System and Log Browser (1) (1)

EarlyWatch Alert

ST-SER 2010.1

(SAP Solution Manager 7.0

SP23)

E2E Enterprise Data Warehouse

Monitoring (BI/BW)


SP03. BOE, BW

SP05: HDB, SLT, BO DS


Support for new Business Objects releases with Solution Manager 7.1

End to End Root Cause

Analysis Functionality

Availability

Timeframe

Prerequisites BOE XI 4.0 BOEx 4.0 Data Services

4.0


Product RTC

SAProuter

SAP Solution

Manager 7.1 BOE, BOEx: SP01

DS: SP03

E2E Workload Analysis

E2E Trace Analysis

N/A

E2E Change Analysis

Introscope WebView

File System and Log Browser

Remote DB Monitoring

EarlyWatch Alert Product RTC

/ ST-SER 2010.2

ST-SER 2010.2

(Q4 2010)


Monitoring for components of a HANA scenario with Solution

Manager 7.1

Components System

monitoring

BI Overview

Monitor

BI

Detail Monitor

BI Platform 4.0 SP3 SP3

BO Jobs (SP3)

Web AS for BO SP3 SP3

BW Backend SP3 SP3 BW Process Chains (SP3)

BW Reporting (SP3)

BW Accelerator SP6 SP6

Data Services SP4 SP5 Data Services Jobs / Data Flows (SP7

planned)

SLT SP5 SP5

HANA Database Availability (SP3)

HANA Alerts (SP4) SP5


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 trademarks 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 or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

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 registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries.

© 2012 SAP AG. All rights reserved

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company.

Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase, Inc. Sybase is an SAP company.

All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.

The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose without the express prior written permission of SAP AG.

This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.

SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics, links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.

SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. This limitation shall not apply in cases of intent or gross negligence.

The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages.

Date post:	27-Jan-2015
Category:	Data & Analytics
Upload:	vbaisetty
View:	110 times
Download:	2 times

011000358700001212912012 e usingsolman-hana-moni

Data & Analytics