Monitor the Health of Your System with BW Reports

  • by David Hill, SAP Basis Administrator
  • Kumar Srinivasan, BW Consultant
  • July 1, 2006
The latest addition to the Computing Center Management System gives you the ability to extract Central Performance History data to your BW system where you can then analyze and correlate it graphically. You need a central monitoring system on Web Application Server 6.40 and BW Release 3.5. This new functionality can help you prevent unexpected outages of systems and applications as well as see trends and report on service-level agreements.
Key Concept

SAP has long provided system monitoring as part of the Computing Center Management System (CCMS). SAP delivers every ABAP system with CCMS monitoring installed and available for standard functions. The main entry point for CCMS monitoring is transaction RZ20. With it you can view monitoring information in the nodes called monitoring tree elements (MTEs). The available MTEs include response time for dialog, background, update, and spool processes; various queue lengths; operating system information such as CPU utilization, file system capacity and paging, and system availability; and Application Link Enabling (ALE) layer health.

Since R/3 Release 4.6D, you can monitor MTEs in multiple systems from one central monitoring system (referred to as CEN). However, the data available was only a point-in-time snapshot. With Web Application Server (Web AS) 6.20, SAP created Central Performance History (CPH) to allow long-term storage of the collected data. Reporting on that data was cumbersome and involved downloading to Excel. Now with Web AS 6.40, you can extract CPH data into BW.

New functionality in Web Application Server (Web AS) 6.40 allows you to extract the data in Central Performance History (CPH) to your BW system, which means you can easily report on it without having to download that data to Microsoft Excel. IT management can use those reports to make decisions on a host of system issues. The benefits of having CPH data in BW include:

  • History: The BW system serves as the data warehouse for monitoring data. This may provide helpful clues about system performance over a period of time. This trending capability in turn prompts the systems administration team to take corrective action.

  • Graphical: A new user interface allows you to analyze the data graphically.

  • Correlation: It helps you understand interesting correlations between data — for example, the correlation between CPU utilization and the number of users on the system.

  • Service-level management: The data collected on system performance and availability through the central monitoring system (CEN) may form the basis for service-level agreements (SLAs) with user departments.

We’ll give you tips from our experience to help extract and analyze monitoring data from CPH, system requirements, and installation. We assume that your Basis team has already configured CEN on a Web AS 6.40 system and that you are working on a BW 3.5 system with 3.52 business content.

David Hill

David Hill has 10 years’ SAP experience, starting in security and then Basis administration. His goal is to create the most stable and well-monitored install base of systems and applications so businesses can automate processes and access information. His SAP experience includes daily operations, R/3 monitoring and troubleshooting, supporting SAP functional teams and ABAP developers, and resolving end-user problems, in addition to installation, enhancement, and upgrade projects.

See more by this author

Kumar Srinivasan

Kumar Srinivasan is a senior BW consultant providing services in all areas of BW and BPS development to clients in the U.S.

See more by this author


No comments have been submitted on this article. 

Please log in to post a comment.

To learn more about subscription access to premium content, click here.