Monitoring
Monitoring the AS Java system helps the administrator to identify resource bottlenecks or problems early on and to take the required action.
With the SAP NetWeaver Administrator, you can monitor the application server itself and the components and applications running on top of it. You can also extend the functionality of your custom applications by adding monitoring capabilities to them and thus to get advantage of the monitoring tools and infrastructure to monitor your own applications.
You can also access log files from one location, which reduces the time required for error identification and correction.
Local Monitoring
Java System Reports
To monitor your local system, you use the SAP NetWeaver Administrator tool Java System Reports.
It is a problem detection and analysis tool that you use for the following:
● Monitor the AS Java cluster and Java applications.
● Track the performance of one or all instances and cluster nodes of a particular Java system.
● Detect and analyze the causes of problems in an AS Java in a situation of reduced performance.
● Perform motivated tuning for productive use with the AS Java.
The most important information is summarized in a set of predefined charts and reports. You can also view data from each single monitor in the monitoring tree of the Monitor Browser and compose your own reports and charts.
More information: Java System Reports.
Monitoring and Displaying Log Files
To ensure the stable and error-free operation of the system, the system administrator needs to check the logs regularly for error messages. If required, it is also possible to reconfigure the default logging settings to optimally suit your scenario.
More information:
Monitoring and Displaying Log Files
Central Monitoring
If you want to monitor SAP NetWeaver Composition Environment 7.1 (CE) centrally, you must use a central monitoring system with release SAP NetWeaver 7.0.
● For more information about the configuration of centrally monitored CE, see the SAP NetWeaver 7.0 (2004s) Operation area on the SAP Service Marketplace (http://service.sap.com/operationsNW70). In the Monitoring section, see the document Monitoring Setup Guide for NW 7.0 for the relevant SP.
● For more information about how to configure the monitoring of individual CE components, see SAP Note 1107345.
Additional Monitoring Capabilities
To serve particular monitoring needs, an additional set of tools is available in the SAP NetWeaver Administrator.
● Guided Procedures Monitoring
The GP Monitor gives you full monitoring capability over the Guided Procedures system and applications and thus allows you to detect any problems that might occur.
The GP Monitor is a Guided Procedures tool for the SAP NetWeaver Administrator.
More information: Guided Procedures (GP) Monitor.
● Monitoring CAF Availability
You can use the monitoring tools to ensure your composite application is running properly. You need to make the relevant configuration with SAP NetWeaver Administrator to use CAF monitoring.
More information: Monitoring CAF Availability
● Monitoring Portal Availability
To monitor portal availability (using the portal heartbeat of the Portal Runtime) in SAP NetWeaver Composition Environment (CE) 7.1, you need to use a central monitoring system with a SAP NetWeaver 7.0 installation.
More information: Portal Monitoring
● Open SQL Monitoring
When Open SQL for Java is used to access a database, it is important to trace how the communication with the persistence store is handled. With the Open SQL Monitors, you can monitor the execution of SQL statements, the status of the table and catalog buffers, as well as the availability and the use of Open SQL database connections.
More information: Open SQL Monitors.
● Message Monitoring
The message monitoring enables you to search for Web service messages that were sent or received on your system. You monitor messages, for example, to track the status of Web service messages or to find errors that have occurred and establish what caused them.
More information: Monitoring Messages.
● Sequence Monitoring
With Web Services Reliable Messaging (WS-RM) you ensure that the communication between a Service Provider and a Service Customer is completed without errors. You use the analysis tools of the sequence monitor to find such errors. You use the sequence monitor, for example, to view its status or to stop or restart faulty sequences.
More information: Monitoring Sequences.
● Archiving Monitor
This area is part of the functionality of Java Archiving Cockpit. It enables you to monitor the progress of archiving sessions and displays statistics about how many objects have been written or deleted, and by whom.
More information:
Java Archiving
Cockpit● Monitoring with the SAP MC
With the monitoring options provided by the SAP Management Console, several additional monitoring scenarios are available.
More information: Monitoring the Application Server with the SAP MC