Availability Monitoring
(Heartbeats)
One monitoring technique in SAP Enterprise Portal is availability monitoring of system components by the CCMS. Using the SAP Solution Manager, a message is displayed in the CCMS for the status of these components. There is a periodic availability check.

Currently the availability of J2EE Engine clusters can be monitored by URL connections and by SAP backend systems.
In the SAP Solution Manager, SAP CCMS Generic Request and Message Generator (GRMG) technology is used to monitor the availability of portal components. It has two parts: the GRMG infrastructure and the GRMG application.
The GRMG infrastructure is part of the CCMS. It sends a test query to the GRMG application and receives an appropriate reply from it. Communications are coded based on the Secure Sockets Layer (SSL) protocol.
For more information about availability monitoring, see the document Customizing and Operation of GRMG Scenarios at service.sap.com/monitoring → Monitoring in Detail.
For more information about the SAP Solution Manager visit service.sap.com/solutionmanager or see the SAP Solution Manager.
The SAP J2EE Engine
must be set up for SSL to communicate the GRMG infrastructure and GRMG
application. The server certificate must also have been imported into the
monitored backend systems.
You must adjust the settings for your specific GRMG scenario and then load
these settings into the CCMS system. In the XML Customizing file you define
the components for which availability and special conditions should be
monitored.
For more
information about the configuration, see
Configuration of the
Monitoring Architecture.
The GRMG
infrastructure is part of the
Computing Center
Management System (CCMS). It periodically sends a GRMG query to a GRMG
application, receives its GRMG reply with the availability data for the
monitored components (such as the SAP backend system, URL or cluster of the
SAP J2EE Engine) and presents the reply in the Alert Monitor using the SAP
Solution Manager.
The GRMG application actually monitors availability. It runs in an iView or is called from an iView. Java-enabled components, HTTP-enabled components and SAP systems are monitored.
GRMG queries and GRMG replies are messages in a defined XML format.
The following graphic shows an example of a typical GRMG Web Server scenario:

The GRMG infrastructure in CCMS (1) periodically sends a GRMG query to the central Web Server (3). The Web Server sends this query to the Servlet Engine (4) as HTTP POST Request (5). The actual availability test is implemented in the GRMG application. In this example, the GRMG application checks the availability of an SAP System (6), an Enterprise Java Bean EJB (7) and servlets (8). The GRMG application collects the results of the check and prepares them as a GRMG reply. The GRMG reply is sent back to the GRMG infrastructure (9),(10) using the Web Server. The reply is analyzed there and displayed in the monitor tree of the CCMS.