0% found this document useful (0 votes)
53 views85 pages

CCMSMonitoring Detailed Overview

A typical solution landscape such as mySAP CRM at a customer site: Many hardware and software components Many interfaces Business processes that span multiple components is complex. What does an administrator have to check? are all components available? are transactions performed with sufficient performance? are all interfaces working properly?

Uploaded by

tummalasp
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
53 views85 pages

CCMSMonitoring Detailed Overview

A typical solution landscape such as mySAP CRM at a customer site: Many hardware and software components Many interfaces Business processes that span multiple components is complex. What does an administrator have to check? are all components available? are transactions performed with sufficient performance? are all interfaces working properly?

Uploaded by

tummalasp
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 85

Monitoring Detailed Overview

Updated September 28, 2005

Product Management SAP NetWeaver Infrastructure Management SAP AG

Agenda

The Challenge of Monitoring a Landscape Overview of CCMS Monitoring Architecture Alert Handling Monitoring Components New Features at a Glance Summary

SAP AG 2005, Monitoring Detailed Overview / 2

Agenda

The Challenge of Monitoring a Landscape Overview of CCMS Monitoring Architecture Alert Handling Monitoring Components New Features at a Glance Summary

SAP AG 2005, Monitoring Detailed Overview / 3

The Challenge of Monitoring Landscapes


A typical solution landscape such as mySAP CRM at a customer site:
Many hardware and software components Many interfaces Business processes that span multiple components Is Complex.

What does an administrator have to check?


Are all components available? Are transactions performed with sufficient performance? Are all interfaces working properly? If a problem occurs: What is the cause of it? How can it be resolved? Are yesterdays backups complete and usable?

SAP AG 2005, Monitoring Detailed Overview / 4

Example: CRM / EBP Landscape

Internet
Vendor

Enterprise Buyer
SAP J2EE Engine Supplier Self-Services ITS Catalog Server XI

Vendor's Web Server

SAP Backend System Middleware


IPC

Internet
Customer

CRM Internet Sales Internet


Employee

Business Intelligence
IPC

SAP J2EE Engine TREX

IMS

Middleware Advanced Planner and Organizer

Intranet
Employee

SAP AG 2005, Monitoring Detailed Overview / 5

The Challenge
An administrators nightmare:
Performance of crucial transactions is very low. Main components become unavailable. Business processes are delayed.

Action required:
Locate the problem. Find out its cause. Tackle the problem. Prevent this from happening again.

SAP AG 2005, Monitoring Detailed Overview / 6

The Solution: SAPs Monitoring Infrastructure


SAPs Monitoring Infrastructure has the following benefits: Central monitoring in one single screen Large landscapes can be centrally monitored at a low total cost of operation. Full scalability Landscapes with only a few components or a large number of components can be efficiently monitored. Preventive monitoring with alerts No admin activity is required except in case of alerts. Alert notifications (e-mail, SMS ) can be triggered automatically. Assisted problem detection and resolution From the central system, administrators can drill down to a monitored component to remove the cause of an alert using predefined analysis functions.
SAP AG 2005, Monitoring Detailed Overview / 7

Agenda

The Challenge of Monitoring a Landscape Overview of SAP Monitoring Architecture Alert Handling Monitoring Components New Features at a Glance Summary

SAP AG 2005, Monitoring Detailed Overview / 8

Monitoring Infrastructure and Workload Statistics


Two Different Aspects
CCMS Monitoring Infrastructure
Overview data: in each component
landscape-wide (in ABAP stack)

ABAP Kernel

JAVA Engine

Workload Statistics
Aggregated data:
in each component landscape-wide (in ABAP stack)

STAT

DSR

Detailed data:
in each component landscape-wide (in ABAP stack)

SAP AG 2005, Monitoring Detailed Overview / 9

Monitoring Overview
Non-SAP component Agent
Shared Memory Segment

SAP Web AS Java SAP Web AS Java Agent


Shared Memory Segment

Push
Central Monitoring Infrastructure ABAP Stack SAP NetWeaver Administrator Java Stack

Solution Manager

3rd Party Tools Business Intelligence

SAP Basis 3.0 SAP instance


Shared Memory Segment

Push
Agent

SAP Web AS ABAP Agent SAP instance


Shared Memory Segment

SAP AG 2005, Monitoring Detailed Overview / 10

Central Views of Local Monitoring Data


Central Central Monitoring Monitoring

Local Monitoring

RZ20 RZ20

RFC

RZ20

Shared Memory

C11 CEN
CCMS Monitoring Infrastructure

RFC
CCMS Monitoring Infrastructure

SAP Web AS ABAP


SAP AG 2005, Monitoring Detailed Overview / 11

SAP Web AS ABAP

Monitoring Infrastructure
What is CCMS ? The Computing Center Management System is
SAPs open, integrated infrastructure for centrally monitoring SAP landscapes Provides alert monitor templates Part of any SAP Web AS ABAP and SAP Basis component Free of charge

SAP AG 2005, Monitoring Detailed Overview / 12

What can be monitored?


Predefined templates provide different monitoring views of SAP solutions and components:
Based on SAP Web Application Server (ABAP and Java, also Basis Releases as of 3.0)
Enterprise Buyer Professional / Customer Relationship Mgmt. Supply Chain Management (APO / LiveCache) Supplier Relationship Management (SCM) Business Intelligence (BI) Exchange Infrastructure Mobile Infrastructure Enterprise Portal Interfaces: tRFC / qRFC / ALE

Other SAP components


Internet Transaction Server Index Management Server Business Connector SAProuter

Non-SAP components
EMC2 Symmetrix

SAP AG 2005, Monitoring Detailed Overview / 13

Agenda

The Challenge: Monitoring a Landscape Overview of CCMS Monitoring Architecture Alert Handling Monitoring Components New Features at a Glance Summary

SAP AG 2005, Monitoring Detailed Overview / 14

SAP NetWeaver Monitoring


Central Monitoring Infrastructure Global Workload Statistics

ABAP

Java

ABAP

J2EE

NetWeaver Administrator on the Java Stack

SAP AG 2005, Monitoring Detailed Overview / 15

Architektur der CCMS-Monitoring-Infrastuktur


3rd Party 3rd Party Products Products
CCMS Alert Monitors Solution Manager NetWeaver Administrator

Local Analysis

Administration

Central Auto Reaction

A P II AP

DB

Central Data Display

Data Storage

Monitoring Object

Monitoring Object

Monitoring Object

Local Shared Memory Segments Local Shared Memory Segments


Monitoring Object Monitoring Object

Data Collection

Data Data Supplier Supplier

Data Data Supplier Supplier

Data Data Supplier Supplier

Data Data Supplier Supplier

Data Data Supplier Supplier

DB
SAP AG 2005, Monitoring Detailed Overview / 16

OS

ABAP

Java

Non-SAP

Agenda

The Challenge: Monitoring Large Landscapes Overview of CCMS Architecture Alert Handling Monitoring Components New Features at a Glance Summary

SAP AG 2005, Monitoring Detailed Overview / 17

Alert Handling Overview


Non-SAP component SAPCCMSR
Shared Memory Segment

SAP Web AS Java SAP Web AS Java SAPCCMSR

Push
Central Monitoring Infrastructure ABAP Stack

Shared Memory Segment

Alerts displayed

SAP NetWeaver Administrator Java Stack

Central Alert Notification

SAP Basis 3.0 SAP instance


Shared Memory Segment

Push

SAP Web AS ABAP SAPCCM4X SAPCCM4X SAP instance


Shared Memory Segment

SAPCM3X

SAP AG 2005, Monitoring Detailed Overview / 18

Monitor Sets and Monitors

View Monitoring Tree Elements


All tree nodes

Monitoring Object

Represents one physical or logical object Summarizes alerts and propagates them to higher nodes

Monitoring Attributes

Receive data and may create alerts Use data for analysis alerts

SAP AG 2005, Monitoring Detailed Overview / 19

