Skip to Content

Monitoring your SAP NetWeaver Components

The Monitoring section deals with all generic tools, to be used on a daily basis by administrators to run SAP NetWeaver with best performance. Almost all SAP NetWeaver components offer additional expert tools for root cause analysis. These are covered in the corresponding components section.

SAP’s Computing Center Management System CCMS is SAPs central infrastructure for monitoring system landscapes: All landscape components are continuously checked. As a first and most important check, CCMS ensures the availability of all productive components. Moreover, additional checks savegard the overall system health. If something is wrong, an alert is triggered, and a person in charge can be notified automatically. Then, CCMS offer a central entry point for deeper analysis: Overview data of the faulty component is presented. Analysis tools guide the administrator directly into helpful expert tools for further analysis.

Besides CCMS, SAP NetWeaver automatically generates statistics information, which gives you both as aggregates a good overview, and additionally as single statistics detailed insight what has happened.

A convenient and fast way to notify in case of problems the person in charge, can be implemented via SAP Alert Management.

Because monitoring is such an extensive topic, the relevant documents are sectored in the following sub-topics:

Performance Monitoring with Statistical Records  
Statistical records give you an overview of the performance of your system. Each dialog step is recorded, an information like user and program name, response time, CPU time and more is logged. This information is very useful when you want to analyze the performance (or a performance bottleneck) of your systems.

Alert Management with SAP NetWeaver Application Server  
The Alert Management system is a business service provided by the SAP NetWeaver Application Server. SAP provides its customers with a wide variety of functions for the management of information that is critical to the user's work. The information is delivered actively and as quickly as possible. You cut considerably the costs incurred for the management of critical situations, because the response time is reduced significantly.

The CCMS Monitoring Infrastructure

The CCMS is SAPs central infrastructure for monitoring system landscapes. Keep in mind, however, that it is running in maintenance mode. With SAP Solution Manager 7.1, SAP will introduce the new Monitoring and Alerting Infrastructure (MAI).

Setting Up your Central Monitoring  
This section contains documents about setting up your central monitoring - from the general approach in the Monitoring Setup Guide to the installation of different Monitoring Agents and the use of the SAP Management Console.

Monitoring Availability  
System availability can be defined on differently depending on the technology layer: Following a bottom up approach, the lowest level of system availability is the existence of the corresponding processes on Operating System layer. Higher on the technology stack is a ping or a dummy login into a system. On application level, there may exist a real business availability check. SAP offers powerful availability checks on all layers.

Transaction RZ20: Working with Monitors and Methods  
The CCMS monitoring infrastructure, a solution within SAP NetWeaver, centrally monitors any IT environments - from individual systems through networked SAP NetWeaver solutions, to complex IT landscapes incorporating several hundred systems. In this section, you learn about the different functions of the Alert Monitor (transaction RZ20) - from creating your own rule-based monitors to using the predefined auto-reaction methods of the Alert Monitor.

Enhancing your Monitoring Possibilities  
This section contains documents which explain how you can extend the functions and the metrics of the monitoring infrastructure. The section focuses on expanding the standard functions by configuring the monitoring of new metrics (like event log messages or qRFC/tRFC calls) and on expanding the functions of the monitoring infrastructure with your own developments.

Former Member

No comments