Skip to Content
Author's profile photo Dirk Jenrich

Availability Monitoring of HTML Pages with GRMG Lite

Do you want to monitor the availability and the content of URLs centrally? Then why not using the CCMS Monitoring Infrastructure? As of SAP NetWeaver 04 SPS 05, you can monitor a URL by creating a GRMG Lite scenario.

To create a GRMG Lite scenario, you need to enter a complete URL. You do not need to maintain any property values unless authentication is required. And you do not need to implement a GRMG application to use this function check, instead, GRMG Lite uses standard capabilities of the HTTP protocol.

As an example, you want to monitor the availability of the Object Server within the SLD. An SLD is a Java server application with which a client application communicates entirely using HTTP. The SLD server contains component information, system landscape descriptions, and a name reservation that are based on the Common Information Model (CIM) standard.

This is quite an advanced example, because using the URL, you need to authenticate yourself. And to check whether the Object Server is running, you have to check the content of the web page for the word Running. But… no pain, no gain.

  1. You call an SLD using http://<server>:<port>/sld; when you do so, you need to authenticate yourself.

    You can determine whether the Object Server is running in the Administration area:


  2. Now you know the URL to be monitored. So, in the central monitoring system CEN, you start transaction GRMG and create a GRMG Lite scenario.

    You now enter the names and descriptions of the scenario and its component (use any name you like). GRMG Lite is grouped by scenarios, where each scenario can contain different components. The results of the availability monitoring are displayed as a separate subtree in the Alert Monitor.


    Apply your entries by pressing the Create button.

    The names, which can be a maximum of eight characters long, become part of the MTE class name of the nodes in the Alert Monitor.

    The descriptions determine the node names of the subtrees in the Alert Monitor; they must be unique.

    Leave the Version input field blank.

3. Now enter the URL that you want to monitor.


4. For a URL without authentication or content check, you would be done. But you’re digging deeper, so you will enter some editable properties.

Property name Meaning
USE_BASIC_AUTHENTICATION type X if you want to authenticate yourself with a user name and password
LOGON_USER user name
LOGON_PASSWORD password of the user above; you should set the property type to PW so that the password is stored in encrypted format in the secure storage, is displayed with asterisks, and is protected by other security measures

\ In NW04 you need to maintain a password with property type PW in client 000, otherwise the CCMS dispatcher won’t be able to read it.

1. Scroll down in the list of editable properties. Now you want to set the properties necessary for checking the content of the page.


Property name Meaning
GET_OR_HEAD type GET if you want to monitor not only the header data, but also the content of an HTML page
CHECK_STRING_1 enter the desired character string; here you expect Running. An alert is to be generated if the character string does not appear in the page.
CHECK_STRING_2 here, you want to monitor the page for another character string, Stopped. However, in this case, an alert is to be displayed if the character string appears in the page. You can do this by placing an exclamation point ! in front of the character string.

To save the scenario, choose the Save button.

You have created the scenario. To start the scenario, select it, and choose the Start button.


You can see from the icon in the Run column that the scenario has been successfully run. This does not necessarily mean that the checked page is available. It just means that the check itself was successfully performed.

Now start the Alert Monitor (transaction RZ20). You can find the results of the availability monitoring with GRMG Lite in the Availability and Performance Overview monitor, monitor set SAP CCMS Monitor Templates.

The Availability SLD subtree is displayed.


You can see that the subtree consists of two parts:

  • A subtree for the self-monitoring of the scenario. This part shows whether the availability check itself was performed successfully.

  • A subtree for each monitored component. You can see from the color of the node Availability that the web page is available; this means that the HTTP return code is ok or redirect. Besides, the string Stopped was not found in the page.

  1. Now, let’s check the monitoring. Stopp the Object Server on the monitored URL by choosing the Stop Server button.


  2. Back in the Alert Monitor, the Availability still is 100% (because the HTTP code is still ok), but the string Stopped is found in the page, so a red alert is raised.


That’s it! Now the availability of the SLD is monitored in the central monitoring system; Moreover, the status of the Object Server is checked via the content of the web page.

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member
      Hi Dirk,
      I have customized several GRMG-lite scenarios. They all work fine, except in one point: I configure a periodical monitoring pause (e.g. overnight due to server-reboot) AND a Heartbeat-Alert, because I have to get aware that the data supplier does not run properly.
      In this situation, I get a heartbeat-Alert every night when the monitoring pause has begun. This is very disappointing. Do you have any idea how to suppress the Heartbeat-Alert?
      Thanks in advance.
      Author's profile photo Former Member
      Former Member

      The monitoring pauses suppress only the execution of the GRMG monitoring scenarios so that no GRMG availability alert is triggered when a monitored system is down. The pauses do this by preventing GRMG from supplying any data to the affected MTEs.

      The CCMS has unfortunately never had a mechanism (other than deactivation of an MTE) for suppressing alerts at their source - in the kernel at the time of evaluation of new data/the condition of an MTE in the CCMS shared memory segment. 

      That means, unfortunately, that the monitoring pauses don't affect the generation of 'heartbeat' alerts, which occur when 'paused' GRMG MTEs become inactive.

      I don't have any very good workaround for this inconsistency to recommend to you at this point. Either one removes the heartbeat alerts so that monitoring pauses do not trigger them. Or one uses an 'organizational' workaround to ignore heartbeat alerts that occur during customary downtimes.

      Regards, Stephen Pfeiffer

      Author's profile photo Former Member
      Former Member
      Dear Jenrich,

      your blog is very useful. Thanks to your "how to" on GRMG Lite we can now monitor URL  on CCMS. Associate whith auto-reaction method and email it become a powerful tool for administrators.

      But, I have a question:
      How to monitor several strings on the same URL:

      For example:

      Status is OK if the strings "running" or "define" are in the page.
      But if the both values are absent status is KO.

      How can I put this combination in GRMG Lite?

      Many thanks & regards,
      Emmanuel COINDRE