History and Current View

Switch between views

Current

History

SAP AG 2005, Monitoring Detailed Overview / 20

Displaying Alerts

Doubleclicking a node shows all corresponding alerts

SAP AG 2005, Monitoring Detailed Overview / 21

Removing the Cause of an Alert

1) Mark the alert

2) Start the analysis method in the monitored system

CEN
SAP AG 2005, Monitoring Detailed Overview / 22

Analysis Method in Monitored System


Example

Monitored system
SAP AG 2005, Monitoring Detailed Overview / 23

Completing Alerts

3) Alert cause resolved in monitored component: Complete the alert in CEN

CEN
SAP AG 2005, Monitoring Detailed Overview / 24

Agenda

The Challenge: Monitoring Large Landscapes Overview of CCMS Monitoring Architecture Alert Handling Monitoring Components New Features at a Glance Summary

SAP AG 2005, Monitoring Detailed Overview / 25

Monitoring Components
Monitoring Special Components SLA Reporting Availability Monitoring

SAP AG 2005, Monitoring Detailed Overview / 26

Monitoring Components
Monitoring Special Components

Central Central Monitoring Monitoring

Internet Pricing
and Configurator Host

RZ20 RFC

SAPCCMSR

IPC

CEN

SAP AG 2005, Monitoring Detailed Overview / 27

Monitoring Components
Monitoring Special Components

Central Central Monitoring Monitoring

Business Connector Host BC BC Jmon-API Jmon-API

RZ20

RFC

SAPCCMSR

CEN

SAP AG 2005, Monitoring Detailed Overview / 28

Monitoring Components
Monitoring Special Components
Central Central Monitoring Monitoring

ITS
SAPCCMSR DLL DLL

RZ20

RF

C
AGate

RF

ITS
SAPCCMSR DLL DLL

CEN

AGate

SAP AG 2005, Monitoring Detailed Overview / 29

Monitoring Components
SLA Reporting Important for Reporting on Service Level Agreements (SLA):
Component availability Front-end response times (SAPGUI) Transaction-specific response times Standard response time ...

SAP AG 2005, Monitoring Detailed Overview / 30

Monitoring Components
New Components and Applications, and Solutions
Exchange Infrastructure 3.0 Mobile Infrastructure as of 2.5 Enterprise Portal 6/SP1; EP 5/SP6 SAP Business Intelligence (BI) as of 3.1 SAP Customer Relationship Management (CRM) as of 4.0 AP Supply Chain Management (SCM) as of 4.1 SAP Supplier Relationship Management (SRM) as of 2.0

SAP AG 2005, Monitoring Detailed Overview / 31

Monitoring Components
Availability Monitoring Heartbeat
Status of last availability check

Availability
Percentage of sucessful heartbeat checks over a given period of time

SAP AG 2005, Monitoring Detailed Overview / 32

Availability: Different Levels Different Mechanisms


Are all components up and running?
XML Message Request Central Central Monitoring Monitoring (GRMG) Any SAP Web AS Application (Java or ABAP) SAP J2EE Engine Application Server

Message Server CCMSPING Agent CEN RFC Destination SAP Web AS

Other SAP Components (SAProuter, ITS) Any RFC-enabled Component

Web AS 6.20

Check Process Monitoring

SAP AG 2005, Monitoring Detailed Overview / 33

Application Availability: GRMG and GRMG Lite


Availability in %, Heartbeat GRMG Lite as of 6.40 SP11

Central Central Monitoring Monitoring Infrastructure

http head / http get http status code / http status code and html output

Any Web Page

