Monitoring the NWDI with GRMG 

Use

On a J2EE Engine, a GRMG Heartbeat application is running. You use it to test the availability of applications.

Testing NWDI Services with GRMG Heartbeat

Call

...

       1.      Call an SAP system on which you want to call the heartbeat application.

       2.      Start transaction GRMG.

A list of the GRMG configurations appears.

       3.      Load a GRGM configuration or create a new one.

       4.      Select a GRGM configuration (or start or refresh it if necessary).

The status of the monitored service appears.

Analysis

...

       1.         Select transaction RZ20 in the CCMS system, on which you want to call the heartbeat application.

       2.      Navigate to the entry SAP CCMS Technical Expert Monitors and start All Monitoring Contexts.

       3.      Check all results under the following nodes:

¡        SAP JDI landscape availability check

¡        Test for CMSor SAP JDI landscape availability check

¡        Test for TCS-Auto_Deployment

       4.      If one of the nodes Test for CMS or Test for TCS-Auto_Deployment has status Red, the respective application is not available.

Continued Analysis/Troubleshooting

...

       1.         Start the J2EE Engine Administrator and log on to the J2EE Engine, on which the service is running.

       2.      Choose Server ®Services ®Deploy.

       3.      Select the node EJBContainer and then the application

CMS: sap.com/tc~SL~CMS~PCS

       4.      If the result of the heartbeat check shows that the service is not available, proceed as follows:

CMS:

sap.com/tc~SL~CMS~PCSis marked as not available or the entry  sap.com/tc~SL~CMS~PCS” is missing.

                            a.      If the entry is missing, deploy the service

CMS (file name cmsserver.ear).

                            b.      If the entry is marked as “not running“, start the application.

       5.      Check the heartbeat status of the service again.