Monitoring SAP NetWeaver
Use this scenario variant to monitor your SAP NetWeaver system landscape. For effective monitoring with as low a TCO as possible, we recommend that you use a central monitoring system, from which you can monitor your entire system landscape on the basis of the CCMS monitoring infrastructure.
The monitoring infrastructure offers the following advantages, irrespective of the display tool for the monitoring data:
● For nodes in which monitoring data is reported, there are rules for the generation of alerts, for example, if particular messages occur, or if defined threshold values are exceeded. An alert therefore represents a problem message that an associated workflow can trigger.
● You can assign methods to nodes. These include analysis methods, which call an appropriate special transaction from the display tool. You can use this transaction to analyze and solve possible problems or error situations. Auto-reaction methods, which are automatically executed in the case of an alert, are also available. You can, for example, inform the responsible employee about this alert by e-mail or SMS in this way.
● The monitoring infrastructure offers a flexible framework into which extensive monitoring and administration functions can easily be added. Certifiable interfaces allow both the transfer of other monitoring data into the monitoring infrastructure and also the export of the monitoring data for additional external processing. The elements of the monitoring infrastructure function largely independently of each other and can be further developed and adjusted independently of each other.
● You only need to maintain configuration settings once in the landscape, in the central monitoring system.

There are two powerful tools available in SAP NetWeaver to centrally display the monitoring data:
● NetWeaver Administrator (NWA)
The NWA unifies the most important administration and monitoring tools both for Java and for ABAP systems in a new, browser-based user interface. The most important advantages of the NWA are:
○ The NWA display all monitoring infrastructure data; that is, alerts and current and historical values.
○ You no longer need to switch between different tools for administration, troubleshooting, and problem analysis of your entire SAP NetWeaver system landscape.
○ There is a central administration tool available to you landscape-wide for Java and, increasingly, for ABAP systems for starting and stopping instances, checking configuration settings and logs, and monitoring error-free functioning of components.
○ The interface follows the current guidelines for interface design, is easy-to-use, task-oriented, and complete. By using Web Dynpro, it runs in a browser.
● Alert Monitor
Use the Alert Monitor (transaction RZ20) as the central ABAP tool for monitoring your entire system landscape.
In addition to the complete display of all monitoring data, the Alert Monitor provides all options for the central Customizing of the monitoring of your system landscape, such as maintaining the threshold values and assigning auto-reaction methods.

To use this scenario variant you require the following installable units:
System with activated usage types:
● Application Server ABAP
● Enterprise Portal (for SAP NetWeaver Administrator)
This scenario variant comprises the following IT processes:
Process |
What You Should Know… |
The monitoring data is collected locally (in the monitored component itself) or centrally (in the central monitoring system) in this IT process. |
|
In this IT process, the responsible people are automatically informed about the relevant problem if an alert occurs. |
|
In this IT process, the responsible administrator determines and solves the cause of a problem. |
|
In this IT process, the troubleshooting is completed by adjusting the documentation or forwarding the problem to SAP. |
For detailed information about setting up central monitoring, see the Monitoring Setup Guide – SAP NetWeaver 7.0 at the Internet address service.sap.com/OperationsNW70.