GRMG Infrastructure
<?xml version="1.0" <!DOCTYPE Customizing <!ELEMENT customizing <!ELEMENT control(grmg <!ELEMENT

GRMG Application XML Request GRMG Application XML Response

Java Application ABAP Application SAP Web AS

Configuration File

SAP Web AS ABAP 6.20


GRMG = Generic Request and Message Generator
SAP AG 2005, Monitoring Detailed Overview / 34

Newest Features of GRMG


GRMG classic for SAP applications; GRMG Lite HTTP PING / HTML scan for any web page Password encryption and improved logon capabilities Easy-to-use scenario editor Analysis utilities Start/stop scenario execution Scenario monitoring pauses Scenario runtime measurement

SAP AG 2005, Monitoring Detailed Overview / 35

Application Availability
Example from SAP CRM Interaction Center Checking the Broadcast Messaging Server with GRMG

Component availability

Scenario availability

SAP AG 2005, Monitoring Detailed Overview / 36

Availability Checks With CCMSPING


Are all components up and running?

Central Central Monitoring Monitoring Message Server

SAP J2EE Engine Application Server

push
CEN

CCMSPING Agent

SAP Web AS

Other SAP Components (SAProuter, ITS)

Web AS 6.40

SAP AG 2005, Monitoring Detailed Overview / 37

Availability Checks With CCMSPING


Newest Features Multiple CCMSPING agents in one landscape, for example, one per system group CCMSPING pushes data to CEN in one-minute intervals Dynamic management of monitoring by way of reference system groups

SAP AG 2005, Monitoring Detailed Overview / 38

SAP System Landscape Availability


Availability Monitor for SAP System Landscapes using the CCMSPING agent
One availability node per monitored system System availability

ABAP Instance

Java Instance

SAP AG 2005, Monitoring Detailed Overview / 39

RFC Destination Check

Central Central Monitoring Monitoring

RFC Destination Check CEN

RFCLIB
Any RFC-enabled Component

SAP AG 2005, Monitoring Detailed Overview / 40

RFC Destination Check


Example from SAP CRM Internet Sales Checking Availability of the Product Catalog Servers RFC Destination

RFC destination availability

SAP AG 2005, Monitoring Detailed Overview / 41

Process Monitoring

Central Central Monitoring Monitoring

SAPOsCol

processX processX

*procmon.ini

processY

SAPCCMSR

CEN

SAP or Non-SAP Component

SAP AG 2005, Monitoring Detailed Overview / 42

Process Monitoring

...\prfclog\procmon\

<xyz>procmon.ini

MaxDB is alive

SAP AG 2005, Monitoring Detailed Overview / 43

Windows Event Log Monitoring

The Windows Event Log in the Alert Monitor (triggered by switch in SAPCCMSR.INI)

SAP AG 2005, Monitoring Detailed Overview / 44

Agenda

The Challenge: Monitoring a Landscape Overview of CCMS Monitoring Architecture Alert Handling Monitoring Components New Features at a Glance Summary

SAP AG 2005, Monitoring Detailed Overview / 45

New Features at a Glance: ABAP Stack

Enhanced Availability Checks Performance Data Persistence and BI Reporting CCMS and Alert Management Statistical Records Correlation (enhanced as of 6.20) Enhanced CCMS Agents Open Integration SNMP Data Exchange With Third-Party Tools

SAP AG 2005, Monitoring Detailed Overview / 46

Enhanced Availability Checks


Availability of SAP System Landscapes
(using the CCMSPING Agent)

RFC Destination Check Application Availability


(GRMG)

SAP AG 2005, Monitoring Detailed Overview / 47

New Features at a Glance: ABAP Stack

Enhanced Availability Checks Performance Data Persistence and BI Reporting CCMS and Alert Management Statistical Records Correlation Enhanced CCMS Agents Open Integration SNMP Data Exchange With Third-Party Tools

SAP AG 2005, Monitoring Detailed Overview / 48

Performance Data Persistence Why?


Monitoring data is displayed as views on shared main memory. The performance data displayed in a CCMS Performance Monitor is volatile:
The size of the shared memory monitoring segments is limited. Monitoring data slots are continously overwritten.

Is there a need for persistent performance data? Yes! Long-term performance history reporting is needed, particularly for reporting purposes in the context of Service Level Agreements (SLA).

SAP AG 2005, Monitoring Detailed Overview / 49

Performance Data Persistence


SAP Web AS Java SAP Web AS Java

Non-SAP component
Shared Memory

Shared Memory

SAP System for SAP System for Central Monitoring Central Monitoring
SAP Web AS 6.20

Central Performance History

SAP Basis 3.0


Shared Memory

SAP Web Application Server

Shared Memory

SAP AG 2005, Monitoring Detailed Overview / 50

Performance Data Persistence


Features of the Central Performance History (CPH):
Central collection of monitoring data of the complete system landscape in a performant way. Handles minute, quarter-hourly and hourly monitoring data. Aggregations from minute values to hourly, monthly and yearly averages Reorganization provided Accessible from the Alert Monitor Configurable, scheduled reporting Export of reported data to operating system level supported

SAP AG 2005, Monitoring Detailed Overview / 51

Analyzing Monitoring Data in BI Why?


The CPH provides limited reporting on CCMS data stored in the central monitoring system. Highly sophisticated reporting on such data can be achieved using SAP Business Intelligence (BI). BI has the following benefits:
Central part of SAP NetWeaver Optimized for saving and analyzing huge amounts of data Flexible and personalizable reports Linking of reports (drill-down analysis) Correlation of independent data sources (CCMS, CRM, FI) Powerful SAP BI analysis tools (correlations, trends, .) Low-cost Service Level Management

SAP AG 2005, Monitoring Detailed Overview / 52

Data Flow Overview


As of 2006

Central Monitoring
ABC DEF Monitoring Infrastructure
Workload Statistics

Business Intelligence
Info Cube

STAT Extractors

CPH
XYZ

Extractors Performance Data

Info Cube

SAP Web AS 6.40

BI Content 3.52

SAP AG 2005, Monitoring Detailed Overview / 53

Monitored Systems

Alert Monitor displays data of the last 24 hours

CPH stores data older than 24 hours

Report

Analyzing Monitoring Data in BI


Facts and Benefits :
All performance data (from ABAP and Java stack) is collected in CPH:
Central data collection, aggregation, and reorganization Delivered for CEN releases as of SAP Web AS ABAP 6.20 SP17

All data collected in CPH is transferred into BI


CCMS data is stored in several BI data containers (info cubes). Demo reports are available. Powerful reporting design using BI reporting tools. Available as of SAP Web AS ABAP 6.20, Basis Plug-In 2004, and BI Content release 3.52.

Statistical data from (from ABAP and Java stack) is transferred to BI


BI as a central data platform for powerful root cause and performance analysis and SLA reporting. To be delivered in 2006.

SAP AG 2005, Monitoring Detailed Overview / 54

Analyzing Monitoring Data in BI


SAP Business Intelligence can link any data from various containers to create a new, virtual container.

SAP Performance Data

SAP Application Data

Non-SAP Customer Data

Report
Virtual Data Container
BI Standard Technology

Advantage: Innovative and highly flexible analysis options


SAP AG 2005, Monitoring Detailed Overview / 55

New Features at a Glance: ABAP Stack

Enhanced Availability Checks Performance Data Persistence and BI Reporting CCMS and Alert Management SNMP Data Exchange With Third-Party Tools Statistical Records Correlation Enhanced CCMS Agents Bi-directional Open Integration

SAP AG 2005, Monitoring Detailed Overview / 56

CCMS and Alert Management


What is Alert Management?
An SAP standard framework for active real-time delivery of mission critical information: Support for e-mail, SMS/Pager, Fax, WAP, Web Interface ... Personalized alert content and delivery Easy-to-use definition environment Preferred channels for messages Publish and subscribe mechanism for alert topics Displayed in EP universal worklist Escalation of alert notifications in case of inactivity Supported by CCMS as of SAP Web AS 6.20

SAP AG 2005, Monitoring Detailed Overview / 57

Central Alert Management Overview


SAP Web AS Java SAP Web AS Java

Alert
SAPCCMSR

Alert Inbox

WAP

Central Monitoring Central Monitoring

Push

Central Central Alert Management Alert Management

RFC
SAP Web AS CEN 6.20

ALM

SAP Web AS ABAP SAP Web AS ABAP

SAPCCM4X

Alert

SAPconnect: E-Mail, Fax, SMS, Pager, ...

SAP AG 2005, Monitoring Detailed Overview / 58

New Features at a Glance: ABAP Stack

Enhanced Availability Checks Performance Data Persistence and BI Reporting CCMS and Alert Management Statistical Records Correlation Enhanced CCMS Agents Open Integration SNMP Data Exchange With Third-Party Tools

SAP AG 2005, Monitoring Detailed Overview / 59

Workload Statistical Records


What are workload statistics used for?
To trace a business process running across multiple components To find out how often a component has been called By whom? For what reason? From where? To discover all parts and response times of a process To analyze problems in CCMS monitoring using the appropriate analysis function

SAP AG 2005, Monitoring Detailed Overview / 60

Statistical Records Correlation


Cross-Component Correlation Java writes distributed statistical records (DSRs)
ERP JAVA Engine ABAP Kernel APO ABAP Kernel

DSR
Web AS Java 6.20

STAT

STAT

Data is correlated across components using the GUID contained in the passport
SAP AG 2005, Monitoring Detailed Overview / 61

Central display aggregated detailed

New Features at a Glance: ABAP Stack

Enhanced Availability Checks Performance Data Persistence and BI Reporting CCMS and Alert Management Statistical Records Correlation Enhanced CCMS Agents Open Integration SNMP Data Exchange With Third-Party Tools

SAP AG 2005, Monitoring Detailed Overview / 62

Enhanced CCMS Agents


Non-SAP component SAP Web AS Java SAP Web AS Java SAPCCMSR SAPCCMSR
Shared Memory Segment

Shared Memory Segment

Push
Central Monitoring Central Monitoring
SAP Web AS ABAP 6.20 CEN

All monitoring data is pushed to CEN as of 6.20

SAP Basis 3.0


Shared Memory Segment

Push

SAP Web AS ABAP SAPCCM4X


Shared Memory Segment

SAPCM3X

SAP AG 2005, Monitoring Detailed Overview / 63

Enhanced CCMS Agents Details


Central Monitoring Central Monitoring
CEN

SAPOsCol Process Process External Components

RFC

JAVA

Agent
Data Supplier Data Supplier

JAVA Interface

SAP Instance SAP Instance External Software


Log File Alert File
Monitoring Segment

SAP AG 2005, Monitoring Detailed Overview / 64

Enhanced CCMS Agents Types


Different Types of Agents for Different Components SAPCCMSR
Monitors the SAP J2EE Engine and components without any active SAP instance. Transfers detailed OS data to CEN by help of SAPOsCol.

SAPCCM4X
Transfers CCMS alert monitoring data from any SAP System as of Release 4.0 to CEN Requires no dialog work process on central system Can be registered at several central systems to ensure high availability.

SAPCM3X
Connects SAP Systems 3.X to a central monitoring system delivering the dispatchers performance data.

CCMSPING
New: Now an active data supplier for SAP system landscape monitoring (pushes availability data to CEN) No longer requires a dialog work process on central system
SAP AG 2005, Monitoring Detailed Overview / 65

New Features at a Glance: ABAP Stack

Enhanced Availability Checks Performance Data Persistence and BI Reporting CCMS and Alert Management Statistical Records Correlation Enhanced CCMS Agents Open Integration SNMP Data Exchange With Third-Party Tools

NetWeaver Administrator (as of SAP NetWeaver 04, SP 12)

SAP AG 2005, Monitoring Detailed Overview / 66

Open Integration
Open Integration with Third-Party Tools Outbound Interface (XAL)
Tight integration with third-party monitoring solutions. Provides access to a central SAP monitoring system with SAP landscape monitoring data, including data from Java components.

New: Inbound Interface (XMW)


With XMW, third-party monitoring data can be reported into CCMS. Administrators can drill down into and trigger the third-party monitoring tool as an analysis method for further analysis.

Both interfaces are available for certification.

SAP AG 2005, Monitoring Detailed Overview / 67

Open Integration
New Inbound XML Interface
XML data is converted in a CCMS monitoring tree.
TP HT t Pos

Central Monitoring Central Monitoring

XML interface is delivered with SAP Web AS 6.20 and patched down to 6.10.

CCMS Monitoring Infrastructure

BAPI Call

CEN

SAP Web AS 6.10

SAPCCM4X Agent

XML

SAP AG 2005, Monitoring Detailed Overview / 68

New Features at a Glance: ABAP Stack

Enhanced Availability Checks Performance Data Persistence and BI Reporting CCMS and Alert Management Statistical Records Correlation Enhanced CCMS Agents Open Integration SNMP Data Exchange With Third-Party Tools

SAP AG 2005, Monitoring Detailed Overview / 69

SNMP Data Exchange With Third-Party Tools


Exchange of Monitoring Data with Third-Party Tools Using The SNMP Protocol
SNMP is a de-facto standard for system management and monitoring No additional interfaces required on the part of third-party tools Low-cost solution implies reduced TCO Central monitoring of components that support SNMP Supports status reporting of devices and components
(such as: SAP components or instances, network routers, switches, and printers)

Various SNMP versions supported

SAP AG 2005, Monitoring Detailed Overview / 70

SNMP Data Exchange With Third-Party Tools

No additional interfaces

Monitored Components

Third-Party Monitoring Console Central Central Monitoring Monitoring

Alerts exchanged as SNMP traps

Monitored Components

CEN

SAP AG 2005, Monitoring Detailed Overview / 71

New Features at a Glance: Java Stack


J2EE Integration into CCMS Monitoring Infrastructure Log Viewer Types Distributed Statistics Records One Agent Per J2EE Instance (as of 6.40) SAP NetWeaver Administrator The following slides provide a quick overview of these new features. For more details, use quick link JAVAMONITORING in the SAP Service Marketplace

SAP AG 2005, Monitoring Detailed Overview / 72

J2EE Integration into CCMS Monitoring Infrastructure

Central Monitoring Central Monitoring Infrastructure Infrastructure


Monitoring

J2EE Engine Visual Administrator

Logging

CEN

Performance Data

SAP Web AS ABAP

SAP Web AS Java

CCMS Alert Monitors also display the data collected by the J2EE Engine. Availability checks of monitored J2EE components Central data push to CEN by CCMSR agent NetWeaver Administrator will replace CCMS Alert Monitors and Visual Administrator.
SAP AG 2005, Monitoring Detailed Overview / 73

Monitoring Tree in Visual Administrator

SAP AG 2005, Monitoring Detailed Overview / 74

Log Viewer Types


Log Viewer Types
Central Log Viewer (NetWeaver Admin)
Web-based

Integrated Log Viewer (Visual Administrator)


All the logs written from the Engine and the running applications are automatically registered Customizing the properties, switching on Log Monitoring ...

Standalone Log Viewer for Central Log Viewing


Consists of Log Viewer Server and Log Viewer Client. Logs from a System Landscape can be viewed centrally in one Standalone Log Viewer Client, if one Log Viewer Server runs on every host.

Command Line Log Viewer Usage: lv.bat, delivered with Standalone Log Viewer
Only for viewing local logs on console Can be switched on during deployment Converts binary data into human readable data

SAP AG 2005, Monitoring Detailed Overview / 75

Distributed Statistics Records


Distributed Statistics Records (DSRs)
statistical data written by the J2EE Engine administered in the DSR Service of the Visual Administrator

SAP System for SAP System for Central Monitoring Central Monitoring Aggreg. statistics Single Record DSR Collector

Non-aggregated single records

SAP Web AS Java SAP Web AS Java DSR Service

Direct call for last minutes load

DB

Collector Database SAP Web AS ABAP 6.20


SAP AG 2005, Monitoring Detailed Overview / 76

Hourly data pull for statistics aggregation

SAPCCMSR File System Agent SAP Web AS Java 6.20

One Agent Per J2EE Instance


EJB / JMX

Central Monitoring Central Monitoring

Java 6.40 Java 6.40 Instance XX Instance XX

SAPCCMSR

Monitoring Segment XX

SAPCCMSR SAP Web AS ABAP 6.40


CEN

Monitoring Segment YY

Java 6.40 Java 6.40 Instance YY EJB / JMX Instance YY

Performance increase Easy-to-read monitors Thresholds of J2EE counters are maintained from CEN or Visual Administrator and stored in the J2EE database. SAPCCMSR with its monitoring data is treated like an SAP system.
SAP AG 2005, Monitoring Detailed Overview / 77

SAP NetWeaver Administrator


SAP NetWeaver Administrator is the new browser-based central administration and monitoring solution for your SAP NetWeaver system landscape. It will replace both CCMS Alerts Monitors and Visual Administrator.
Central Monitoring Infrastructure

ABAP

ABAP Stack SAP NetWeaver Administrator Java Stack

Central Administration and Monitoring

SAP NetWeaver Administrator is a Java application that is part of the shipment of SAP NetWeaver 04 from 6.40 SP 12 on and NW2004S.

SAP AG 2005, Monitoring Detailed Overview / 78

SAP Netweaver Administrator


Key Capabilities
NetWeaver Administrator will replace CCMS Alert Monitors and Visual Administrator. Monitors ABAP and Java components together in a new Web application Clear and structured data presentation State-of-the-art application based on WebDynpro, which meets latest SAP UI standards Deals with current / historical data and alerts Central Web-based log viewer

SAP AG 2005, Monitoring Detailed Overview / 79

SAP NetWeaver Administrator


Central Monitoring and Administration System
ABAP Monitoring Infrastructure
SAPCCM4X

ABAP

Java J2EE Engine

NetWeaver Administrator

Monitored Components

SAPCCMSR -j2ee

SLD System
J2EE Engine SLD

Java

SAP AG 2005, Monitoring Detailed Overview / 80

Agenda

The Challenge: Monitoring a Landscape Overview of CCMS Monitoring Architecture Alert Handling Monitoring Components New Features at a Glance Summary

SAP AG 2005, Monitoring Detailed Overview / 81

Summary
Central Monitoring of SAP Landscapes
NetWeaver Administrator will replace CCMS Alert Monitors and Visual Administrator. SAPs central monitoring infrastructure is flexible and fully scalable. Monitoring data is displayed centrally by
CCMS Alert Monitors Solution Manager SAP NetWeaver Administrator Third-party monitoring tools

Workload Statistics
Correlated across components (including Java) Displayed centrally in the Global Workload Monitor

Open integration with third-party products CCMS is an integral part of SAP technology Free of charge

SAP AG 2005, Monitoring Detailed Overview / 82

Certification for Third-Party Software Vendors


When third-party software is successfully certified, a company: Receives the right to use the SAP tagline Receives an SAP Interface Certificate Acquires a listing in the SAP online partner and product directory -- a valuable resource for customers and consequently an opportunity for vendors to market their software www.sap.com/icc Satisfies one of the criteria for becoming an SAP partner www.sap.com/partner

SAP AG 2005, Monitoring Detailed Overview / 83

Further Information
SAP Service Marketplace
For more information, use the quicklinks /monitoring and /javamonitoring.

Related SAP Training


http://www.sap.com/ Education ADM106, Advanced System Monitoring ADM100, SAP Technology Administration ADM200, SAP Web AS Java Administration

Contact
Mail to Product Management: Consulting contact: [email protected] Stephan Schmid ([email protected])

SAP AG 2005, Monitoring Detailed Overview / 84

Copyright 2005 SAP AG. All Rights Reserved


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, NT, EXCEL, Word, PowerPoint and SQL Server are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix and Informix Dynamic ServerTM are trademarks of IBM Corporation in USA 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, the Citrix logo, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, MultiWin and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML 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. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, R/3, mySAP, mySAP.com, xApps, xApp 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 in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies.

SAP AG 2005, Monitoring Detailed Overview / 85

You might also like