Monitoring the Monitoring Architecture

Use the Availability of Monitoring Architecture monitor to display information about the status of the monitoring architecture itself. This monitor contains availability and error messages for the most important tools in the context of the landscape-wide central monitoring.

Execution

Check the Availability of Monitoring Architecture monitor for alerts. To open the monitor, proceed as described in Tasks. Depending on the affected nodes, you can react to the alert as follows:

Affected MTE	Description
Availability CCMS Agents	This subtree contains availability information for the CCMS agents that are registered with CEN. These are both the SAPCCM4X and SAPCCMSR CCMS agents and the availability agent CCMSPING.
<Agent>.<Host>.<Instance number>	Check in the topology display of transaction RZ21 whether the corresponding agent is really no longer responding (see Monitoring CCMS Agents in the Topology Display). If the agent is not accessible, check its log file and restart the agent locally (see Controlling CCMS Agents).
Availability SAPOsCol	This subtree shows the status of all SAPOSCOL agents in the displayed system.
<instance name>	Check the SAPOSCOL log files and restart SAPOSCOL (Controlling SAPOSCOL from the Operating System).
Availability of Triggers, SAPMSSY8 and SAPMSSYT	This subtree groups information about programs and jobs that must be running for the monitoring architecture to function correctly.
<SysID>\CCMS_Selfmonitoring	This subtree contains information about those of the above programs and jobs that are only executed once system-wide (see CCMS Selfmonitoring Monitor for System-Wide Data).
SapmssyT	SAPMSSYT is a data collection method of the monitoring architecture, which runs once an hour as a job. Its tasks are primarily: Distributing the method assignments to MTE classes on remote systems in the context of the central auto-reaction; it also determines data for the self-monitoring of all CCMS agents. Controlling the CCMS agents, including transferring the GRMG Customizing data to CEN. You can find SAPMSSYT messages under Messages; SapmssyT_Runtime gives the runtime of the job.
Startuptools once per System	You can also have methods that run in the background started by the background dispatcher for startup methods (SAP_CCMS_STARTUP_TOOL_BATCH_DP), which runs the methods immediately after the start of an instance. Methods that are started by this dispatcher can set their own runtime and error messages in this subtree.
<SysID>\MoniInfra_<instance>	This subtree contains information about those of the above programs and jobs that are executed on every instance (see CCMS Selfmonitoring Monitor for Instance-Specific Data).
Sapmssy8	SAPMSSY8 runs every five minutes, starts the local method dispatcher for methods in dialog, and ensures that the properties and methods in the shared memory and the database are compared. If SAPMSSY8 is no longer running, start transaction RZ03 and choose Utilities Diagnosis Cyclic System Prog .
Tooldispatching (short running tasks)	The log attribute Messages of this subtree contains runtime messages from the local method dispatcher that starts the methods that are to run in dialog. Runtime and error messages of these methods are also displayed here. Note Problems with specific methods affect only specific MTEs. Most monitoring functions are not affected by method errors. End of the note.