By default, GRMG availability monitoring runs in dialog, which means, especially if you are using a large number of GRMG scenarios (as of about 50), that there is a danger that the runtime of the corresponding data collection method GRMG_TRIGGER becoming too long (more information: Changing the Timeout of the HTTP Connection of the GRMG Request). As of SAP NetWeaver 7.0 EHP1, you can have the processing of the GRMG scenarios run in the background, meaning that you can avoid the problems due to the maximum runtime being exceeded.
You can identify the exceeding of the maximum runtime in dialog by the generation of an alert in the corresponding instance-specific subtree of the CCMS Selfmonitoring monitor, in the subtree .
As of SAP NetWeaver 7.0 EHP1, the exceeding of the maximum runtime no longer leads to the permanent failing of the GRMG availability monitoring, since the nodes in the alert monitor that have the status FATAL ERROR due to the exceeding of the maximum runtime are automatically reset by the start-up method GRMG_RESET_TOOL. However, to avoid the maximum runtime being exceeded, you should run the availability monitoring in the background, if the above alerts exist.
Monitoring with the Generic Request and Message Generator start page