Prerequisites

Configuring the Monitoring Architecture

To be able to monitor your system landscape with the monitoring architecture, you need to have performed the configuration in the central monitoring system (CEN) and in the monitored components. The most important steps of this configuration are:

• The background dispatching and the central system dispatching in CEN must be active (see Activating and Deactivating Method Execution).

• Monitored systems must be declared as such to the monitoring architecture (see Registering SAP NetWeaver Components and Hosts in CEN).

• Monitored instances and hosts must be registered with CEN by using CCMS agents (see Registering SAP NetWeaver Components and Hosts in CEN).

• The operating system collector SAPOSCOL must be active on all monitored hosts of your IT landscape.

• Components for which there are instrumentations for monitoring with the GRMG must be appropriately configured (see GRMG Monitoring of SAP NetWeaver Components)

• If you require central availability monitoring of ABAP and Java systems and their instances, use the availability agent CCMSPING (Configuring Availability Monitoring with CCMSPING)

For more detailed information about this, see Configuring the Monitoring Architecture.

Adjusting the Templates for the Monitors

In the alert monitor, monitors group thematically connected monitoring data in a tree structure (see alert monitoring tree). The monitors of the SAP CCMS Technical Operations Templates set include the most important data for the regular monitoring of your system. This set was created specifically for administration tasks.

If you are using the SAP NetWeaver Administrator for the central monitoring of your system landscape, you can use these templates directly. Monitoring data is displayed for all systems that are in the associated System Landscape Directory (SLD) and that are identified as centrally monitoring by CEN.

If you use the Alert Monitor for the central monitoring of your system landscape, you need to adjust the monitor definitions for your IT landscape; the steps required to do this are described in the following procedure:

Adjusting Monitored Systems

In their delivery status, the monitors of the SAP CCMS Technical Operations Templates set show only nodes for the local system:

Modify the monitor definitions so that the values of all desired monitored systems are displayed.

1. Start the alert monitor by entering the transaction code RZ20, and activate the maintenance functions by choosing  Extras   Maintenance Functions On .

2. Copy the SAP CCMS Technical Operations monitor set by selecting the set, choosing Copy, and entering a name of your choice for your copy.

   Note

   You need to copy the set first, since you cannot change the delivered standard monitor set.

3. Expand your copy, select the desired monitor, and choose Change. The Edit Monitor Definition screen appears.

4. The definition consists of subtrees for different rules (see Rule Nodes: Rule Description and Use). Expand the subtrees and search for the rule CCMS_DEFINE_R3_SYSTEMS. This rule specifies the systems from which values are to be displayed in the monitor.

   Note

   The nodes for availability monitoring with CCMSPING and GRMG (see Availability Monitoring) always belong to CEN for technical reasons. Therefore, the rule CCMS_DEFINE_R3_SYSTEMS does not exist in these subtrees.

5. Select the rule and choose Change. On the next screen, Edit Rules Nodes, choose Continue >>.

6. In the Parameter Values group box, enter the desired systems as the value for the parameter R3System. You can enter the following values when doing so:

   Entry	Meaning
   <CURRENT>	Local system
   <ALL>	All systems that are known to the monitoring architecture as monitored systems
   <any name>	System group; you can define a system group yourself that contains the desired systems (see Maintaining System Groups)
   J2EE_Systems	System group containing all Java systems that are registered with CEN through CCMS agents

7. If you do not just want to display values fort he local system, you should activate the indicator Display virtual summary nodes in the monitor. This means that the values for each monitored system are displayed in a separate subtree.

8. Choose Continue >> and, after you have changed all relevant rule nodes, save the changed monitor definition. The monitor could now look like this, for example.

   

Adjusting Monitored Values

You can also extend the monitors to include other monitoring values or remove parts of the monitoring from the monitors. For more information about this, see Editing Monitors and Monitor Sets.

Setting Up Notifications for Alerts

If you want to be automatically informed about alerts in the above monitors, assign a notification as an auto-reaction method to the corresponding MTE classes. You do not then need to call the alert monitor to be informed about a possible alert. We recommend that you forward the alerts to Alert Management (ALM) for your notifications. ALM offers more communication channels and extended notification functions, such as representative rules, notification variants (for example, during the day by e-mail, during the night by SMS), subscription to alert topics, and escalation mechanisms. To forward CCMS alerts to Alert Management, you only need to copy, adjust, and assign the corresponding auto-reaction method. For detailed information, see

Configuring a Method for Forwarding Alerts to the ALM.

Note the following with regard to auto-reaction methods, however:

• By default, an auto-reaction method is always executed in the system in which the corresponding alert occurs. This also means that you need to perform the configuration of the method in each monitored system.

• An alternative is the central auto-reaction method. This means that the method is no longer executed in the local system, but rather in CEN. You therefore only need to make the required configuration settings in CEN (see Setting Up Central Auto-Reaction Methods).