sap standard for system monitoring · 2019. 11. 12. · sap® standard for system monitoring 2 sap...

SAP® Standard for System Monitoring

Version: 1.11

December 2008

SAP Standard for System Monitoring

Whitepaper

Active Global Support SAP AG

© 2008 SAP AG

SAP Standard for System Monitoring Version: 1.11

of 31


Table of Contents

Table of Contents..............................................................................................2

1 Management Summary ........................................................................3

2 SAP Standards for E2E Solution Operations.....................................4

3 The System Monitoring Standard at a Glance ...................................7

4 What is the Basic Concept of the System Monitoring Standard?....8 4.1 Architecture and Process Flow..........................................................................8 4.2 Configuring Central Monitoring........................................................................10 4.3 Operating Central Monitoring ..........................................................................11 4.4 Reporting .........................................................................................................12 4.5 Tools................................................................................................................14 4.5.1 Overview..........................................................................................................14 4.5.2 Integration of Non-SAP Monitoring Tools ........................................................17 4.5.3 KPI Definition and Categorization....................................................................18 4.5.4 KPI Monitoring and Optimization Tools ...........................................................19 4.5.5 Service Level Reporting ..................................................................................19 4.6 Outlook ............................................................................................................22

5 How to Implement the System Monitoring Standard? ....................23 5.1 Prerequisites....................................................................................................23 5.2 Methodology ....................................................................................................24 5.3 Setup ...............................................................................................................24 5.3.1 Process Implementation Steps........................................................................24 5.3.2 Output..............................................................................................................25 5.4 Trainings..........................................................................................................25 5.5 Further Information ..........................................................................................28

6 How to Measure the Success of the Implementation?....................29 6.1 Benefits............................................................................................................29 6.2 Setting up KPI monitoring................................................................................30

© 2008 SAP AG


of 31


1 Management Summary

This paper describes the system monitoring standard, one of the standards that SAP pro-vides to help customers optimizing the end-to-end operations of their SAP-centric solution. The standard explains basic principles of technical monitoring, focusing on monitoring key figures for performing a qualitative and quantitative assessment of system operation. The subject of monitoring interfaces and business processes is discussed in a separate standard. Depending on the situation, the available tools are deployed to varying degrees. This docu-ment focuses on proactive monitoring, that is, preventative solution monitoring that aims to prevent incidents. This contrasts with reactive monitoring and analyses using monitoring methods, which is discussed in the E2E Root Cause Analysis standard. Reactive monitoring is triggered when an incident occurs that requires a root cause analysis using monitoring methods. Proactive monitoring is based on reporting of historical developments and trends. In addition to proactive monitoring, this document also addresses Service Level Reporting.

Proactive monitoring can be automated to a certain degree. The most labor-intensive tech-nique is manual or expert monitoring. Here, analysis and statistical tools are deployed to query measuring points and evaluate them on the basis of experience. Appropriate measures are then applied to counteract critical developments. Since this procedure is labor intensive and requires extensive experience, customers strive to automate their monitoring processes. They do this by defining and measuring Key Performance Indicators (KPIs) and comparing and evaluating these with predefined threshold values. The quality of the automated monitor-ing concept largely depends on the selected KPIs and the definition of relevant threshold values. With fully automated monitoring, suitable countermeasures are automatically initiated when the threshold value is exceeded. Since the degree of automation depends on the effort and benefits involved, general recommendations cannot be provided. To verify the automated monitoring concept, however, manual expert monitoring is advisable. If it then transpires that adequate provision was not made for certain KPIs and their threshold values, the monitoring concept must be adjusted. Expert monitoring is also referred to as a health check and should be carried out at regular intervals.

This monitoring concept and its measured values should also be used as a basis for creating periodic reports on historical developments and, if necessary, trends. Forecasts can enable critical developments to be recognized and counteracted in good time. Selected KPIs also act as criteria for conducting a qualitative and quantitative assessment of system operations in the form of Service Level Reporting.

© 2008 SAP AG


of 31


2 SAP Standards for E2E Solution Operations

Mission-critical operations is a challenge. While the flexibility of SAP-centric solutions rises, customers have to manage complexity, risks, costs, as well as skills and resources efficiently. Customers have to run and incrementally improve the IT solution to ensure stable operation of the solution landscape. This includes the management of availability, performance, proc-ess and data transparency, data consistency, IT process compliance, and other tasks.

Typically, multiple teams in the customer organization are involved in the fulfillment of these requirements. They belong to the key organizational areas Business Unit and IT (see Figure 1). While the names of the organizations may differ from company to company, their function is roughly the same. They run their activities in accordance with the corporate strategy, cor-porate policies (for example, corporate governance, compliance and security), and the goals of their organizations.

Figure 1: Organizational model for solution operations

The different teams specialize in the execution of certain tasks: On the business side, end users use the implemented functionality to run their daily business. Key users provide first-level support for their colleagues. Business process champions define how business proc-esses are to be executed. A program management office communicates these require-ments to the IT organization, decides on the financing of development and operations, and ensures that the requirements are implemented.

© 2008 SAP AG


of 31


On the technical side, the application management team is in direct contact with the busi-ness units. It is responsible for implementing the business requirements and providing sup-port for end users. Business process operations covers the monitoring and support of the business applications, their integration, and the automation of jobs. Custom development takes care of adjusting the solution to customer-specific requirements and developments. SAP technical operations is responsible for the general administration of systems and de-tailed system diagnostics. And the IT infrastructure organization provides the underlying IT infrastructure (network, databases …). Further specialization is possible within these organi-zations as well. For example, there may be individual experts for different applications within SAP technical operations.

Efficient collaboration between these teams is required to optimize the operation of SAP-centric solutions. This becomes even more important if customers engage service providers to execute some of the tasks or even complete processes. Customers have to closely inte-grate the providers of outtasking and outsourcing services into the operation of their solu-tions.

Key prerequisite for efficient collaboration of the involved groups is the clear definition of processes, responsibilities, service level agreements (SLAs), and key performance indicators (KPIs) to measure the fulfillment of the service levels. Based on the experiences gained by SAP Active Global Support while serving more than 36,000 customers, SAP has defined process standards and best practices, which help customers to set up and run End-to-End (E2E) Solution Operations for their SAP-centric solutions. This covers not only applications from SAP but also applications from ISVs, OEMs, and custom code applications integrated into the customer solution.

SAP provides the following standards for solution operations:

• Incident Management describes the process of incident resolution

• Exception Handling explains how to define a model and procedures to manage ex-ceptions and error situations during daily business operations

• Data Integrity avoids data inconsistencies in end-to-end solution landscapes

• Change Request Management enables efficient and punctual implementation of changes with minimal risks

• Upgrade guides customers and technology partners through upgrade projects

• eSOA Readiness covers both technical and organizational readiness for enterprise service-oriented architectures (eSOA)

• Root Cause Analysis defines how to perform root cause analysis end-to-end across different support levels and different technologies

• Change Control Management covers the deployment and the analysis of changes

• Solution Documentation and Solution Documentation for Custom Develop-ment define the required documentation and reporting regarding the customer solu-tion

• Remote Supportability contains five basic requirements that have to be met to op-timize the supportability of customer solutions

© 2008 SAP AG


of 31


• Business Process and Interface Monitoring describes the monitoring and super-vision of the mission critical business processes

• Data Volume Management defines how to manage data growth

• Job Scheduling Management explains how to manage the planning, scheduling, and monitoring of background jobs

• Transactional Consistency safeguards data synchronization across applications in distributed system landscapes

• System Administration describes how to administer SAP technology in order to run a customer solution efficiently

• System Monitoring covers monitoring and reporting of the technical status of IT so-lutions

• Test Management describes the test management methodology and approach for functional, scenario, integration and technical system tests of SAP-centric Solutions

Out of this list, this white paper describes the system monitoring standard.

© 2008 SAP AG


of 31


3 The System Monitoring Standard at a Glance

The System Monitoring Standard covers monitoring and reporting of the status of IT solu-tions. The business unit expects that performance problems and errors are detected proac-tively and resolved before they affect business continuity. To provide transparency to cus-tomer business, customer IT has to report service levels, capacity trends and solution quality on a regular base. In order to fulfill on the demand of customer business given a limited IT budget, customer IT must industrialize and automate monitoring and reporting of the solution.

While root cause analysis (a separate standard) aims at problem resolution, system monitor-ing detects incidents automatically. Monitoring covers all technical components necessary to operate the business processes. You need Key Performance Indicators (KPIs) and a suitable measurement and monitoring in the areas of availability, stability, performance, throughput and security. Based on all data available in monitoring, web reports are defined that focus on service levels, capacity trends or solution quality, including third-party monitoring infrastructures. This allows unified evaluation of the availability of the whole system landscape. System Monitoring is owned and executed by SAP Technical Operations. Possible results are smoother business execution and optimized total cost of operations.

© 2008 SAP AG


of 31


4 What is the Basic Concept of the System Monitor-ing Standard?

4.1 Architecture and Process Flow

The SAP monitoring infrastructure consists of three levels:

• Data Collection: The components’ health is checked via data suppliers. SAP pro-vides a large number of preconfigured data suppliers, which are activated by default. If problems occur, the data suppliers raise alerts. Most of the data suppliers run in the local component. Nevertheless, there are some data suppliers which are triggered in a central monitoring system. For instance, the data supplier for checking the compo-nent availability does of course not run in the local component but centrally.

• Data Storage: The results of the data suppliers are stored in local shared memory segments for fast access.

• Data Display: All monitoring information is made available in the System Monitor-ing work center of SAP Solution Manager. Problems and alerts are displayed cen-trally in a single screen, the Alert Inbox, as soon as they occur, which reduces the time required for error identification and correction. In this way, SAP’s monitoring in-frastructure allows you to achieve greater efficiency at lower costs. Monitoring data can also be displayed in the native, underlying CCMS infrastructure, and in third-party solutions, which use an open SAP read interface to obtain the data. For further details, see below.

Additional configuration steps allow advanced technologies, such as notifications to specific recipients using different communication channels, meaning that administrators no longer have to actively check the systems for alerts.

Monitoring tasks depend on the usage type of your system (such as AS ABAP, AS Java, BI, EP …) and on the release. For an overview of all monitoring tasks, see the Technical Opera-tions Manual for SAP NetWeaver. For each usage type, the manual recommends a number of specific tasks. Look for Tasks in the Monitoring section of your usage type.

The concept of the monitoring infrastructure assumes that you declare a system in your sys-tem landscape that runs SAP Solution Manager. This option implies minimum total cost of operations (TCO). SAP Solution Manager 7.0 is a double-stack system, which is based on SAP’s newest platform SAP NetWeaver 7.0.

The monitoring information of your system landscape can be displayed in monitors in the System Monitoring work center of SAP Solution Manager itself. Alternatively, monitoring in-formation can also be displayed in third-party system management tools via certifiable inter-faces.

For non-ABAP based systems, workload metrics are collected with Wily Introscope (a third-party performance management application licensed by SAP and free of charge to SAP cus-

© 2008 SAP AG


of 31

http://help.sap.com/saphelp_nw2004s/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/45/dc863f455f3417e10000000a114084/frameset.htm


tomers for SAP standard products) and reported into SAP Solution Manager. The metrics can be displayed in SAP Solution Manager either with Online Dashboards or End-to-End Work-load Analysis (hourly aggregated). SAP recommends to implement End-to-End Diagnostics especially for all landscapes containing any Web AS Java based solution, SAP Enterprise Portal, SAP Exchange Infrastructure, SAP NetWeaver BI with Java Front-end, SAP Net-Weaver Master Data Management, SAP ERP 6.0 and SAP CRM 4.x and higher. For more details, please refer to http://service.sap.com/diagnostics and the ‘SAP Standard Root Cause Analysis’.

Third-party monitoring solutions can exchange monitoring data with SAP’s monitoring infra-structure through open interfaces for reading data out of and writing data into SAP Solution Manager.

