Show TOC

Procedure documentationExecuting GRMG Scenarios in the Background Locate this document in the navigation structure

 

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.01, 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.

Note Note

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   GRMG_Self-Monitoring   Resets and Execution Reliability  .

As of SAP NetWeaver 7.01, 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.

End of the note.

Procedure

  1. Call transaction GRMG. The Generic Request and Message Generator screen appears.

  2. Choose the button   Start/Stop   Execute GRMG in Background  .

  3. You can now make the following entries on the Parameters for GRMG Background Job CCMS_GRMG_BATCH_EXECUTION screen:

    Input Field

    Meaning

    Name of the GRMG Job

    Name of the job that the GRMG scenarios call. Do not change the existing value.

    Frequency in Minutes

    Time between two executions of the GRMG availability monitoring. The smaller the value you choose here, the faster you will be informed in the monitoring infrastructure if a monitored component is no longer available.

    Note Note

    Experience has shown that you should not set this period to less than three minutes.

    End of the note.

    Number of Parallel Tasks

    You can perform the availability monitoring in parallel by setting a value greater than one in this field. This is primarily useful if you want to monitor a very large number of GRMG scenarios with a high frequency. We recommend that you set this parameter, if the runtime of the jobs CCMS_GRMG_BATCH_EXECUTION is longer than the period between two executions of the job, which you set in the parameter Frequency in Minutes.

    Note Note

    To determine the runtime of the job, call transaction SM37 and, in the Job Name field, enter CMS_GRMG_BATCH_EXECUTION. In the User Name field, enter the wildcard character * and choose the Execute (Execute) button.

    End of the note.

    Parallel Server Groups

    If you have the execution of the availability monitoring performed in parallel, you can restrict the instances on which the availability monitoring is executed by entering a corresponding server group here (more information: Defining RFC Groups for Parallel Processing Jobs). If you are using a central monitoring system that is used exclusively for monitoring your system landscape, do not enter anything here, even if you are using parallel processing.

More Information

Monitoring with the Generic Request and Message Generator start page