Monitoring, Logging, and Tracing

Different components, applications and services are shipped with Knowledge Management. Knowledge Management provides several monitoring and logging applications for these objects in the form of iViews. These applications check and monitor Knowledge Management in the background. They deliver information about the status and function of the various items and contribute to the recognition of critical system events.

You can use the information delivered by the monitoring, logging, and tracing applications to analyze the system and take appropriate action where necessary.

For more information, see: Monitoring

The monitoring and logging applications of the portal and Knowledge Management are integrated into the Monitoring workset of the portal. This workset is available to system administrators by default.

You use the Logs & Traces plug-in in the SAP NetWeaver Administrator to display and analyze log files.

If you have fulfilled the relevant prerequisites, you can monitor parts of Knowledge Management and TREX using SAP Solution Manager.

Monitoring of KM in the Portal

The following monitoring and logging functions are available as iViews in the portal:

• Component monitor

  Displays the status of objects and allows you to identify configurations with errors.

  This monitor is suitable for individual installations of Knowledge Management. We recommend the cluster monitor for cluster installations.

• Cluster monitor

  Displays the status of objects in a distributed system landscape with multiple KM nodes and allows you to identify configurations with errors.

  It functions in a similar manner to the component monitor. You can use the cluster monitor to monitor all nodes in your KM system landscape centrally.

• Cache monitor

  Displays the statuses and statistics of active caches and allows you to empty caches manually.

• TREX monitor

  Enables the monitoring of the various servers used for Search and Classification (TREX) and allows intervention when errors occur.

• Crawler monitor

  Displays information on the active crawlers and allows you to control them.

• Indexing monitor

  Returns information on the status of current indexing processes.

• Running reports

  Displays information on reports that are currently running in the background.

  If necessary, you can stop the reports. For more information, see Reports .

Monitoring KM with SAP Solution Manager

SAP Solution Manager provides various monitors for monitoring Knowledge Management. For more information, see Monitoring KM with SAP Solution Manager .

Monitoring TREX with the TREX Alert Server

You can also implement the TREX alert server instead of or as well as SAP Solution Manager. The TREX alert server regularly checks central TREX functions and informs you about the system status by e-mail.

For more information, see TREX Alert Server .

Logging for KM

Logging System Information

Knowledge Management uses the log mechanisms of the Application Server Java (AS Java). The system information is written to the following files:

 

Important Log and Trace Files

 

You use Log Viewer to display and analyze the logged data. For more information, see: Log Viewer

To view KM-specific entries, use the search function (Location category). Search for KM-specific entries using the string /KMC/RF/APPLOG.

 

For information about these files, see Trace and Log Files .

For more information about monitoring the trace and log files, see Monitoring and Displaying Log Files .

 

Logging Configuration Changes

Changes to the configuration entries are logged automatically. The log tells you which users made changes and when they made them.

Log file for configuration changes

For more information, see Logging Configuration Changes .

 

Activity Tracing

Knowledge Management sends system information to the Java Application Response Time Measurement (JARM) application. This application allows you to record the activities of individual KM requests and their components, and to analyze them as regards performance and errors.

For more information, see Java System Reports .