Show TOC

 Structure of the GRMG ResponseLocate this document in the navigation structure


A GRMG response is an XML document that is sent from a GRMG application to the GRMG infrastructure. It contains the following data:

  • Information about the scenario, in which monitoring is being performed with the GRMG
  • Information about the components that are monitored with the GRMG
  • Message(s) that contain information about the availability of the monitored components

The GRMG response is generated by the GRMG application using the GRMG Java classes or with the ABAP standard classes (see Principle of Creating a GRMG Application).


After all monitoring functions that the GRMG application has to perform after receiving the GRMG request have been performed, the GRMG application creates an XML document that combines the results of these tests, and sends this GRMG response back to the GRMG infrastructure. The GRMG infrastructure interprets this response and displays it in a monitoring tree of the alert monitor.


The GRMG response has the following structure (in the following GRMG response, the data types of the individual tags are specified in square brackets [ ]):

<?xml version="1.0" encoding="UTF-8"?><scenario>  <scenname> [CHAR(8)] </scenname>  <scenversion> [CHAR(3)] </scenversion>  <sceninst> [CHAR(3)] </sceninst>  <component>    <compname> [CHAR(8)] </compname>    <compversion> [CHAR(3)] </compversion>    <comphost> [CHAR(15)] </comphost>    <compinst> [CHAR(2)] </compinst>    <messages>      <message>        <messalert> [CHAR(8)] </messalert>        <messseverity> [CHAR(3)] </messseverity>         <messarea> [CHAR(20)] </messarea>        <messnumber> [CHAR(3)] </messnumber>         <messparam1> [CHAR(120)] </messparam1>        <messparam2> [CHAR(120)] </messparam2>        <messparam3> [CHAR(120)] </messparam3>        <messparam4> [CHAR(120)] </messparam4>        <messtext> [CHAR(50)] </messtext>      </message>      ..    </messages>  </component>  ..</scenario> 

The values of the following tags are copied from the GRMG request, and have the following meanings:

Tag Name Description


Tag for grouping a scenario


Technical name of the GRMG scenario


Version of the GRMG scenario (> 0)


Instance of the GRMG scenario (> 0)


Tag for grouping a component


Technical name of the monitored component


Version of the monitored component (> 0)

The values of the following tags must be set in the GRMG application, and have the following meanings:

Tag Name Description


Name of the host on which the monitored component is running


Reference number of the monitored instance on which the component is running; this value is not set in the GRMG request, but rather determined by the GRMG application


When programming a GRMG application, ensure that you set this value correctly. If the value is not set, it is set to Unknown by the GRMG infrastructure, and this value is displayed in the monitoring architecture. The availability values are also not supplied. In the case of one instance, set the value to 001.

In the case of multiple identical components on different instances (such as the J2EE Engine) on a host, you can ensure that each component can be uniquely addressed using different compinst values.


Tag for grouping messages


Tag for grouping an individual message


Result of the message; two values are supported:

OKAY: Associated messages are displayed in the color Green in the monitoring architecture

ERROR: Associated messages generate a red alert in the monitoring architecture


Severity of an alert: a numerical value between 000 and 255, with which alerts of the same color are prioritized. The larger this number is, the more important the corresponding alert; in the alert monitoring tree, if there are multiple alerts with the same color, the alert with the larger severity is propagated upward. The default for the severity of an alert in the monitoring architecture is 50.


Message class of an SAP T100 message that is transferred to the monitoring architecture; if the corresponding message does not exist in the central monitoring system, the message in messtext is displayed


Message number of an SAP T100 message that is transferred to the monitoring architecture; messnumber is a number between 000 and 999


Parameter 1 of an SAP T100 message, if this is specified


Parameter 2 of an SAP T100 message, if this is specified


Parameter 3 of an SAP T100 message, if this is specified


Parameter 4 of an SAP T100 message, if this is specified


Message Text

Always return a value for this element. If you transfer both an SAP T100 message and a message text, this message is only displayed in the GRMG infrastructure if the corresponding SAP T100 message does not exist.


You therefore have two possibilities for transferring messages:

You specify a message class and a message number for which a message is defined in the SAP Web AS system

You specify a static message text

We recommend that you use ABAP messages.

 Monitoring with the Generic Request and Message Generator start page