SAP Monitoring

Agenda
SAP Solutions CCMS Monitoring Architecture Alert Framework Solution Manager Monitoring Solution Manager Diagnostics Solution Manager Reporting NC Enhancements Third party monitoring Future outlook

SAP SOLUTIONS

Monitoring Applications
BASIS: CCMS monitoring infrastructurearchitecture Alert Framework (ALM) SAP Solution Manager 4.0
System Repository SSM Monitoring Diagnostics Business Process Monitoring IT Performance Reporting EWA/SLR IT Performance (CPH/BI) System Administration

Wily Introscope For minimum TCO, you can use it on one system. For maximum flexibility, you can use it on different systems.

SAPs View

CCMS MONITORING ARCHITECTURE

CCMS Monitoring Architecture Overview

CCMS Monitoring Architecture Internal

CCMS Monitoring Architecture Standard Interface

CCMS Monitoring Architecture Standard Interface: details

Monitoring Set MTE (Monitoring Tree Elements)
Monitoring Object: A collection of related monitoring attributes. (E.g.: Object -> Filesystem C: Attributes -> Freespace and Percentage_Used) Monitoring Attribute Virtual tree nodes

Different Views
Current Status Open Alerts

Usage of Colors

CCMS Monitoring Architecture Standard Interface: Views

CCMS Monitoring Architecture Standard Interface: Alerts

CCMS Monitoring Architecture Methods

Datacollection Methods Supply data for the monitoring infrastructure. Autoreaction Local versus Central autoreactions E.g.: Send e-Mail, start transaction, run operating system command Analyse methods Used to zoom directly to application that can analyse the alert problem. (Not available yet for J2EE problems, will be available in the future releases of NetWeaver Administrator)

CCMS Monitoring Architecture Analyse

CCMS Monitoring Architecture Monitor (Sets)

Besides the monitor sets that are part of SAP standard its possible to create your own monitors and sets. Possibility to create a monitor that only holds the items you need. Static versus Rule based monitor sets System groups

CCMS Monitoring Architecture Monitoring Attributes

Attributes define how and when an alert should be triggered and what reactions can or will be used. Attributes that can be influenced: Data-, autoreaction and analyses methods Thresholds Severity Number of alerts to be kept Heartbeat alert etc. Attributes can inherit properties from higher level nodes Possibility to transport attributes via property sheets

CCMS Monitoring Architecture SAP Default templates

SAP delivers predefined monitor Sets and monitors Some examples are:

SAP CCMS Monitor Templates - Entire System SAP J2EE Monitor Templates Engines SAP CCMS Technical Expert Monitors System / All Monitoring Segments / All Monitoring Contexts

CCMS Monitoring Architecture SAP Default templates

The default templates contain monitors for: Operating system Database SAP R/3 Services Transports Communication Performance Security J2EE applications Error messages Etc.

CCMS Monitoring Architecture Availability Monitoring

Different Levels Different Mechanisms Availability monitoring can be performed at different levels using one of the following mechanisms:
Application availability monitoring by means of an XML message request and response mechanism (called Generic Request and Message Generator, GRMG) System and component availability using the CCMSPING agent CCMSPING pings against the message server of SAP systems to retrieve instance availability information. This is used to efficiently monitor availability of a large number of SAP systems from a central location. Dummy logon checks can also be performed. RFC destination check You can check the availability of any RFC-enabled component. The RFC server answers periodic RFC pings from the monitoring system. Process monitoring

CCMS Monitoring Architecture Availability Monitoring

CCMS Monitoring Architecture CENtral Administration

CCMS Monitoring Architecture CENtral Administration

Topology overview Method definition (Datacollection, autoreaction and analyse) Properties Definition of system groups Configuration of Central performance history System repository Availability Monitoring (Monitoring Pause)

ALERT FRAMEWORK

Alert Framework

Alert Framework
Alert Inbox Alert Handling Alert Categories Connection to CCMS Sending e-Mail, SMS, etc Alert History Used by other applications like XI, Workflow, Business Object Repository, etc

Alert Framework Alert Inbox Layout

Alert Framework Alert Handling

Possible actions with ALM Alerts: Reserve Complete Forward Escalate Reject NewColutions enhancements to the alert inbox: Auto Refresh Multi-Select Connection back to CCMS Search Filter

Alert Framework Alert Categories

Structure for Alert reception Alert reception can be done by:
Fixed recipients Role Role and subscription

Definition of escalation Possibility to use rules Connected to CCMS by autoreaction. The autoreaction defines which category receives the alert.

Alert Framework E-Mail / SMS

Alert Framework E-Mail / SMS

- Uses SAP Connect Messages possible through:
E-Mail SMS Pager Fax Etc.

- Forward alerts based on time rules

Alert Framework Other usages

