Availability Monitoring of J2EE Engine and
Java-Based Applications
Use
In productive system landscapes, the availability of components has to be checked automatically. Using the so-called “Heartbeat” (Generic Request and Message Generator (GRMG)), the administrator has a central infrastructure to check the availability of the J2EE Engine and the JAVA based applications.
The GRMG Application agent is implemented as a Servlet with name ServerGRMGApplication distributed in the form of an application EAR file named heartbeat.ear. The application itself is registered under the name sap.com/com.sap.engine.heartbeat.
Before you
continue using the GRMG, make sure you are familiar with the
Monitoring with the
Generic Request and Message Generator documentation.
Installation
The heartbeat.ear is automatically deployed during the J2EE Engine installation. In order to see the J2EE availability data in your central CCMS monitoring system, you just have to upload the customizing file on the ABAP system using the Visual Administrator. The upload can take up to one hour, because an hourly report informs the agent of the GRMG scenario. You can see if the upload was successful in the ABAP system by starting Transaction GRMG.
In order to see results, the com.sap.engine.heartbeat application must be running. For more information, see Enabling the Availability Monitoring of J2EE Engine and Displaying the Monitored Data in the CCMS.
The J2EE Engine Service Components to be Tested
The grmg-customizing.xml defines the following J2EE Engine components to be tested: HTTP Provider Service, P4 Provider Service, Web Container, EJB Container, Web Services Container Service.
The ServerGRMGApplicationreceives a GRMG request. With the help of the GRMG library (com.sap.util.monitor.grmg), the request is processed and a validation is made whether the XML syntax and contents are correct. A check is then made to test whether the components specified in the XML file are working properly. If you try to request a component not defined for testing, an error message is sent as a response.
Testing J2EE Engine Components
Component Name |
Test Description |
HTTP Provider Service |
There is an HTML file in the heartbeat.ear. The system tries to access this HTML file for testing the HTTP. If the HTTP Provider Service is up and running, a message will appear that informs you that the component is working properly; otherwise you receive an error message. |
P4 Provider Service |
To test this component the system tries to create a new InitialContext. If it succeeds, a confirmation message is displayed; otherwise an error message appears. |
EJB Container |
In the heartbeat.ear, there is a test bean named GRMGEJBTest. To perform the test the system first looks up this test bean and then tries to call one of its methods. If the test passes correctly, a message will inform you that the EJB Container is working properly; otherwise an error message appears. |
Web Service Container Service |
In the hartbeat.ear there is a test Web service named GRMGWSTest, which communicates through a SOAP protocol using a HTTP connection. The implementation of this test Web service is an EJB Bean. To test the J2EE Engine Web services, a request is sent to the GRMGWSTest. If the test Web service returns a correct (“hardcoded” in the bean) answer, this means that the J2EE Engine Web Service Container is working properly; otherwise an error message appears. |
See also: