Skip to Content

If you want to monitor the availability of technical components and entire business processes centrally, have a look at the Generic Request and Message Generator (GRMG). It is SAP’s standard tool for monitoring the availability of web components and Java applications, and it’s part of the Monitoring Infrastructure used in the NetWeaver Administrator and the Alert Monitor. For more information, see http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/504a550ae6274495e2ce30d176f33b/frameset.htm.

In this blog, I will show how to monitor the availability of the System Landscape Directory (SLD) with GRMG. Maybe you’ve already read my blog about “Availability Monitoring of HTML Pages with GRMG Lite” (https://weblogs.sdn.sap.com/pub/wlg/3989), where I used the SLD as an example, too. When reading that blog, maybe you thought: “If GRMG is SAP’s standard tool for availability monitoring of Java applications, why should I use GRMG Lite for monitoring the availability of this really crucial Java application? Doesn’t SAP offer a standard solution for that?”

Yes, we do – but for SAP NetWeaver 04, the request was that GRMG should only monitor the connection to the SLD server, not its run status. So you could stop the Object Server, and still receive a 100% availability, which is something that needs getting used to. But for SAP NetWeaver 2004s, things have changed – reason enough to introduce the GRMG monitoring of the SLD.

  1. As the first step, you require a template for the GRMG Customizing File. You can find this on the SAP Community Network using the following link: https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/20ece666-9996-2a10-de98-cf68c35f7dd1.

  2. Download the archive System Landscape Directory SLD GRMG Monitoring Template to a location to which you have read access from your front end, and decompress the archive.
  3. Open the contained file, Template_sld_grmg_cust.xml, with a suitable editor, and make the following changes:

    Save your changes.

    105.PNG

    • Change the value of the tag <scenstarturl> by replacing [host] and [port] with the relevant connection data for the SLD that you want to monitor.

    • Change the value of the <scendesc> by replacing [host] with the name of the host on which the SLD to be monitored is running.

  4. In the central monitoring system (CEN), call transaction GRMG. Choose the Upload button, and then select the above file, Template_sld_grmg_cust.xml.

    106.PNG

  5. Select the scenario that you have just created, J2EE_SLD, and choose Start. As of this point, the scenario is periodically executed.

    107.PNG

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

  6. Now start the Alert Monitor (transaction RZ20). You can find the results of the availability monitoring with GRMG in the Availability and Performance Overview monitor, monitor set SAP CCMS Monitor Templates. Expand the sub-tree GRMG-Tested Availability (Web Components). The SLD subtree is displayed.

    108.PNG

    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 System Landscape Directory that the application is available; this means that the GRMG application performed the availability tests with a positive result and sent back a corresponding GRMG response to the GRMG infrastructure in the CEN.

  7. Now, let’s check the monitoring. Stopp the SLD Server by choosing the Stop Server button.

    109.PNG

  8. Back in the Alert Monitor – the Self-Monitoring sub-tree is still green (because the availability check is still providing valid results), but the Availability went down to 0%, and an alert is raised.

    110.PNG

That’s it! Now the availability of the SLD is monitored in the central monitoring system.

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Daniel King

    For anyone trying this, do be aware the HTTP destination for the SLD GRMG heartbeat will return a 400 error response if you test it from SM59 or from your Web browser./sld/rtc  yields<br/><br/>400: “HTTP method GET is not supported by this URL”<br/><br/>This is perfectly normal.  GRMG is apparently using an HTTP POST mechanism, which is supported by the URL.  I was able to verify that with an HTTP client that could submit a POST request.

    (0) 

Leave a Reply