Show TOC

Monitoring Composition EnvironmentLocate this document in the navigation structure

Use

Monitoring the AS Java system helps the administrator to identify resource bottlenecks or problems early on and to take the required action.

With 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

History Reports

To monitor your local system, you use the SAP NetWeaver Administrator tool History Reports . It is a problem detection and analysis tool that you use for the following:

  • Monitoring the AS Java cluster and Java applications

  • Tracking the performance of one or all instances and cluster nodes of a particular AS Java

  • Detecting and analyzing the causes of problems in AS Java in case of reduced performance

  • Performing motivated tuning for productive use with 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.

For more information, see: History 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. For more information, see:

Monitoring and Displaying Log Files

Log Viewing

Log Configuration

Central Monitoring

If you want to monitor Composition Environment (CE) in SAP NetWeaver 7.3 centrally, you have several options:

  • For more information about configuring a centrally monitored CE with SAP NetWeaver 7.3 and above, see “Configuring the Monitoring Architecture” in the CCMS Monitoring documentation.

  • For more information about configuring a centrally monitored CE with SAP NetWeaver 7.0, see Start of the navigation path http://service.sap.com/operationsNW70 Next navigation step Monitoring Next navigation step Monitoring Setup Guide End of the navigation path.

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 SAP NetWeaver Administrator.

  • SAP NetWeaver Business Process Management Monitoring

    You can monitor processes and tasks of BPM with the SAP NetWeaver Administrator applications Manage Processes and Manage Tasks. These applications enable you to detect any problems within BPM processes and tasks.

    For more information, see: Monitoring and Managing BPM Systems, Processes, and Tasks with 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 SAP NetWeaver Administrator.

    For more information, see: Guided Procedures (GP) Monitor

  • Portal Monitoring

    You can use a number of applications in SAP NetWeaver Administrator to monitor the different components, applications, and services that compose the portal.

    To monitor portal availability (using the portal heartbeat of the Portal Runtime) in SAP NetWeaver Composition Environment (CE) 7.3, you need to use a central monitoring system with a SAP NetWeaver 7.0 installation.

    For more information, see: 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 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.

    For more information, see: Using Open SQL Monitors

  • Message Monitoring

    The Message Monitoring application 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.

    For more information, see: 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.

    For more information, see: 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.

    For more information, see:

    Java Archiving Cockpit

    Archiving Monitor

  • Monitoring with the SAP MC

    With the monitoring options provided by SAP Management Console, several additional monitoring scenarios are available.

    For more information, see: Monitoring the Application Server with SAP MC