Start of Content Area

Function documentation Additional Settings for Availability Monitoring with the GRMG  Locate the document in its SAP Library structure

Use

Configure and start the availability monitoring of applications in transaction GRMG. The normal steps for doing this are described in the process Activating and Customizing Monitoring with the GRMG.

The transaction also provides additional functions for editing GRMG scenarios and adjusting the GRMG availability monitoring, which are described here:

The following information is displayed for each scenario in the table of GRMG scenarios that have been uploaded into the central monitoring system:

      Scenario Execution Status; this column specifies whether the scenario was successfully executed, and therefore an availability check could be performed:

      Name of the scenario; this name is used as part of the names of the MTE classes in the GRMG nodes for the scenario in the alert monitor.

      Version and instance of the scenario; differentiates between multiple scenarios with identical technical names (for more information about this, see Creating a Template for the Customizing File)

      Description of the scenario; the scenario is displayed under this name in the Alert Monitor

      URL/RFC Destination of the scenario that is called for the actual availability check

Features

First call transaction GRMG in your central monitoring system.

Note

For a description of the basic functions, see:

      Activating and deactivating execution

To stop the execution of selected scenarios, choose This graphic is explained in the accompanying text Start/Stop Deactivate Execution. To reactivate the execution of a stopped scenario, choose This graphic is explained in the accompanying text Start/Stop Activate Execution.

Use this function, if you want to temporarily pause a scenario; this can be the case, for example, if it is causing problems, or is temporarily not required.

      Scheduling monitoring pauses

You can deactivate the availability monitoring for selected periods, for example, during the weekend or during maintenance work. You can also repeat these monitoring pauses daily or weekly. You have two options for scheduling monitoring pauses:

       You can schedule monitoring pauses independently for each selected scenario. To do this, choose This graphic is explained in the accompanying text Pauses Schedule Monitoring Pause.

       You can schedule identical monitoring pauses for all selected scenarios. To do this, choose This graphic is explained in the accompanying text Pauses Uniform Monitoring Pause.

Defining monitoring pauses works in the same way as a corresponding function in the context of availability monitoring with CCMSPING. This is described in Creating and Changing a Monitoring Pause.

      Copying a scenario

To copy a scenario, choose the button This graphic is explained in the accompanying text Edit/Delete Copy Scenario.

Note

You can copy both GRMG Lite and GRMG scenarios; however, it is only meaningful for GRMG scenarios. This is due to the fact that the copy does not allow any changes to the components of a scenario, which is usually necessary for GRMG Lite scenarios with their scenario-specific component descriptions.

      Deleting a scenario

To delete selected scenarios, choose the button This graphic is explained in the accompanying text Edit/Delete Delete Scenario. The monitoring trees in the Alert Monitor that belong to the deleted scenarios are also deleted.

      Downloading GRMG Scenarios from the System to the Front End

You can download the Customizing file for a GRMG scenario to your front end at any time. To do this, select the relevant scenario, and choose This graphic is explained in the accompanying text Upload/Download Download Scenarios. The system displays the file name and the path of the file.

Note

Note that passwords (property type PW) are not downloaded.

      Checking CCMS agents for new scenarios

GRMG Customizing files with the prefix GRMG_, which are in the directory [Drive]:\usr\sap\prfclog\grmg (Microsoft Windows) or /usr/sap/tmp/grmg (UNIX) on a host with a running CCMS agent , are automatically loaded into the central monitoring system and started. This automatic process can last up to an hour, since it is dependent on the running of the program SAPMSSYT, which is started once an hour. To see the results immediately, choose This graphic is explained in the accompanying text Upload/Download Poll Agents for new scenario.

      Updating the Display

To update the display for the GRMG scenarios for availability monitoring, choose This graphic is explained in the accompanying text Start/Stop Update Execution Status.

      Displaying status messages

If a GRMG scenario could not be successfully started (scenario execution status This graphic is explained in the accompanying text), you can display the relevant error message by selecting the desired GRMG scenario and choosing This graphic is explained in the accompanying text Start/Stop Display Status Messages. For a description of the possible error messages, see GRMG Self-Monitoring Monitor.

Note

To display additional information about an error, start the GRMG Selfmonitoring Monitor in the Alert Monitor.

      Calling utilities

For GRMG troubleshooting, choose the This graphic is explained in the accompanying text Utilities button. The following functions are available to you there:

       Choose Display ICM Log to display the local log for the Internet Communication Manager. The log contains information about connection errors and problems when creating or executing HTTP sessions.

Note

To fully utilize the possibilities of the ICM log, set the ICM trace. To do this, start the ICM monitor (transaction SMICM) on the application server on which you are working, and set the trace to the value 3 (Goto Trace Level Set). Execute the scenario that you want to analyze in transaction GRMG, and then display the ICM log. You then also see the message bodies that are exchanged with GRMG. Do not forget to reset the ICM trace to the standard value.

       Choose Ping Target Host to perform a connection test to the host that is specified in the URL of the selected scenario.

       Choose Trace Route to Target Host to execute the command TRACEROUTE (or TRACERT in Microsoft Windows). You can use it to check whether the host from the URL of the scenario is accessible through the network from the application server on which you are logged on to.

This graphic is explained in the accompanying text Monitoring with the Generic Request and Message Generator start page

 

End of Content Area