Checking Monitoring Availability
In the Solution Manager, CCMS Generic Request and Message Generator (GRMG) technology is used for the availability monitoring of various application types. This technology consists of the GRMG infrastructure and the GRMG application. The GRMG infrastructure is part of the Computing Center Management System (CCMS). It sends a text query to the GRMG application and receives a corresponding response; both the query and the response are messages in a defined XML format.
This Java monitoring infrastructure can also be used for the availability monitoring (heartbeat support) of Java WD applications. The following three checks can be executed for any local WD application or any WD DC application:
● Was the application deployed on the server?
● Was the application started successfully?
● Was the back-end connection established using RFC?
○ The system checks whether the back-end systems defined for this application can be reached. No connection is established, but instead the system executes an RFC ping. It is therefore not necessary to log on to the back-end system with a valid user.
To instrumentalize the WD application for the GRMG monitoring – that is, to supply the GRMG infrastructure with the application-relevant data – you must adapt the configuration template grmg-customizing.xml. This is done by entering the application URL in the configuration file. The template is part of the standard shipment of the Application Server. With the configuration tool; the NW Administrator tool is available for monitoring standalone Java WD applications.
Prerequisites
● Registration of the computers involved in the availability check with IP address in the internal network. The name of the host (value of the %Host% variable in the GRMG configuration file) must enable an unambiguous IP address resolution in the CCMS system.
● Installation of the CCMS agent
More
information:
Installing/Registering
the CCMS Agents for Experts.
Procedure
There is need that you adjust and upload the GRMG customizing file for every GRMG scenario. You first require a suitable GRMG customizing file, thus also for Web Dynpro applications. This file contains the information required for monitoring the application in the form of parameters. This information is read and processed by the GRMG infrastructure, which runs on the central monitoring system. To make use of the availability monitoring function, you must adjust the customizing file grmg-customizing.xml.
1. Assign the configuration file to the Web Dynpro application: Open the Navigator view in the Developer Studio and import grmg-customizing.xml into the Web Dynpro DC via context menu entry Import on the DC name). You can find the GRMG XML file in your file system (operating system Windows) in directory /saploc/prfclog/grmg of your Java engine installation.
2. Copy the XML file into the META-INF directory of the application project. This packs the configuration into the .ear file.
3. Execute the build and deployment for the Web Dynpro application in the Web Dynpro perspective of the Developer Studio and start the application.
4. Start the configuration tool which is part of the Java engine.
5. Make the following parameter adjustments in the GRMG customizing file:
a. Name of scenario
<scenname>WDADM630</scenname>
b. Name of application including vendor ID and name of development component
<scenstarturl>http://%HOST:%PORT/webdynpro/dispatcher/sap.com/tc~wd~tools/Explorer?sap.session.client=GrmgClient</scenstarturl>
6. Load the GRMG customizing into the CCMS.
Default Source Template of the GRMG Configuration File for a WD Application
The source template is delivered with the Web Dynpro Runtime and configures the heartbeat server for the Web Dynpro application. In this XML source code, you must make the relevant adjustments for the availability check of the current Web Dynpro application.
<?xml version="1.0" encoding="UTF-8"?>
<customizing>
<control>
<grmgruns>X</grmgruns>
<runlog></runlog>
<errorlog></errorlog>
</control>
<scenarios>
<scenario>
<scenname>WDADM630</scenname>
<scenversion></scenversion>
<sceninst>001</sceninst>
<scentype>URL</scentype>
<scenstarturl>http://%HOST:%PORT/webdynpro/dispatcher/
sap.com/tc~wd~tools/Explorer?sap.session.client
=GrmgClient</scenstarturl>
<scenstartmod>Unknown</scenstartmod>
<scentexts>
<scentext>
<scenlangu>E</scenlangu>
<scendesc>GRMG: Web Dynpro on %SID:%INST.</scendesc>
</scentext>
</scentexts>
<components>
<component>
<compname>WDDEPLOY</compname>
<compversion>001</compversion>
<comptype>Unknown</comptype>
<comptexts>
<comptext>
<complangu>E</complangu>
<compdesc>Web Dynpro Deploy</compdesc>
</comptext>
</comptexts>
<properties>
<property>
<propname>Unknown</propname>
<proptype>X</proptype>
<propvalue>Unknown</propvalue>
</property>
</properties>
</component>
<component>
<compname>WDSTATE</compname>
<compversion>001</compversion>
<comptype>Unknown</comptype>
<comptexts>
<comptext>
<complangu>E</complangu>
<compdesc>Web Dynpro Enablement and Start</compdesc>
</comptext>
</comptexts>
<properties>
<property>
<propname>Unknown</propname>
<proptype>X</proptype>
<propvalue>Unknown</propvalue>
</property>
</properties>
</component>
<component>
<compname>WDJRFC</compname>
<compversion>001</compversion>
<comptype>Unknown</comptype>
<comptexts>
<comptext>
<complangu>E</complangu>
<compdesc>Backend access using JRFC</compdesc>
</comptext>
</comptexts>
<properties>
<property>
<propname>Unknown</propname>
<proptype>X</proptype>
<propvalue>Unknown</propvalue>
</property>
</properties>
</component>
</components>
</scenario>
</scenarios>
</customizing>
Displaying Availability Data
The availability data is displayed in the heartbeat monitor of the CCMS. In the SAP system, start the transaction TZ20 and choose All Monitoring Contexts → SAP CCMS Technical Expert Monitors → SAP J2EE Monitor Templates → Heartbeat → Web Dynpro.
More Information
GRMG Monitoring (Monitoring Web Dynpro iViews in the Portal)