SAP APO liveCache Monitoring

 

External Heartbeat

The collector uses an external program (DBMCLI) to periodically check if an SAP instance is able to access liveCache. A red alert is generated when a failure occurs.

Heartbeat

liveCache can have a number of statuses. liveCache is working properly when it has a status of "WARM." By default, the status is checked every 5 minutes; however, this value is userdefinable. A red alert is generated if any other status then "WARM" is detected.

System Error Messages

At user-definable intervals (the default is every 5 minutes), the collector reads the System Error Message log file. Every error message is reported as a red alert. A customization table is used to suppress notification of specific error messages and/or to modify how error messages are evaluated.

 

Synchronous BAPI Logging & Archive Logging

A customization table is used to set the logging level ("liveCache logging switched off," "synchronous logging turned on") and the archive logging (ON/OFF) for each client. A red alert is generated as soon as the actual value deviates from the default.

Connection to liveCache

The connection to liveCache is checked according to the specified interval. In addition to the connection tests, the system also checks if the appropriate entries for LDA (primary connection for multi-connect) and LCA (secondary connection) are present in the DBCON table.

OMS Data Cache, Converter Cache

The Object Management System (OMS) stores and manages the business objects. The data blocks are stored in cache for rapid access, and the references to the physical blocks are stored in the SYSTEMDEVSAPCE. Storing the references in the so-called converted cache enables them to be accessed more quickly. After each run, the collector reports the actual OMS data cache usage values and hit ratio as well as the hit ratio for the converter cache.

These values can be used for creating a performance graphic.

 

Status Checks

The collector periodically checks the status of:



Database Full YES/NO



Diagnosis Monitoring ON/OFF



Monitoring ON/OFF



Vtrace ON/OFF

A red alert is generated as soon as the actual value deviates from the default, which is black and bold.

 

Initialization Log File

The initialization log file is refreshed every time liveCache is started and initialized. The collector searches the last log file for errors. The strings that the collector searches for in the log file are defined in a customization table. The "*" (asterisk) wildcard can be used in the string definitions. The alert threshold can be determined at the string level.

 

Functional Check / Simulation

A report is used to check liveCache's function ability. Test data is written to and read and deleted from the LC. A red alert is generated if an error occurs during the simulation. The last erroneous log file is always saved so that analyses can be performed at a later stage.

COM Routines

Application functions are implemented in liveCache as C++/COM routines. These functions enable the objects to be modified directly in memory.

Trace Level

The collector checks if at least one trace level is active. A red alert is generated when an active trace level is found.

Runtime (COM routines)

A COM routine's average runtime can provide an indication of the system's utilization. A customization table is used to define a COM routine's average response time. A red alert is generated when a defined response time is exceeded.