Configuring the Caches of the Monitoring Architecture 

Use

The CCMS monitoring architecture uses various caches to improve its performance. The validity periods of these caches are stored in the table ALCACHECNF of the central monitoring system. If the relevant values are requested during the validity period of the cache, the query is met directly from the cache. This reduces the number of RFC calls required, which leads to an improved performance of the display in the alert monitor.

You can, however, use the buttons Refresh and Invalidate Data Cache (Control-F4) in the alert monitor, to force new collection of the values at any time (see Setting Up a Central Data Cache).

These validity periods are set by SAP a way that means that even if there are a large number of changes in your monitored IT landscape, you can quickly see all of these changes in the alert monitor. In very stable production environments, you can increase the validity periods of selected caches as you wish.

Since there is not maintenance interface for ALCACHECNF, you must perform the maintenance in the Data Browser (transaction SE16). There is an entry in the table for each individual cache, consisting of the technical name and the validity period in minutes.

The following caches exist in the monitoring architecture:

Technical Name	Validity in Minutes	Description
ALALERTX	1440 (1 day)	Cache for active alerts Since the alerts do not change until they are completed, it is useful to store a duplicate of an alert in the cache after it is read, and to meet the next read request from this cache.
ALCONSEG	5	Cache for routing If there are communication problems with monitored systems or CCMS agents, the system waits before its next connection attempt to avoid triggering unnecessary trace entries or timeouts. You set the wait time in this cache.
ALMBCADM	30	Cache for collected MTEs from MTE classes When processing rules, and in particular the rule GET_MTE_BY_CLASS, the system collects the MTEs of an MTE class using a broadcast mechanism. This information is expensive to collect, but relatively static, and is therefore stored in a cache. This cache therefore determines the period of time after which a newly started server is displayed in the alert monitor.
ALMBRADM	30	Cache for collected MTEs from MTE classes This cache is similar to ALMBCADM and is required when processing the rule CCMS_GET_MTE_BY_CLASS_AND_OPTIONS. This rule exists as of SAP Web AS 6.40.
CSMCENTOOL	1440 (1 day)	This value specifies the reorganization frequency of the store for central auto-reactions. Do not change this value; it is only used internally.
CSMSEGM	20	Cache for monitoring segments of monitored systems When processing rules, the system collects the monitoring segments of the monitored systems. This information is stored in a cache. This cache determines the period of time after which a newly started system is displayed in the alert monitor.
CSM_X_TABLES	15	Cache for monitoring contexts of monitored systems When processing rules, the system collects the monitoring contexts of the monitored systems. This information is stored in a cache. This cache determines the period of time after which a newly started system is displayed in the alert monitor.

Procedure

To change the validity period of one of the caches listed, proceed as follows:

       1.      Choose Overview ® Data Browser, or call transaction SE16.

       2.      The Data Browser: Initial Screen screen appears. Enter the table name ALCACHECNF, and confirm your entry.

       3.      The Data Browser: Table ALCACHECNF: Selection Screen appears. Choose Execute ().

       4.      The Data Browser: Table ALCACHECNF screen appears. To change one of the validity periods, select the relevant entry and choose the Change button (). In a very stable production environment, you can increase the validity periods of the following caches as you wish:

¡        ALMBCADM

¡        ALMBRADM

¡        CSMSEGM

¡        CSM_X_TABLES

       5.      Enter the desired validity period in minutes and save your entries.