Set Up Your SAP System to Monitor and Alert on Its Base Elements
- by Jim Baxter, Independent SAP Basis Consultant
- December 9, 2011
Faced with the bewildering array of monitors available in the Computing Center Management System (CCMS), it is not an easy task to define an acceptable range of monitors to provide a general picture of the health of your SAP systems. With SAP Solution Manager 7.0 systems up to enhancement package 1, Support Package 26, learn how to build a range of monitor elements using rules that help define an alerting infrastructure that does just that — monitor and alert on the base elements of your SAP system. Step through the setup and structure of the monitoring infrastructure.
The Computing Center Management System (CCMS) allows you to assess the well-being of SAP systems. It is fast, easy to configure, reliable, and — if correctly configured — highly effective. It has saved many SAP Basis technologists from embarrassment by providing advance warning of problems in their landscape. Using centralized monitoring in transaction RZ20 in the SAP Solution Manager system is a must in any SAP environment, even if you use only the basics, such as availability monitoring. You can neatly organize your monitor trees and receive advance warning of system failure, system slowdowns, interface problems, or system crashes.
The core of system monitoring lies in providing you with an understanding of how well your system is performing. Of course, to implement effective monitoring, you need the system to be able to understand all the elements involved. Using the Computing Center Management System (CCMS), you can do just that. By setting up the proper monitoring elements, you can be sure that the alerts in your system are acting properly. For instance, with critical batch job monitoring, when a critical job fails, an automated process is triggered that informs the responsible person.
If you look at a basic SAP ABAP system and try to understand what makes it tick, it simplifies the task of setting up the monitors. There are six basic areas:
- Operating system
- R/3 online tasks (referring to all online tasks in the ABAP stack)
- R/3 batch tasks (referring to all batch tasks in the ABAP stack)
- Printing and emailing
I’ll show you how to set up a monitoring environment based on these six elements so that for each defined system you can quickly see where faults may lie. In this article, I’ll focus on the method of how to monitor and in part 2 I’ll cover what to monitor. This article is intended for system administrators and technical managers, and requires no prerequisites beyond using an SAP Solution Manager system prior to 7.1.
Would you like to see this full item?