Skip to Content

If you are using the CCMS Monitoring Infrastructure for centrally monitoring your SAP system landscape, then you surely will remember your first experiences using the Alert Monitor. It was probably not love at first sight, and one of the reasons for that is the sheer number of monitor templates and nodes which are presented by transaction RZ20. “Good heavens! I know 10 percent of the MTEs at most! do I have to monitor them all?”.

No, you don’t have to. Remember, the predefined monitors for the Alert Monitor are templates – a showcase what you can monitor using your Alert Monitor. For sure, your next question will be “But what are the most crucial nodes?”.

Difficult question. Ask 10 different seasoned administrators, and you’ll get 11 different answers. But ask long enough, and you’ll see some patterns in the answers, some nodes that almost everybody monitors in everyday life. And these nodes we’ve integrated in the monitor set SAP CCMS Technical Operation Templates. The monitors in this set contain a selection of the most important messages and performance values for both Java and ABAP systems. Use each of them to monitor one aspect of your landscape:

  • Availability
  • Availability of Monitoring Architecture
  • ABAP Critical Messages
  • ABAP Key Performance Indicators
  • Java Critical Messages
  • Java Key Performance Indicators
  • Space Management

For all these monitors, you’ll find detailed documentation if you follow this link: http://help.sap.com/saphelp_nw2004s/helpdata/en/e2/7d104202795a33e10000000a155106/frameset.htm.

What do you have to do to use these monitors for monitoring your system landscape?

Remark:

I assume that you’ve already finished the setup of your central monitoring infrastructure. If not, follow the steps in the Monitoring Setup Guide (https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9d634e46-0a01-0010-6fa1-df3d51ca593b).

Remember, the monitors are templates. But with the name of the set starting with SAP, the monitors of the set are write-protected. If you want to edit them, first copy the monitor set:

  1. Start transaction RZ20, and activate the maintenance functions by choosing Extras –> Activate Maintenance Functions.

    pic3 (1).PNG

    2. To copy a monitor set, select it, and choose Monitor (set) –> Copy; on the Copy Monitor Set screen, enter a name for the copy of the set.

pic4 (1).PNG

Now you can change your copy of the monitor definitions. But what precisely you have to do? One thing is that the ABAP monitors are by default only monitoring the local system. If you want to monitor remote systems, you have to change the monitor definition. To do so:

  1. Expand the monitor set and select the monitor that you want to change. Choose Monitor (set) –> Change. All the monitor definitons of the ABAP monitors contain a root node CCMS_DEFINE_R3_SYSTEMS with a parameter R3System = :

    pic1 (1).PNG

  2. When doing central monitoring, you don’t want to monitor just your local system, so change that parameter to  or any system group that contains the desired systems. To do so, mark the node, and choose the Change Nodes icon. Choose Continue >> and change the value of the parameter R3System:
    pic2 (1).PNG

    Choose Continue >> again, and save your monitor definition.

    Remark:

    To create a system group, call transaction RZ21, choose Technical Infrastructure –> Configure Central System –> Maintain System Groups. From the Maintain Groups dropdown listbox, choose Create System Group.

The steps for changing the displayed systems are only necessary for the monitor definitions of the following monitors:

  • ABAP Critical Messages
  • ABAP Key Performance Indicators
  • Space Management

Why? The Java monitor definitions already show all systems of the system group J2EE_SYSTEMS. A Java system is added to that group whenever a CCMS agent monitoring that system is registered at the central monitoring system CEN. And when it comes to availability monitoring: These nodes reside (technically speaking) in the CEN, so there’s no need to change R3System = there.

As a rule of thumb you can say that in all monitor definitions in which it makes sense to change the systems displayed in that monitor, there is a root node CCMS_DEFINE_R3_SYSTEMS with a parameter R3System = , so it’s easy for you to change the definition. If that node doesn’t exist, then it usually does not make sense to change it.

You can do further changes on the monitor definitions, e.g. inserting new nodes or deleting existing nodes. For more information about creating and editing monitor definitions, follow these links:

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply