SAP administration can be complex, so that even the day-to-day monitoring of the environment can be a time-consuming task. How do you comprehensively and consistently check the status of all SAP instances in your environment without it becoming a drain on your time?
Cockpit ITSM simplifies the monitoring of your SAP environment. Instead of running your daily checks manually, Cockpit ITSM enables SAP administrators to create tailored daily reports to provide a comprehensive insight into the health of the entire environment. Create tailored reports to:
- Monitor operating system information,
- Identify errors,
- Confirm data recording,
- Monitor the status of all jobs,
- Guarantee reliable restores can be made, and
- Ensure optimum operation.
Reports are rapidly created using existing templates as their basis.
Creating a Report
Cockpit ITSM’s flexible reporting tool offers a number of standardized report templates which administrators can adapt as they wish. Included within the standard templates are several automated SAP report templates that can be easily configured to meet the unique needs of your own SAP environment. We estimate that it takes around 10 minutes to configure the template as required. This then generates an automated daily report with customizable alarm thresholds which can be configured to notify the SAP administrators and service team, as required.
It is our suggestion that the daily checklist includes:
- Availability of applications servers and their work-processes disp+work (SM50/SM51/SM66). The applications servers must be visible in the transaction SAP SM51 and all work-processes in status “WAITING”. Any work processes in error must be detected.
- Status of the last backup and backup log (DB12) - these two elements are essentials in case of a restore.
- SAP Update status (SM13). When the SAP update is stopped, data is no longer inserted into the database - the SAP system is not operational.
- Lock entries (SM12). Lock entries that are too old may be problematic and sometimes have to be deleted.
- Short dump (ST22). A short dump occurs when a ABAP program is terminated due to a problem. The origin of the problem can vary (for example, error in the ABAP code, internal R/3 problem, etc.) and unusual shorts dumps require an investigation.
- System logs (SM21). The system log is the place to find information about any serious errors that may have appeared in the SAP system.
- Background jobs (SM37). Jobs in error or running for long a long time must be analyzed.
- Operating system information (ST06): memory usage, CPU usage, etc.
- Other checks can be added per the specifics of your SAP environment: for example, live cache status (LC10) for an APO system; process chain statuses (RSPCM) for a BI; dialog response time (ST03) for the performance of a system, etc.
However, because you can tailor the report to meet the demands of your own environment this doesn’t have to be an exhaustive list.
The flexibility of Cockpit ITSM makes it a uniquely effective solution for IT teams to manage their environments and their workloads.