GRMG Self-Monitoring Monitor in CCMS

Use this monitor to monitor the correct functioning and configuration of the Generic Request and Message Generator (GRMG). The monitor consists of two subtrees:

· You can display the status of each GRMG scenario. You can therefore check whether it was possible to perform an availability check correctly or not.

· You can have GRMG Customizing files automatically uploaded into the central monitoring system and started. The prerequisite for this is that the Customizing files are in a specific directory to which a CCMS agent has read authorization, and that the file follows a naming convention (see also SAPCCMSR.INI: Configuration File of the CCMS Agents). If GRMG Customizing files are automatically uploaded, information about the relevant CCMS agent is displayed in this subtree.

If you have set the parameter TRACE = X in the data collection method GRMG_TRIGGER, messages of the method (such as start of scenarios, scenario errors, newly uploaded scenarios…) are also written to the data supplier log. You can find this log in the CCMS Selfmonitoring Monitor, in the subtree MoniInfra_ ®DataSupplier ® Log.

Prerequisites

You have performed the customizing of the GRMG monitoring.

Activities

To display this GRMG self-monitoring data, follow the procedure below:

1. Choose CCMS ® Control/Monitoring ® Alert Monitor, or call transaction RZ20.

2. Open the SAP CCMS Technical Expert Monitors monitor set, and start the GRMG Selfmonitoring monitor.

The status of the GRMG scenarios is also displayed in the normal monitor for availability monitoring. This is the monitor Availability and Performance Overview of the monitor set SAP CCMS Monitor Templates (see Displaying the Availability Monitoring with the GRMG in the Alert Monitor).

Features

Scenario Execution Subtree

You can see here whether the GRMG application was available and returned a valid response. You can obtain the following information from the subtree for a scenario:

· If the subtree is green, the GRMG application was available and returned a valid response. The availability of the component is displayed in the normal associated subtree (see Displaying the Availability Monitoring with the GRMG in the Alert Monitor).

· If the subtree is red, the monitoring architecture could not execute the scenario. In this case, a corresponding error message is displayed in the Run Status/Error Messages monitoring attribute in the subtree.

To obtain additional information about possible errors, select the monitoring attribute Run Status/Error Messages, and choose Display Details. If possible, HTTP headers including return codes and status reasons are displayed.

Note that if a scenario error occurs, the normal subtree is no longer provided with data and the associated values will become obsolete. A scenario error does not necessarily mean that the monitored component is not available.

The following scenario errors can occur, and are listed below with their most probable causes:

HTTP_POST Errors

The error description contains the prefix Reason for HTTP POST Failure.

Error Description	Possible Cause
· HTTP communication failure · Connect failed · Timeout occurred	· The URL specified in Customizing points to a host or port that does not exist. Check that the URL is correct, and whether the application that listens at the port is running. · The HTTP server for the URL is not running. In this case, start the server. Note that the monitored components that are running on the same server will also not be available in this case.
· TCPIP error occurred · Data error occurred	There are problems in the network configuration or the network operation.
· Internal error occurred	There are problems in the HTTP service of the monitoring system; check the status of the service with transaction SMICM.
· System failure occurred	There are problems with the HTTP server that is specified in the URL of the scenario.
· Argument not found · Plugin not active · Internal error · HTTP invalid state	There are problems in the HTTP client functions of the central monitoring system; check the status of your HTTP operation with transaction SMICM.
· Destination not found · Not authorized to use HTTP destination	There are problems with the RFC connection of type HTTP (which you specified in Customizing instead of a URL); the connection does not exist, or the required authorizations for its use are missing.

Scenario Errors

The error description contains the prefix Reason for scenario failure.

Error Description	Cause
· No message returned	This scenario error often occurs, if the response from the URL to the GRMG request is an HTML document rather than an XML document. The XML parser cannot return a specific error message in this case. This is usually because the GRMG application specified in the URL does not exist on the specified host. The Web server returns an HTML page Page not found or another non-XML page, which the parser cannot interpret. You should therefore check that the GRMG application is correctly installed on the target host and is operating correctly.
· No response for any component in request · >	This error message can occur if the response of a GRMG application does not return a status for any of the components specified in the GRMG request. Check whether the components in the GRMG Customizing file match those that are monitored by the GRMG application. You can also compare the GRMG request and the GRMG response directly by temporarily activating the trace (level 3) on the central server of the monitoring system in transaction SMICM.
· Any message about an invalid XML format · >	This error message occurs if there are formal DTD errors, such as tags that are not closed. You can check GRMG response directly by temporarily activating the trace (level 3) on the central server of the monitoring system in transaction SMICM.
· Any message about the CCMS monitoring architecture, such as Invalid TID or Wrong segment	There are problems with the CCMS monitoring architecture. Check the CCMS Selfmonitoring monitor for other alerts, and ensure that you have started the monitoring with the GRMG only on the central server of the monitoring system.

Customizing File Pickup Subtree

This subtree displays information about the automatic uploading of GRMG Customizing files. In general, these files are automatically uploaded to the central monitoring system and the associated GRMG scenario is started if the Customizing file is in the directory and has the prefix :

MTE Name (MTE Class)	Meaning
Upload Log (GRMG_UPLOAD_LOG)	Log for automatic uploading of Customizing files
Upload Agent (GRMG_UPLOAD_AGENT_NAME)	CCMS agent that loads the files of the directory below into the central monitoring system
Last data supplier run (GRMG_UPLOAD_DSRUN)	Last run of the data collection method that loads the Customizing files into the central monitoring system; by default, this is done once an hour If you want to start the data collection method immediately, use transaction SE38 on the central instance to run the program SAPMSSYT.
Upload Directory (GRMG_UPLOAD_DIRECTORY_NAME)	Directory in which the system searched for the Customizing file that the above CCMS agent loaded into the central monitoring system.
File specification (GRMG_UPLOAD_DIRECTORY_NAME)	Naming convention that the Customizing file must follow for the above CCMS agent to upload it into the central monitoring system.
Most recent file timestamp (GRMG_UPLOAD_FILE_TIMESTAMP)	Timestamp of the last change to the GRMG Customizing file that was uploaded to the central monitoring system using this agent

Monitoring with the Generic Request and Message Generator start page