SAP Basis

ADM100 Lesson: Monitoring Architecture
– Withanalertifanerroroccurs
– With help that provides cross-system detailed information if an
error occurs
– With the help of the CCMS Alert Monitoring Infrastructure and
the special transactions connected to it
Many components are involved in the processing of a business process
in the mySAP Business Suite. These components must be monitored, as
both a gradual reduction in performance and a sudden breakdown of a
component could susceptibly affect the entire productivity. It is a task of
the administrator to monitor the system landscape regularly, and not only
inthecaseoferrors,buttotakepreventativeaction.
For example:
A file system in which files of the SAP database are stored is 100%
full. The database can no longer extend the tables in the files. A user
performs a business transaction in the context of which a data record
should be asynchronously added to one of these tables. The insert
fails due to the space problem in the file system. The database error
is seen as so serious that the entire asynchronous update process is
automatically deactivated. All user sessions hang with the display
of the hour glass. The SAP system hangs. If the fill level of the file
system had been regularly checked, the administrator could have
created space in other file systems and avoided the system downtime.
Monitoring should be organized as efficiently as possible. There is not
enough time for an administrator to log on to each host component to
check its status. An efficient monitoring structure should be able to display
the entire system landscape at a glance centrally. If an error occurs, the
person responsible is automatically notified. Tools should be provided
for the analysis of errors that provide cross-system detailed information
about the problem.
2003/Q3 © 2003 SAP AG. All rights reserved. 473