Displaying J2EE Engine Monitoring Data in the CCMS 

Use

You can monitor the SAP J2EE Engine from a central ABAP monitoring system using the CCMS monitoring architecture. The collected data is sent to the central monitoring system using a CCMS agent.

Prerequisites

·        Your central monitoring system must be a SAP Web Application Server ABAP 6.40.

·        You must have installed, registered, and activated the SAPCCMSR agent with the –J2EE option. For information about this, see Installing an Agent on a Java Instance (Java Standalone System) or Installing an Agent on a Java Instance (Double-Stack System).

Features

·        J2EE data about availability, status, logs, and JARM is displayed in the CCMS alert monitor (transaction RZ20). If errors occur, alerts are triggered. If you have assigned an auto-reaction method to the alerts, the system automatically performs actions if errors occur (such as notification of the error).

For more information, see:

Enabling the Availability Monitoring of J2EE Engine

Monitoring the Status of the J2EE Engine Using the CCMS

Monitoring the J2EE Log Files in the CCMS

Java Application Response Time Measurement

The display in the CCMS is divided into different monitor types (heartbeat, log files, and so on), and shows data for all of the J2EE Engines monitored by the central system. If you only want to view the data for one engine, and therefore want to change the standard allocation, you can create your own monitor.

 

·        J2EE statistics records are displayed in the Global Workload Monitor (transaction ST03G) and in the functional trace (transaction STATTRACE). Statistics records are created to enable you to monitor the performance of a J2EE Engine. These statistics records provide information about the workload generated and the resources used in the system by actions. This means that, on one hand, you obtain a very exact picture of the overall quality of a system, and on the other hand, in the case of a performance bottleneck, you obtain information about its cause.

For more information, see Distributed Statistics Records (DSRs).

 

·        Performance trace data is also displayed in the functional trace (transaction STATTRACE). The performance trace provides duration information for the individual modules of the engine and therefore provides a finer granularity than the statistics records. It also displays unaggregated data in a different way to the statistics records.

For more information, see Performance Trace.