Alerts are a key element of monitoring. They quickly and reliably report errors – such as val-ues exceeding or falling below a particular threshold value or that an IT component has been inactive for a defined period of time. These alerts are displayed both in the Alert Inbox of the System Monitoring work center and in the native CCMS alert browser (CCMS transaction code RZ20). Alert display has an auto-refresh functionality to ensure that most current alerts are shown. This reduces the workload for the system administration, since operators now only need to watch the error messages, instead of endless system data.

A lot of customers have third-party system management tools in place. These tools are strong in IT infrastructure monitoring. SAP gives these tools access to the alert information via certifiable BAPI interfaces (BC-XAL and BC-XMW). SAP recommends using system management tools, which are certified for using the interfaces. This guarantees consistency of alert information being displayed in SAP and in the tool itself. For more information, contact the SAP Integration and Certification Center (SAP ICC, http://www.sap.com/icc).

Special roles are required for system administrators responsible for central monitoring. For details, see the relevant sections in the SAP Security Guide, in particular Central Monitoring with CCMS and System Landscape Administration with SAP NetWeaver Administrator .

For a general monitoring overview, see the overview documentation in the SAP Help Portal.

System Monitoring includes several tasks for ensuring the system landscape runs correctly. These tasks exist alongside appropriate tools for supervision and evaluation.

The following tasks are exemplary for System Monitoring:

• Manual expert Monitoring: manual use of tools for analysis and statistics

• Partial Automatic Monitoring: definition and use of KPIs and useful thresholds

• Fully Automatic Monitoring: based on carefully adjusted sets of KPIs, thresholds and suitable auto reaction methods

• Health Check: manual verification of automatic monitoring with readjustment of KPIs and thresholds

• Periodical Reporting and Service Level Reporting: historical analysis and extrapola-tion of trends

© 2008 SAP AG


of 31

http://service.sap.com/diagnostics

http://www.sap.com/icc

http://help.sap.com/saphelp_nw2004s/helpdata/en/09/e319cedcc07142910c4c39b3abe8ad/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/40a442b024b211e10000000a155106/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/c8/40a442b024b211e10000000a155106/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/c82c42be6fde2ce10000000a1550b0/frameset.htm

http://help.sap.com/saphelp_nw2004s/helpdata/en/c2/c5e742be760121e10000000a155106/frameset.htm


System Monitoring must be done both locally and landscape-wide, using the appropriate tools provided. SAP Solution Manager is the recommended solution for landscape-wide monitoring. CCMS (Computing Center Management System) is the basic monitoring infra-structure, which can be used locally or centrally. Solution Manager also uses CCMS as its underlying monitoring infrastructure. Performance data can also be stored in the Business Intelligence (BI) component of SAP NetWeaver, enabling performance analysis of past peri-ods.

4.2 Configuring Central Monitoring

SAP Solution Manager is the recommended solution for central monitoring. It provides for an initial, quick and basic setup with preconfigured alerts.

Basic steps must be performed in the SAP Implementation Guide (IMG). Advanced configu-ration is covered in the Setup view of the System Monitoring work center.

The monitoring infrastructure allows you to monitor a large number of systems and servers.

There is a large number of useful functions provided by the underlying technical infrastructure that allow you to obtain information about the various systems in your IT landscape, their properties and status, but also to set important statuses:

• You can obtain an overview of the systems of which your IT environment consists.

• You can decide which systems are to be monitored and for which systems availability monitoring should be performed.

• You can assign certain analysis and auto-reaction methods to the alerts, which con-tribute to faster processing of the error. Administrators may be notified in case of alerts. Notifications must be configured as auto-reactions.

Alert thresholds are predefined by SAP. For example, the default “red” threshold for dialog response time is set to 3 seconds.

If properly configured, monitoring data is transferred between the monitored components and the central monitoring Solution Manager system by a pull mechanism.

SAP strongly recommends to also use a push mechanism for performance and efficiency reasons. The push mechanism is enabled by CCMS agents on the monitored components. CCMS agents are independent processes with an interface through RFC to a central monitor-ing system and an interface to the local shared memory. These agents provide additional features such as operating system and log file monitoring

In addition to using the standard CCMS alert handling, you can forward alerts to the SAP Alert Management (ALM). For more information, see Forwarding Alerts to Alert Management (ALM). ALM is a business alert delivery infrastructure, which offers personalized alert set-tings, rule-based determination of recipients, and fast alert delivery. Note that the use of ALM in the context of technical CCMS alerts is optional.

The setup and configuration process consists of the following steps:

© 2008 SAP AG


of 31

http://help.sap.com/saphelp_nw70/helpdata/en/77/d9ba3b3bf00152e10000000a114084/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a7da1505211d189550000e829fbbd/content.htm

http://help.sap.com/saphelp_nw70/helpdata/en/77/d9ba3b3bf00152e10000000a114084/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/en/3f/567ddea69d3d4c93a6aedabd08899e/content.htm

http://help.sap.com/saphelp_nw04/helpdata/en/3f/567ddea69d3d4c93a6aedabd08899e/content.htm


• Perform the basic configuration steps in the SAP Implementation Guide (IMG).

• Configure central monitoring in the System Monitoring work center. Check the SAP default threshold settings. For example, by default you will get a red alert, if the dialog response time exceeds 3 seconds. The thresholds can be main-tained centrally and distributed to the local component via the Change and Transport System.

• Install CCMS agents and register your landscape components.

• Configure notification for the most important alerts. For example, in case of a produc-tive system breakdown, the availability monitor triggers a red alert. The person in charge can be notified automatically via email or SMS.

Note: Configuring thresholds strongly depends on your business needs and on your IT sce-narios. All monitoring counters are configured with a default threshold, which can act as a good starting point. For instance, CPU utilization turns red at 98% CPU rate. To find an appropriate threshold, you can store a performance counter for some weeks, and analyze the average afterwards. The average gives you a feeling about your IT behavior. Finally, you can set the threshold 10-20% above / below the average, which indicates a clear deviation. For more information on setting thresholds, see the documentation in the work center setup.

4.3 Operating Central Monitoring

SAP Solution Manager is the tool for the setup, configuration and daily system monitoring. You can use the SAP Solution Manager for an initial, quick and basic setup with preconfig-ured alerts as well.

In SAP Solution Manager’s Monitoring work center you can display alerts in the context of a solution. A solution reflects systems and system components relevant to run one or more core business processes. In a solution, you display the alert information in a list, a graph, or in relation to your business processes maintained in SAP Solution Manager.

The monitoring process consists of the following steps:

1. A data supplier checks its component and detects a problem. An alert is generated.

2. The alert is pushed to SAP Solution Manager.

3. A central auto-reaction is triggered, which notifies the operator in charge.

4. The Work Center’s Alert Inbox acts as a Starting Point, from which you call the analysis method.

5. All alerts are displayed in a tree structure, or in a flat list. The alerts contain a status indicator with a color and a numerical value.

6. The operator drills down to the respective managed system for a first analysis. This is done by starting the predefined analysis function out of the alert list. The analysis function offers context dependent monitoring information. As of SAP Solution Man-ager 7.0 enterprise edition EhP1, KPI-specific history data is available for key per-formance indicators. Clicking an icon lets you display values for the last 30 days, with

© 2008 SAP AG


of 31


drill-down to a daily overview. In addition, predefined reports from IT Performance Reporting can be displayed for a historic analysis.

7. If the problem cannot be solved, a Service Message can be created from the Alert Inbox. The operator confirms the alert as soon as the problem is solved. The root-cause of a reported issue would then be found using Solution Manager Diagnostics.

If you have a certified third-party system management tool in place, the alert information is forwarded from SAP to the tool. All further analysis and correlation is done in the tool itself. Finally, the tool confirms the alert in SAP.

4.4 Reporting

SAP Solution Manager offers reporting options, from preconfigured standard to fully flexible expert reporting. The automated, preconfigured and standardized reporting functionality saves time and enables administrators to concentrate on their key competences.

The following reporting options exist:

• Limited reporting on historic performance data is supported by the Central Perform-ance History (CPH), which is an integral part of SAP's central monitoring infrastruc-ture. Customers can use this option if they are only interested in obtaining a simple historic performance overview.

• SAP Solution Manager is SAP’s application management platform. Therefore, sev-eral reporting functionalities regarding performance data and technical KPIs are lo-cated here. They offer a full range, from preconfigured standard to fully flexible expert reporting.

EarlyWatch Alert: SAP EarlyWatch Alert (EWA) is an important part of mak-ing sure your core business processes work. It is a report that monitors the essential administrative areas of SAP components and keeps you up to date on their performance and stability. SAP EarlyWatch Alert runs automatically to keep you informed, so you can react proactively to issues, before they be-come critical. EWA is most effective when activated for all SAP components in your solution. It exists both for Web AS ABAP and Java based systems.

Service Level Reporting: For business and management to measure the ef-fectiveness of IT and IT systems, service level agreements (SLAs) define the level of availability and software performance required. Service Level Report-ing (SLR) documents performance against those service levels over a set period of time. KPIs also include a large number of technically relevant indi-cators that provide useful information on the stability of and changes to the software and hardware. Examples of KPIs include system availability ex-pressed as a percentage, database and transaction response times, CPU load, and database growth.

• BI is the expert reporting solution. As SAP Solution Manager is based on SAP Net-Weaver, it contains BI as analytics standard from SAP. You can use it for perform-ance analysis on current and historic. It features great design flexibility and high-level reporting. BI lets you combine all kinds of data sources, in particular workload statis-

© 2008 SAP AG


of 31


tics from SAP Web AS ABAP and Wily Introscope, and EarlyWatch Alert data from monitored systems. All BI setup tasks are automated and all extractors for managed SAP systems come out of the box. You can focus on building web queries with the data already collected in CCMS Monitoring Infrastructure or statistics records, or data extracted for the root cause analysis scenario of SAP Solution Manager which is anyway required for support by SAP. Manual compilation of customer-specific IT re-ports can be avoided. If customers require flexible and full-scope reporting combining diverse data sources, they should use this option.

Note that the BI data model has been unified with SAP Solution Manager 7.0 enter-prise edition EhP1 regarding technical reporting. An enhanced extraction framework is used for collecting the data.

For more details on End-to-End Diagnostics, see http://service.sap.com/diagnostics.

SAP recommends setting up at least EWA. Service level reporting, either in SAP Solution Manager or in SAP NetWeaver BI, is important for those customers who have to prove IT load to internal departments or external customers (e.g., customers of IT service providers).

For more details, see the sections:

• Performance Reporting in BI in the SAP Community Network

• Unit EarlyWatch Alert, Service Level and Solution Reporting in the Technical Con-sultants Learning map of the SAP Solution Manager 7.0 Online Knowledge Product (OKP).

© 2008 SAP AG


of 31

http://service.sap.com/diagnostics

https://www.sdn.sap.com/irj/sdn/operations?rid=/webcontent/uuid/90f52300-c12e-2a10-29b3-e4aeb156496a

http://service.sap.com/rkt-solman

http://service.sap.com/rkt-solman


4.5 Tools

4.5.1 Overview

The CCMS monitoring infrastructure can be used to identify many key attributes of the SAP monitoring strategy (see Figure 2).

Figure 2: Monitoring Infrastructure

Agents continuously collect monitoring information for specific areas at local level. The latest measured values and alerts (if threshold values were exceeded) are stored in a buffer and reported to SAP Solution Manager. Current values and alerts can be displayed locally or further processed centrally in SAP Solution Manager. Alerts can be used, for example, to trigger automatic notifications to operators or initiate health checks. Only the values that are most important for the customer are stored centrally. Intelligent storage enables historical data to be analyzed – for example, as part of Service Level Reporting – or future bottlenecks to be predicted. The central display is fully embedded in the work center and, in addition to a view of the alerts (which can be filtered and personalized), provides direct access to suitable expert tools.

Automated IT operations are cost effective. For this reason, SAP recommends automatic, alarm-based monitoring. However, this requires experience, expert knowledge of system behavior, and adequate maintenance of the underlying threshold values. To this end, SAP provides additional expert tools that make the system status transparent for customers. Ex-

© 2008 SAP AG


of 31


pert tools facilitate proactive, manual health checks. The experience that the customer gath-ers with them can be integrated in the checks for the threshold values and the definition of automatic health checks, thereby optimizing automatic monitoring.

The following tools and infrastructure components play a fundamental role in ensuring that a central, proactive, and automated technical monitoring concept is successfully deployed:

Data sources:

• CCMS monitoring infrastructure

This is the basic infrastructure for centrally monitoring an SAP system landscape. This infrastructure is used whenever you display monitoring data, be in the “native” RZ20/21 alert monitors, in SAP NetWeaver Administrator or in SAP Solution Man-ager.

• SAP statistics data

Aggregated SAP statistics data is displayed centrally in transaction ST03G. The local equivalent is transaction ST03. Both transactions also display individual statistics re-cords. SAP statistics data can also be collected and displayed in SAP NetWeaver Business Intelligence. The "System Monitoring" work center can be used to access ST03G and call various BI reports.

• Log information

If it is not already available in the CCMS monitoring infrastructure, log information can be displayed in the SAP Log Viewer or SAP Management Console. Each technical component usually has its own log. The E2E trace technique enables logs and traces to be centrally integrated and analyzed in SAP Solution Manager. For a further, de-tailed check of a technical component, it is useful to deploy the component tools (which are usually extremely specific) locally.

• E2E root cause analysis based on Wily Introscope

The overview information from Wily Introscope is accessible from the "System Moni-toring" work center of SAP Solution Manager by means of a link. The data is dis-played in the browser. Detailed information is also collated in the "Root Cause Analy-sis" work center in SAP Solution Manager.

Tools and functions:

• SAP Management Console

The SAP Management Console provides basic monitoring functions out of the box. It is the appropriate tool for problems during the bootstrap phase, whilst the other tools won’t run with a stumbled startup of the NetWeaver Stack.

• SAP NetWeaver Administrator

The NetWeaver Administrator unifies the most important local administration tools both for Java and ABAP systems. SAP NetWeaver Administrator is based on the CCMS monitoring infrastructure and provides a user-friendly, Web-based view of the data. While the local version of the tool in SAP NetWeaver 7.1 replaces the SAP Vis-

© 2008 SAP AG


of 31

http://help.sap.com/saphelp_nw2004s/helpdata/en/7e/c82c42be6fde2ce10000000a1550b0/frameset.htm


ual Administrator and is thus becoming the most important tool for AS Java, the cen-tral version is integrated in SAP Solution Manager.

• Visual Administrator

The J2EE Engine Visual Administrator is a graphical user interface (GUI) that en-ables administration of all AS Java cluster elements and all modules running on them. It provides remote monitoring and management of managers, services, librar-ies, and interfaces working on each element in a single GUI. It will be replaced by the local NetWeaver Administrator in the NetWeaver 7.1 release.

• End-to-End Workload Analysis and End-to-End Exception Analysis

E2E workload analysis provides unified access to server side workload statistics. E2E exception analysis provides unified access to exceptions reflecting in high sever-ity log entries and dumps. Component specific log and dump viewers can be ac-cessed directly from the E2E exception analysis. Both exist as of SAP Solution Man-ager 7.0 SP10.

• System Monitoring

The system monitoring in the SAP Solution Manager, uses the Computing Center Management System (CCMS) (transaction RZ20) infrastructure. This means that sys-tem alerts which occur in the local CCMS are passed to the SAP Solution Manager via RFC connections between the SAP Solution Manager and the managed systems. The system shows these alerts in a graphic or in Sessions. You can also handle the alerts centrally, without having to go to the local CCMS of the managed systems.

You can see the alerts from several systems in a solution landscape in the SAP Solu-tion Manager in a graphical overview, in contrast to the local CCMS of the managed systems. This is the view of a central CCMS. You can also monitor non-SAP systems in a CCMS of a managed system.

• Business Process Monitoring

Business Process Monitoring is the proactive and process-oriented end-to-end moni-toring of the core business processes of a company. It includes the observation of all technical and business application-specific functions that are required for a smooth and reliable flow of the business processes. Business Process Monitoring is de-scribed in detail in the ‘SAP Standard Business Process and Interface Monitoring’.

• Reporting in SAP Solution Manager

SAP Solution Manager provides various reporting functions for measuring and docu-menting the quality of services provided by the IT organization. Your options span from using completely preconfigured reports, like SAP EarlyWatch Alert reporting, to defining reports in solution reporting for your individual needs with a great level of freedom.

For more tools, see the Tools section in the Technical Operations Manual or check the units Solution and System Monitoring in the Technical Consultants Learning map on the SAP Ser-vice Marketplace.

© 2008 SAP AG


of 31

http://help.sap.com/saphelp_nw2004s/helpdata/en/39/83682615cd4f8197d0612529f2165f/frameset.htm

http://help.sap.com/saphelp_sm40/helpdata/en/2f/de3316e1fc425080f83c718bec41de/content.htm

http://help.sap.com/saphelp_sm40/helpdata/en/42/b8cbc523183119e10000000a1553f7/content.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/fb/831042fc5b5733e10000000a155106/frameset.htm


Therefore, the "System Monitoring" work center in SAP Solution Manager is particularly im-portant as a central monitoring tool. It contains the following functions:

• Overview: System, instance, and service availability

• Alert inbox: For CCMS alarms

• Proactive monitoring: Overview and detailed monitoring tools for ad-hoc monitoring. A distinction is made here between AS ABAP, AS Java, and component-specific tools.

• Connectivity monitoring: For technical monitoring of interfaces

• Job monitoring: Status of background jobs

• Reports: Summary of EarlyWatch Alert, Service Level Reporting, and BI-based re-ports. These are divided into system-specific and cross-solution reports.

• Setup

• Direct access to self-diagnosis functions and Solution Manager Diagnostics is also provided.

• Further links (to SAP Central Process Scheduling by Redwood, for example) can be configured.

4.5.2 Integration of Non-SAP Monitoring Tools

Many customers also use components from other manufacturers to handle their business processes. In these hybrid landscapes, special system management products are often de-ployed. Nowadays, all major system management products provide integration scenarios with SAP. Integration is extensive and feasible in many different ways:

• At data collection level, partners can supply additional key information. A job schedul-ing system will provide optimum support for proactive monitoring if information is supplied about the scheduler status, jobs, and queues.

• Alarms can be forwarded to a partner monitoring system for central processing, along with alarms outside SAP. The BC-XAL interface, for example, provides dedicated ac-cess to CCMS alarms and up-to-date monitoring data.

• SAP Business Intelligence can be used as a central data store and provides many in-terfaces for reading and writing data. Partners can thus access landscape data cen-trally.

• Work centers represent an open UI concept. They provide a simple and direct inter-face to partner tools (for example, in the form of a link to the tool in the work center).

Example scenario:

Wily Introscope supplies valuable information for monitoring non-ABAP components. This information can either be accessed directly in the form of an expert tool or is stored in aggre-gated form in SAP NetWeaver Business Intelligence. Various reports in different work centers

© 2008 SAP AG


of 31


can be used to evaluate the Wily data together with other landscape information. The user can see which data source originally provided the information. In this way, heterogeneous IT landscapes can be represented and operated homogeneously.

4.5.3 KPI Definition and Categorization

Since different solutions are also based on different technical architectures and technologies, similar differences apply to the specific KPIs. From the E2E Solution Operations perspective, however, categories for technical monitoring can be defined and suitable KPIs assigned ac-cording to the solutions in question (see Table 1). Specific KPIs from the individual categories must then be incorporated in the central monitoring cockpit for each technical component.

Specification Proposed Threshold Value Category

Availability Heartbeat of a technical com-ponent

A missing heartbeat signals a fail-ure of the technical component

Average general response time Empirical value based on the stan-dard response time. Above-average deviations should be sig-naled

Performance

Response times of particularly important subcomponents or actions

The KPI values that endanger core business processes should be used as threshold values

Hardware: CPU, I/O, memory, operating system

Application: Memory, proc-esses

Utilization capacity

Processing queue: Overflows

Exception situations Terminations of processing steps, such as short dumps or exceptions

Unauthorized access or fre-quently failed access

Users with security-relevant authorizations

Security

Super user access

Table 1: Overview of Categories of Monitoring KPIs

© 2008 SAP AG


of 31


4.5.4 KPI Monitoring and Optimization Tools

If monitoring is to be automated as far as possible, it is extremely important that suitable threshold values are defined. A threshold value is only optimal if it actually signals an incident when the measured value is exceeded or undershot or an event occurs. If an alert is trig-gered without an incident occurring or if an incident occurs without triggering an alert, the automated monitoring concept is useless. The monitoring tools are therefore shipped with default values for SAP components that are based on empirical values. Despite every effort to standardize them, many of the threshold values depend on the actual system utilization. For this reason, the threshold values require iterative optimization, which, in turn, entails re-viewing the solutions manually at regular intervals. An expert checks whether critical aspects or tendencies have been missed in the automatic monitoring concept or whether threshold values need to be amended.

Work Center Tool Category

Availability System Monitoring -> Overview

Transaction ST03 E2E Trace

Performance System Monitoring -> Proactive Monitoring

E2E Workload Analysis

Transaction OS06

Transactions ST04, DB50

Utilization capacity System Monitoring

E2E Workload Analysis

Alert Inbox Transaction ST22

E2E Exception Analysis

Exception situations System Monitoring -> Alert Inbox

Log Viewer

Security Audit Log SM20 System Log SM 21

Application Log

Security System Administration -> User Administration

Further Logs and Traces

Table 2: Overview of the KPI Tools

4.5.5 Service Level Reporting

SAP EarlyWatch Alert (EWA) is a service provided by SAP that records technical measured values at regular intervals (usually weekly), depicts their historical development and trends, and evaluates the risk based on empirical values. Suitable countermeasures are also rec-ommended where possible. EWA is the first step towards an automatically generated report for evaluating critical KPIs. EWA is maintained and updated by SAP so that empirical values

© 2008 SAP AG


of 31


from almost every customer are integrated in the report. The only limitations are specific cus-tomer solutions that give rise to major discrepancies in the measured values and thus cannot be evaluated using generic and automated means. Nevertheless, EWA is a valuable report that exposes extreme customer situations even indirectly. EWA includes the most important categories and KPIs for ABAP and Java applications shown in the categories in Table 1.

Reporting for the relevant KPIs in E2E Solution Operations is closely linked with monitoring. Therefore, the monitoring tools integrated in SAP Solution Manager can easily be linked to the integrated BI.

By activating the Central Performance History (CPH) database in SAP Solution Manager, you can save and transfer in aggregated form all of the measured values that are sent from the data collectors to the CCMS. BI also includes the measured values from the E2E Root Cause Analysis tools (see Figure 3). This has the advantage that all of the data is available, as well as its historical development. By default, the KPIs are stored in aggregated form every min-ute, quarter of an hour, and hour. You can also take into account different time zones in the evaluations.

Figure 3: Reporting Architecture with Integrated BI

SAP Solution Manager delivers pre-configured reporting templates. Data from EWA, CPH, and other statistical data from E2E tools can be integrated in BI Reporting (see Figure 4). This data can then be evaluated using the powerful reporting tools that are inherent in BI. Naturally, the data can also be exported or transferred and, if required, analyzed with other tools.

© 2008 SAP AG


of 31


Figure 4: Service Level Reporting in BI

In addition to a simple list of the measured values and aggregated data, the KPIs can also be merged and represented as a graphic to identify trends in the KPI progression more easily. You can view the query definitions shipped by SAP in the BEx Query Designer in the CCMS Info Area. The query definitions are used in Web templates, which you can execute with your own metrics. This means that you can decide on the granularity of the evaluation yourself. You can publish the reports generated in this way at regular intervals by using the BEx Broadcaster, for example. Alternatively, you can make them generally available in the SAP NetWeaver Portal.

Regular reporting and evaluations are essential to guarantee the quality of the E2E Solution Operations, Service Support, and delivery processes. In a customer-outsourcer relationship, Service Level Reporting can be used to monitor the observance of the KPIs defined in the Service Level Agreement. The primary objective of solution operations, however, is to ensure that the solution is stable and provides a high level of performance. The requirements of the users, that is, the departments, ultimately dictate the parameters for E2E solution operations. For this reason, KPIs must be defined and reported on in accordance with these qualitative and quantitative requirements. Ideally, these KPIs should form the content of the Service Level Agreements. If they do not, you should compile regular reports in addition to Service Level Reporting. You can then use these reports to perform your own quality checks and detect and prevent bottlenecks early on. The reports, however, also enable departments to estimate their own work and evaluate and improve processes. At the same time, these KPIs can also be used in Business Process Monitoring.

© 2008 SAP AG


of 31


4.6 Outlook

SAP is currently investing in a new state-of-the art end-to-end alerting infrastructure. The goals of this development are:

• Provide a unique and centralized alerting approach for managed infrastructures such as ABAP, Java and .Net as well as unmanaged infrastructures as native com-ponents

• Retrieve metrics and simple events from different data providers such as CCMS at managed System or Wily Introscope via different data retrieving methods (Push and Pull)

• Derive complex events and end-user alerts out of the retrieved metrics and simple events to avoid „alert flooding“

• Provide end-user alerts for several alert consumers such as Alert Inbox, Incident Management and Notification Engine provided by SAP Solution Manager as well as 3rd party vendors

• Deliver a central directory for metrics, events and alerts and context information such as system landscape, business processes or interfaces including SAP and cus-tomer template knowledge

The diagnostics agent (resp. RFC communication) will be used for data retrieval instead of the CCMS agent on SAP's new alerting infrastructure. According to the current planning, this infrastructure and corresponding monitoring templates will be available for all SAP main-stream products with SAP Solution Manager 7.0 enterprise edition EhP2.

© 2008 SAP AG


of 31


5 How to Implement the System Monitoring Stan-dard?

5.1 Prerequisites

To implement System Monitoring, knowledge regarding the business requirements for avail-ability and throughput of the systems and technologies is required as well as technical details for the systems and interfaces involved. The affected organizations must be identified.

Furthermore, possible dependencies must be known and a holistic System Monitoring con-cept must exist.

Concerning the supervising function of System Monitoring, there are dependencies on all other topics, especially the following:

• Incident Management: occurrence of incidents prevented by automatic surveillance of the respective systems and interfaces

• Business Process and Interface Monitoring: monitoring of threshold values is es-sential for business process-oriented monitoring

• Root Cause Analysis: makes extensive use of System Monitoring information

• System Administration: Administration-related decisions based on monitored data

For customers with very high availability requirements, System Monitoring tools must be im-plemented as a high availability solution due to information reliability concerning the condition of the system landscape.

The goal is to set up a technical monitoring concept that is central, proactive, and automated:

• Central: A centralized monitoring approach simplifies both setup and day-to-day op-erations. Logons to the faulty component can be prevented if the problem can be rec-tified using the information stored in the central system.

• Proactive: Preventative solution monitoring detects problems right from the outset. In this way, severe disruptions to system operations can be counteracted in advance.

• Automated: Automated monitoring can respond quickly and reliably. It also reduces operating costs.

Central, proactive, and automated technical monitoring requires a dedicated SAP system that displays the monitoring data and alarms and provides the necessary tools and methods to analyze them. As part of its End-to-End Solution Operations offering, SAP combines all of the necessary tools in the work centers within SAP Solution Manager. For this reason, SAP Solu-tion Manager is ideal as a central monitoring component.

© 2008 SAP AG


of 31


5.2 Methodology

The concept of the monitoring infrastructure is that all required information is available in a central monitoring system. Problems are displayed as soon as they occur; all log files are also accessible from a central location, which reduces the time for error identification and correction.

Additional configuration steps allow advanced technologies such as notifications, meaning that administrators no longer need to actively investigate systems for alerts.

To configure the monitoring, perform the tasks described under the following link in the speci-fied sequence:

Configure the Monitoring Infrastructure

5.3 Setup

The setup of the central monitoring concept is divided into:

• An initial setup

• A continuous optimization of initial settings

In addition, a distinction is made between activities in the central part of the infrastructure and in the components that have to be monitored.

Requirements for a successful setup are:

• The availability of a dedicated system for central monitoring, like SAP Solution Man-ager 7.0 SP15+.

• The system landscape is entered in an SAP System Landscape Directory (SLD). The landscape data is also defined in the repository of SAP Solution Manager SMSY.

• An SAP NetWeaver Business Intelligence (BI) system is required to collect long-term monitoring information. Either the BI contained in SAP Solution Manager can be used here or, due to the volumes of data involved, a dedicated system.

5.3.1 Process Implementation Steps

In the initial setup phase, the following activities must be addressed:

1. The systems to be monitored must be registered in the central system. CCMS agents should be used here.

2. The KPIs that are relevant for alerts and ad-hoc monitoring must be defined. In addi-tion, the KPIs that are to be transferred to BI for reporting purposes and their level of granularity must be defined.

3. The default SAP threshold values for these KPIs must be checked.

© 2008 SAP AG


of 31

http://help.sap.com/saphelp_nw2004s/helpdata/en/02/411841a66af223e10000000a155106/frameset.htm


4. The documentation for these KPIs must be reviewed. Instructions must be compiled as to how to handle exceedings of thresholds.

5. The assigned analysis methods for these KPIs must be reviewed.

6. Author actions must be defined and assigned. Automatic notifications and execution of operating system commands are particularly significant here. Notifications can be made quickly using SAP Alert Management.

7. Data collection must be set up in BI. This step is usually carried out when Root Cause Analysis is set up.

8. The roles and work centers must be assigned and the central alert inbox set up.

As part of the continuous optimization process, the following questions must be answered:

• Do additional KPIs have to be taken into account to ensure reliable system operation?

• Do fundamental error situations occur where the relevant KPIs do not have any signifi-cance?

• Have the threshold values been defined appropriately? Are alarms triggered too late? Are too many alarms triggered with the result that they are ignored?

As part of this process, the relevant settings must be adapted continuously. The question of suitable threshold values can be answered using an historical analysis in BI Reporting.

5.3.2 Output

The result of the setup is the final operations handbook where the following information is included:

• Definition and usage of the tools & procedures

• Organization in the company including responsibilities, roles and activities

5.4 Trainings

The following training courses are available:

ADM106 – SAP System Monitoring Using CCMS I

In this course you will gain expert knowledge on using the CCMS monitoring infrastructure and learn to set up central monitoring of an SAP system landscape.

Course Content

• Structure and basic operating functions of the CCMS monitor

• Agent technology

• Steps for setting up central monitoring

• Monitoring remote systems

© 2008 SAP AG


of 31


• Creating your own static and rule-based monitors

• Special monitors for SAP components

• Using property variants for monitoring

• Maintain threshold values

• Maintain methods using MTE classes

• E-mail notification in case of errors

ADM107 – SAP System Monitoring Using CCMS II

This course consolidates and expands knowledge from ADM106 mainly with up-to-date SAP Web AS 6.40-related issues.

Course Content

• Configuration of the sapccm4x, sapccmsr, and ccmsping agents

• Using the central data cache

• Configuration of central auto reaction methods with e-mail notification

• Configuration and use of the central performance history and reporting on it using BI

• Monitoring background tasks

• Monitoring file contents using agents

• Availability monitoring of RFC connections

• Connecting the CCMS to Alert Management (ALM)

• Configuration of GRMG monitoring (such as Web site availability)

• Further details on system monitoring

SM100 - SAP Solution Manager for Operations of SAP Solutions

Course Content

• SAP Solution Manager Overview

• Installation Overview

• Customizing SAP Solution Manager

IMG structure (Basic and Optional Settings)

• Solution Monitoring

System Monitoring

Business Process Monitoring

© 2008 SAP AG


of 31


• Service Desk

Service Desk Reporting

Message Processing

• Service Delivery

Service Plan

Issue tracking

Maintenance Optimization

• EarlyWatch Alert Reporting

• Service Level Reporting

• Solution Reporting

Service Reporting

Availability Reporting

System Administration Reporting

• Solution Manager Diagnostics

• Change Request Management

E2E100 – End-to-End Root Cause Analysis

E2E100 covers tools and approaches for analyzing the root cause of incidents and isolate the component causing the incident in a heterogeneous IT landscape. Prerequisites for this course include an overview of SAP Technology as well as basic understanding of SAP Solu-tion Manager. Understanding of E2E Solution Support basic concepts as taught in the e-learning E2E50 is helpful to put root cause analysis in perspective to the other solution opera-tions areas change control, business integration and automation, and upgrades/SOA readi-ness.

E2E100 is a five day course ending with a certification exam in the afternoon of the fifth day. Upon successful completion of this certification, the participant receives the certificate ‘Appli-cation Management Expert – Root Cause Analysis’. The certification tests the knowledge in the area of the E2E root cause analysis. This certificate proves that the candidate has a basic understanding within this profile, and can implement this knowledge practically in E2E solu-tion operations. The certification test consists of questions from the areas specified below:

Course Content

• Introduction to End to End Root Cause Analysis

• Incident Management Process and Pre-clarification

• End to End Change Diagnostics

• End to End Workload Analysis

© 2008 SAP AG


of 31


• End to End Trace

• End to End Exception Analysis

• Data Inconsistency Analysis

• Client Side Root Cause Analysis

• Proving Stabilization of Solution Landscapes with SAP EWA

• Review and Certification Preparation

• Certification for the Application Management Engineer – End to End Root Cause Analysis

5.5 Further Information

Detailed information about SAP’s interfaces for reading CCMS monitoring data and alerts (BC-XAL) can be found on SAP Service Marketplace. SAP recommends using system man-agement software which has been certified for BC-XAL.

BC-XMW is an interface for writing monitoring information and alerts from outside into the CCMS monitoring infrastructure.

Overview presentations, documentation and SAP Tutors on CCMS are available in the SAP Service Marketplace using quick link /monitoring.

For specific information on NetWeaver Administrator, use quick link /nwa.

Overview presentations, documentation and SAP Tutors on Solution Manager are available in the SAP Service Marketplace using link http://www.service.sap.com/rkt-solman.

© 2008 SAP AG


of 31

http://www.service.sap.com/rkt-solman


6 How to Measure the Success of the Implementa-tion?

6.1 Benefits

Through the implementation of System Monitoring, customers benefit from using a proficient practice on supervision of systems and recognizing critical situations before they become business-critical. System Monitoring is an essential for other areas of End-to-End Solution Operations. Through acquisition of the correct data, customers are able to prove operational efficiency, optimize resource utilization, and increase control over enterprise-wide processes.

In addition, establishing one central and proactive strategy for System Monitoring reduces the cost for solution operations by avoiding organizational redundancies.

Benefits at a glance:

• Homogeneous management of heterogeneous solution landscapes by work center integration

• Central monitoring of technical components of a solution landscape (to a large ex-tent)

• Timely recognition of critical developments through graphical reproduction

• KPIs as criteria for quality and quantity in solution operations

• Expert tools, making the status of the system landscape visible to the customer

• Enablement of analyzing and improving business processes

• Increase in administrative efficiency, reducing total cost of operation

© 2008 SAP AG


of 31


6.2 Setting up KPI monitoring

A successful implementation of System Monitoring can be verified by installing a set of appropriate Key Performance Indicators (KPIs) and measuring them before and after the implementation. KPIs proposed in this context are listed in Table 3:

KPI Measuring

Availability of System Monitoring System Monitoring is set up and applicable

Availability of related tool chain Proven expert monitoring tools & procedures are available

Availability of automatic alerting Immediate alerting for business-critical incidents is available

Table 3: Measuring KPIs

© 2008 SAP AG


of 31


Copyright 2008 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, Excel, Outlook, and PowerPoint 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, iSer-ies, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation.

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.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, 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. Data contained in this document serves informational purposes only. National product specifi-cations 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 consequen-tial 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 informa-tion 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.

© 2008 SAP AG


of 31

sap standard for system monitoring · 2019. 11. 12. · sap® standard for system monitoring 2 sap...

Documents