SAPtips Journal

February/March 2005 Volume III Issue 1

Basis Team Tools: Using CCMS to Monitor SAP ’s Performance

Page 1

By Joey Hirao, JoTech LLC
Editor’s Note: Set sail with Joey Hirao on the good ship CCMS (Computing Center Management System) as he navigates the potential perils of system monitoring and performance. Your cruise will take you to the various CCMS ports where you will learn what it is and how it has evolved over time. You will thoroughly explore the Operating System, Database, and SAP Basis Layer components of the system with Captain Joey at your side. Take the helm and learn to configure and use CCMS thresholds to see at a glance how the system is performing. If dark clouds are forming on the horizon, you’ll be the first to know once you’ve learned Joey’s methods for setting up early warnings messages via pager or email. Once you’ve mastered these techniques, you’ll find smooth sailing ahead on the seas of SAP system monitoring and performance. have monitoring tools to help with these operational issues. This article covers the use and configuration of SAP’s monitoring module called the Computing Center Management System, or CCMS; specifically for SAP on Unix with an Oracle database. This module works with SAP version 4.6x. Keep in mind that this article is not intended as instruction on performance tuning.

Using CCMS

CCMS is a combination of the mature system administration functions and transactions folder releases, coupled with the modern alert monitoring capabilities.

The module that we now know as CCMS (in the current release of SAP) evolved over the years from basic performance monitoring transactions. So, it’s no surprise that CCMS is a combination of the mature system administration functions and transactions folder releases, coupled with the modern alert monitoring capabilities. CCMS manages system monitoring with alert thresholds. Functionally, thresholds are merely an extension of monitoring. Monitoring provides data for specific parameters. Thresholds act as a boundary to these values. For example, database data buffer quality is merely a number. However, when a threshold is associated with it, that value inherits a quality such as poor, good, great. Now that we have done the formal introductions to the topic, lets get down to business. First off, let’s start by examining the monitoring aspects. CCMS breaks down monitoring into large components: • Operating System • Database • SAP Basis Layer Operating System Within CCMS, the primary transaction for operating system monitoring is ST06. Transaction ST06 reports the overall operating system status. See Figure 1. Key metrics such as CPU and SWAP utilization are captured. If further details about one particular metric is desired, click the “Detailed


SAPtips Journal

So you have SAP installed. Now what? So long as there is activity and change within the system, the Basis team will raise the sails and embark on their endless journey of system monitoring. Monitoring includes everything from space utilization in the database to the number of short dumps. If you start tallying up everything and anything that can go wrong in the system, this seemingly simple task becomes a bear of a chore. As you increase the number of systems under your responsibility, soon there will be no time to do anything other than monitoring. At this rate, you’ll never get back to port. Luckily, there’s some help out there. SAP and third-party vendors

SAPtips © 2005 Klee Associates, Inc.

Drill down into “Operating System” to see the MTEs associated with that tree. the “Operating System” node is actively monitoring those particular MTEs shown in Figure 4. expand the “SAP CCMS Monitor Templates” option. See Figure 2 for a detailed look at CPU utilization. Another way to look at this data is via the CCMS alert monitor. you will see “Operating System”. Under this tree. Figure 1: Operating System Monitoring (ST06) SAPtips Journal Figure 2: CPU Utilization Detail Figure 3: SAP Alert Monitoring Templates SAPtips. See Figure 3 for the standard SAP templates. Let’s pick “database buffer size” and drill down. See Figure 6. and green is OK. let’s examine the database and the available tools and metrics. See Figure 4 for the MTEs. The main transaction for database performance statistics is ST04. Similar to the operating system’s ST06. Here you will see SAP’s standard alert monitoring templates. An alert monitoring tree is a concatenation of individual Monitoring Tree Elements (MTE). In order to view the operating system monitors. yellow is a SAPtips © 2005 Klee Associates. See Figure 5. but with thresholds established to determine alert status. you can select the “Detailed Analysis Menu” button to drill down any one metric. . Go to transaction RZ20 to see the root level of the alert monitoring tree. Inc. Double-click on the word “Size” and you will get the size statistics for this database data buffer. Database Moving on. This is the same data as seen with transaction code ST06. The color legend is logically sequenced: red is critical. These MTE are individual items in the system that are to be monitored.SAPtips Journal Page 2 February/March 2005 Volume III Issue 1 Analysis Menu” and drill down further into the item you desire. What does this mean? In short.

com SAPtips © 2005 Klee Associates. Inc. .SAPtips Journal Page 3 February/March 2005 Volume III Issue 1 Figure 4: Operating System MTE Figure 5: Database Performance Analysis (ST04) SAPtips Journal Figure 6: Database Data Buffer Detail SAPtips.

except that we have different transaction codes and different MTEs. except that we have different transaction codes and different MTEs. Here is a list of the important ones: There are other transaction SAPtips © 2005 Klee Associates. Database specific MTEs are associated with the “Database” node. You can copy SAP’s templates and modify the thresholds based on your needs. and green is OK. the CCMS alert monitor. SAPtips Journal Figure 7: Database MTE The alternate way to view this is via transaction RZ20.SAPtips Journal Page 4 February/March 2005 Volume III Issue 1 There are additional transaction codes for the database. The Basis layer has more transaction codes. Let’s run through an example. see Figure 7. Inc. there are Basis specific MTEs in the CCMS alert monitor. However. but these are the main ones for Oracle database monitoring. The navigation is similar to the operating system. Transaction Code DB02 DB12 DB14 Description Database space Database backups Database operations log Monitoring the Basis metrics is the same as monitoring the operating system. This is the same data as seen with transaction code ST04. Similar to the database and operating system. for database alerts select “Database” under the “SAP CCMS Monitor Templates” root. Configuration There is some configuration you can include into the CCMS alert monitors. but with thresholds established to represent alert status. SAP Basis Layer Without being too repetitive. SAPtips. . monitoring the Basis metrics is the same as monitoring the operating system. From transaction code RZ20. The Basis layer has more transaction codes. select the “SAP CCMS Monitor Templates” option and select one of the listed sub-components. yellow is a warning. but these are the main ones for Oracle database monitoring. The alert legend is the same as before: red is critical. Here is a list of the important ones: There are other transaction codes.

emails are sent. To do this. 5. Select “CCMS_OnAlert_Email” and open for change. Select “Methods > Method overview” and select “Display Overview”. Next. Transaction Code SM21 ST02 ST03 ST22 SM50 SM66 SM12 SM37 SP12 SM50 SM66 SM12 SM13 SM20 SE01 SMGW SM58 SAP system logs SAP Buffers SAP Performance Short Dumps Work process overview Global work process overview Lock Entries Background jobs Spool requests Work process overview Global work process overview Lock Entries Update requests Security audit log Transport logs SAP Gateway monitor Transactional RFC monitor Description Figure 8: Copying a Template SAPtips Journal 2. From transaction code RZ20. drill down to the MTE.e. 5. edit the parameters: SENDER = Enter the “From SAP” username RECIPIENT = Enter the recipient’s email address (i. You can set CCMS monitoring as private or public. 6. See the following instructions to set up automatic emailing. select the newly created monitoring set and then select the Change icon. This means that when alerts occur. SAPtips © 2005 Klee Associates. 3. 7. Inc. Set up SAPCONNECT to enable external emailing. A useful feature in CCMS is the ability to set up automatic reaction via email. Make any necessary changes per your needs. ) RECIPIENT-TYPEID = Enter “U” for Internet address and “B” for SAPusername.doe@company. select the template that you want to copy. . Figure 9: Modify CCMS Monitoring Set SAPtips. To customize any of the thresholds. follow the menu “extras” > “Activate Maintenance Function”. See Figure 10 as an example of changing the syslog error MTE. see Figure 9. john. Select the “copy” icon and then enter the name of the new copy (see Figure 8) 4. Change any threshold values and save. On the Parameters tab. 2. Go to transaction RZ21. 1.SAPtips Journal Page 5 February/March 2005 Volume III Issue 1 1. Select properties of the MTE.

At one customer site. Jotech LLC. If I did not implement CCMS as my early warning mechanism. Everything from the operating system to the actual Basis SAPtips.Hirao@SAPtips. Joey is SAP Basis certified. for one reason or another. the “bad” code would not have been fixed until the bulk of users started using the system the following morning. Select properties of the MTE 9. I would not have had time to do anything other than system monitoring. The sooner you know of a potential SAPtips © 2005 Klee Associates. Subsequently. SAP has many functions that can malfunction. someone has to do it. This was when a fix to some custom code went into production with errors. Joey Hirao. As the Basis motto goes. It becomes one of my “required” post-installation steps. enter CMS_ OnAlert_Email in the “Autoreaction method” field Voila! Now you will receive alerts via email on that MTE. really stands out. I can cite many examples where the early warning mechanism really helped out. SAPtips Journal Conclusion System monitoring can be a boring task but. this produced a tremendous amount of sort dumps. Solaris Administrator certified. He designs. a day without calls is a day you’re doing your job. UNIX. . NT. Inc. One time. He is the founder of Jotech LLC. CCMS is something I always try to implement after installing a system. and the author of SAP R/3 Administration for Dummies. the better. layer is your responsibility. On the Methods tab. Joey has been working with SAP technology for the past six and an MCSE. Joey is a Basis consultant with expertise in SAP Basis. Luckily. in particular. hey. SAP provides you with tools that allow you to be proactive and preventative. ≈ Putting it all together The real value of using CCMS becomes evident when you “hear” of a problem before the users call you with a complaint. Save your changes 7.SAPtips Journal Page 6 February/March 2005 Volume III Issue 1 6. Early warning notification via pager and/or email truly cuts down on real user complaints. implements and maintains SAP systems for customers worldwide. If it were not for the late night pages. I ended up being the only Basis staff supporting a multitude of SAP systems. Go to the MTE for which you want to activate emailing 8. Joey’s email address is Joey. and database technologies.

Inc. and is owned by Klee Associates. Inc. Although we make every good faith effort to ensure accuracy. All other product names used herein are trademarks or registered trademarks of their respective owners. Inc. NO WARRANTY: This documentation is delivered as is. and Klee Associates. Any use of this documentation is at the risk of the user. SAP AG software referenced on this site is furnished under license agreements between SAP AG and its customers and can be used only within the terms of such agreements. reserves the right to make changes without prior notice. makes no warranty as to its accuracy or use. Page 7 SAPtips Journal SAPtips.SAPtips Journal February/March 2005 Volume III Issue 1 The information in our publications and on our Website is the copyrighted work of Klee SAPtips © 2005 Klee Associates. Inc. Inc. this document may include technical or other inaccuracies or typographical errors. and this publication are not affiliated with or endorsed by SAP AG. SAP AG and mySAP are registered trademarks of SAP AG. NO AFFILIATION: Klee Associates. Inc. Klee Associates. .