ALM is also used by the following
Business Object Repository triggering events in case certain changes occur in a BOR object (event linkage). For example, an alert is to be triggered if a purchase order was changed. Post Processing Framework (PPF) checking certain conditions and triggering alerts if the conditions are met. SAP Workflow Custom made alert triggers

Besides the alert inbox its also possible to display the alerts in the Universal Work List UWL of SAP Portal.

SOLUTION MANAGER MONITORING

Solution Manager Monitoring Components

System Repository

System Monitoring

Central System Administration (CSA)

Business Process Monitoring

System Repository System Input

System Landscape defines systems that will be monitored. Possibility to generate connections Automatic system data import via SLD or RFC. SLD connection recommended.

System Monitoring CCMS Based

System Monitoring based on Solutions and CCMS architecture. Solution Manager displays CCMS alerts on a different way. MTEs to display can be selected per solution. Status information on component level with drill down capabilities

System Monitoring Solution/System view

System Monitoring Alert overview

Business Process Monitoring Overview

Business Process Monitoring Example: Sales Order Management

SOLUTION MANAGER DIAGNOSTICS

Solution Manager Diagnostics Definition

Analysis tool for Root-Cause Analysis Analysis tool for End-2-End (E2E) problems SAP Portal for remote support on J2EE systems Provides only read access, no changes possible Netweaver Administrator is used next to diagnostics for local system maintenance. Input for J2EE EWA reports

Solution Manager Diagnostics Overview

Diagnostics Functionality
- OS and DB Access (Read only) - E2E Change Analysis Compare system with other systems or with itself on different times. - E2E Trace Analysis Pinpoint the problem area within a multiple system scenario (eg portal -> ecc -> crm) - E2E Workload Analysis Examines the workload cross-system. (ST03N) - E2E Exception Analysis Collect all erroneous info from a multiple system scenario (System Log Messages, Dumps, J2EE Log File Errors,

Solution Manager Diagnostics Architecture

Central Diagnostics server application
Running on central monitoring system

Central Wily Introscope System

Third party product that is part of SAP Netweaver Like cronacle basis can be used for free, full functionality is licensed.

Diagnostics agents.
Running on the connected satellite systems. (As of NW04s SP15 installed automatically)

Wily agents
Deployed on the j2ee stack of the satellite system

EG: E2E Trace

Solution Manager Diagnostics Wily Introscope

SOLUTION MANAGER REPORTING

EarlyWatch Alert Definition

Earlywatch alert report is a periodic alert report that checks the system state over time based on rules that are maintained by SAP. EarlyWatch Alert is available for different components: SAP ERP / Enterprise SAP Web Application Server SAP NetWeaver SAP APO/SCM SAP BW /SEM SAP XI SAP EBP/ CRM SAP EP SAP Bank Analyzer EWAs for different components contain both common content and component specific content

EarlyWatch Alert Central Repository

Service Level Reporting Monitoring Functions

Systems Availability Performance Hardware capacity Configuration parameter changes Errors Database space management Applications Response time by business process step Performance for dedicated transactions Update errors for dedicated transactions Software changes Monitoring of background jobs Interfaces Interface errors

Service Level Reporting Data Collection

Service Level Reporting KPIs

Service Level Reporting Example KPI

Central Performance History Functionality

Persistence layer for collected data

Used for long term monitoring and trend analyses

Has own reporting facilities Can be used as input for both Service Level Reporting and BW reporting

Central performance History Usage

BI Reporting
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: Integrated in SAP NetWeaver Optimized for saving and analyzing large amounts of data Flexible and personalizable reporting Linking of reports (drill-down analysis) Correlation of independent data sources (technical, SAP application data, SAP Solution Manager data) Powerful BI analysis tools (correlations, trends, .) Low-cost Service Level Management

BI Reporting Architecture

BI Reporting KPIs
Close to 100 KPIs are reported to the BI system!

BI Reporting Datasources

BI Reporting Graphical reports

NC ENHANCEMENTS

NC Enhancements
Alert Inbox
Central screen with alerts in progress Auto refresh Usage of colors Multi-select Search Filters Back connection to CCMS

Autoreactions
Solution for monitoring pauses Change of system names towards ALM Auto assign auto reactions

Availability Dashbord

NC Enhancements Availability Dashbord

NC Enhancement Alert Inbox

THIRD PARTY MONITORING

Third party monitoring

Third party monitoring Integration

FUTURE OUTLOOK

Planned enhancements
New Central Monitoring Architecture based on the existing Diagnostics/Wily platform. - Central CCMS will be replaced by Wily - Less maintenance costs because total architecture can be maintained centrally (Agents/Thresholds). - Alert Correlation - Alert Inbox functionality like the NC Enhancements - End-user experience monitoring - End-to-End reporting - Wily has many monitoring options for non-SAP (SAP monitoring is included in the license).

E2E Monitoring/Analysis

E2E Monitoring

E2E Monitoring

E2E Alerting

End-User Experience

E2E Reporting

Software Lifecycle Management

The End

Questions?