Displaying J2EE Availability Data in the CCMS 

Use

You can display the availability data and alerts for J2EE components monitored with GRMG in the corresponding CCMS Monitor.

Prerequisites

You must have enabled the Availability Monitoring of the J2EE Engine.

Procedure

...

       1.      Log on to the central monitoring system.

       2.      Start the CCMS Alert Monitor by opening Transaction RZ20.

       3.      Open the SAP J2EE Monitoring Templates monitor collection.

       4.      Open the Heartbeat monitor.

Result

The top node in the subtree contains the description of the GRMG scenario, which usually identifies the name and location of the application checked by the scenario. For each application sub-component that is checked by the scenario, there is a separate component subtree, for example, the scenario J2EE_630 004 monitors among others the component Test for P4 service. The subtree shows the host or J2EE server node on which each instance of a component is running. The Availability monitoring attribute reports the availability of the component in percent averaged over the last fifteen minutes.

If a monitored component is OK and available, then the entire monitoring tree will be green.

If one or more of the subcomponents monitored for the component is malfunctioning, then that part of the monitoring tree turns red and one or more alerts are generated.

If an error occurs in the execution of the GRMG monitoring scenario, then only the Scenario Error monitoring tree is refreshed in the central monitoring system. For example, if an HTTP communication error occurs – the monitoring system cannot contact the J2EE engine – then a scenario execution alert is triggered. But no data is reported on the availability of the monitored component, because no data is available. In this case, the component monitoring tree at first remains green, and then goes into inactive status. At the time of entry into inactive status, a heartbeat alert is triggered to tell you that monitoring of the J2EE component has stopped.

An inactive subtree and heartbeat alert may mean that the J2EE engine is down, but it may also be the result of an incorrect URL or some other problem. See the self monitoring subtree in the heartbeat monitor (Transaction RZ20) and Transaction GRMG in the central monitoring system for more information.