Skip to Content

What is GRMG

Generic Request and Message Generator (GRMG) can be used for technical monitoring and for application monitoring. GRMG is widely used to monitor all components in an application, based on ABAP or Java. In XI landscape GRMG can used to monitor the health of XI Java components.GRMG consists of two parts
+ 1. GRMG Infrastructure+ The GRMG Infrastructure is part of the monitoring architecture of the Computing Centre Monitoring System (CCMS). It communicates with GRMG application by sending GRMG requests, the application inturn responds with a GRMG response.This GRMG response is interpreted by the GRMG infrastructure and displayed in the alert monitoring tree.
+ 2. GRMG Application+
The GRMG application performs the actual availability monitoring.

Prerequisites of Using GRMG

Systems group “ExchangeInfrastructure_Systems” should have been created in the Central Monitoring System, containing all the systems in XI Landscape.

Configuring CCMS Monitoring for XI- Part I .

Why use GRMG

XI Integration Server consists of many Java components like
Integration Repository, Integration Directory, Runtime Workbench, System Landscape Directory, J2SE Adapter Engine and J2EE Adapter Engine. The

health of these individual java components is important for XI to successfully
process messages. By using GRMG we can activate heartbeat monitoring for these
java components.

How to Configure GRMG

The first step for configuring heart beat
monitoring for XI components requires creation of GRMG scenarios. As specified
before GRMG requests and responses are well formed XML messages. In fact GRMG
scenarios for the components are specified in XML templates. SAP Note 634771
provides a template SAP_XI30_GRMG_Cust_Template.txt consists of scenarios
which represent a component that can be
monitored by GRMG.



Upload the scenario using the Upload/Download button. You can either upload
scenario by scenario or upload the

template with all the scenarios.


Once you have uploaded the scenarios into GRMG, based on the scenarios
configured in the template, GRMG application will be filled

with GRMG scenarios as shown in the following figure.


Now create an RFC destination of type HTTP for each scenario in transaction SM59.

If the component is running on a J2EE Engine, enter G otherwise enter H  as
the type of RFC destination.

Use XIRWBUSER for logon credentials as recommended by SAP. Also make sure the path prefix of each component

is filled as specified in the above table


Once you have created an RFC Destination for each of the components, your
SM59 should look like the figure below.


Once RFC Destinations have been created for the GRMG scenarios, go back to
GRMG and start each of the scenarios.

Use the start/stop button for starting each scenario. If the GRMG scenario was successfully started,

it will be marked with a green tick. 


Having created GRMG Scenarios, and their corresponding RFC destinations, Call transaction RZ20 ,

Expand the monitor set SAP CCMS Monitor Templates, and start the Exchange Infrastructure monitor.

You can view the availability of the activated scenarios.



This web log introduces GRMG and how to configure heart beat monitoring of

Java components of XI using GRMG scenarios.

To report this post you need to login first.


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

    1. Former Member
      will u plz tell me how to see SAp notes?
      i seached in sap library.they have mentioned procedure to upload ,dowload etc.
      But i did not found any transaction to get SAP notes or see sap notes available
    1. Hi,

      Never got time to put in blog III. But here is how you can configure monitoring for Adapter Framework.

      Configuring CCMS Alerts for the Adapter Engine
      If processing of a message on the Adapter Engine fails, the message state is changed to faulty. To notify administrators immediately of such processing failures, they can be propagated as alerts to CCMS. As CCMS is the SAP standard interface to third-party monitoring tools, these failure events may also become visible in non-SAP monitoring tools.

      Configuration Steps

      To make use of Adapter Engine alerts, you must configure the connection to CCMS as follows:

      1. Make sure that the J2EE engine on which the Adapter Engine is running is configured to be monitored by the central CCMS system.

      To do so, execute transaction RZ20 on your central monitor server. There, the J2EE engine should be visible in the CCMS monitor under SAP J2EE Monitor Templates ® All Systems. If not, follow the steps described in the Supportability Setup Guide for SAP NetWeaver 04 on SAP Service Marketplace at ® Cross-NW.

      2. Check whether the Adapter Engine is configured to report errors to CCMS.

      To do so, start the Visual Administrator and select service SAP XI AF Core. The value of property CCMSEnabled must be set to true (in lower case letters). If it is not, change the property value to true and restart the service.

      To verify that the setting is effective, select the Visual Administrator Monitoring service. Under Root ® Applications, you should see a node for the Adapter Engine.


      1. Former Member
        Hi Naveen,
        I followed your blog and uploaded the GRMG Scenario. It is succesfull. But often the scenarios get deactivated(Grayed)and I have to manually start the scenarios.Any ideas on this issue.


      2. Former Member
        will u plz tell me how to see SAp notes?
        i seached in sap library.they have mentioned procedure to upload ,dowload etc.
        But i did not found any transaction to get SAP notes or see sap notes available

Leave a Reply