Monitoring and Error Handling for SAP Web AS Java 

Purpose

Monitoring the SAP system helps the administrator to identify resource bottlenecks or problems early and to take action if required.

Integration

We recommend that you use the CCMS to monitor a production application server. The prerequisite for this is that the J2EE Engine is connected to a central monitoring system (CEN) by means of the agent SAPCCMSR with option –J2EE. The central monitoring system must be an SAP Web Application Server ABAP 6.40. In addition to extensive monitoring functions, the CCMS allows you to monitor entire system landscapes. Independent of the CCMS, you can check the logs of production systems in the Log Viewer of the Visual Administrator.

In the case of systems used purely for development and testing, the Visual Administrator provides basic functions for resources monitoring. Alerts are output in the monitoring service for monitored resources. For more information see State Monitoring in the Visual Administrator.

Features

For information about the options for monitoring the running system, see Error Identification and Analysis. A step-by-step procedure for actions to take if you identify an error is also provided there.

For information about what to take into account when reporting the error to SAP Support, see the Error Reporting section.

Problem Analysis Guide

The SAP NetWeaver™ Problem Analysis Guide (PAG) contains the following problem analysis scenarios for the various components of SAP Web AS Java:

·        Change Management Server Problem Analysis Scenarios

·        J2EE Engine Problem Analysis Scenarios

·        Web Dynpro Java (ESS Scenario) Problem Analysis Scenarios

·        Design Time Repository Problem Analysis Scenarios

·        SAP Java Connector Problem Analysis Scenarios

Note that this documentation is available in English only.