!--a11y-->
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 on the status and function of the various items and contribute to the recognition of critical system events.
Portal functions are used to carry out performance monitoring and activity tracing for Knowledge Management.
You can use the information delivered by the monitoring, logging, and tracing applications to analyze the system and take appropriate action where necessary.
The monitoring and logging applications of the portal and Knowledge Management are integrated in the Monitoring workset of the portal. This workset is available to system administrators by default.
If you have fulfilled the relevant prerequisites, you can monitor parts of Knowledge Management and TREX using SAP Solution Manager.
For more
information, see the Portal Administration Guide, section
Monitoring Technology
and Logging.
The following monitoring and logging functions are available as iViews in the portal:
Displays the status of objects and allows you to identify configurations with errors.
Displays the statuses and statistics of active caches and allows you to empty caches manually.
Enables the monitoring of the various servers used for Search and Classification (TREX) and allows intervention when errors occur.
Displays information on the active crawlers and allows you to control them.
Returns information on the status of current indexing processes.
Displays error messages, warnings, and information generated by KM applications and services.
● 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.
SAP Solution Manager provides various monitors for monitoring Knowledge Management. For more information, see Monitoring KM with SAP Solution Manager. For more information about monitoring TREX, see SAP Note 697949.
You can also implement the TREX alert server instead 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.
Knowledge Management system information is now written to the file defaultTrace.trc. You can use the information logged in this file to monitor the system and analyze errors. This file is located in the directory .../usr/sap/<SAP_System ID>/JC<J2EE Engine Instance>/j2ee/cluster/server<n>/log/. Use the log viewer of the J2EE Engine to display and evaluate this file.

To view KM-specific entries, use the search function (category Location). Search for KM-specific entries using the string com.sapportals.wcm.
For more
information, see
Log
Viewer.
Changes to the configuration entries are logged automatically. You can see in the log, who made which changes when. For more information, see Logging Configuration Changes.
You can use the performance monitoring functions of the portal for the components of Knowledge Management. You identify the requests and threads pertaining to the KM components by the following component names:
Component |
Corresponding Component Name |
Content Management |
EP:KM:CM |
Search and Classification (TREX) |
EP:KM:TREX |
For more
information, see the Portal Administration Guide under
Performance
Monitoring.
Knowledge Management sends system information to the Java Application Responsetime Measurement (JARM) application. This application allows you to record the activities of individual KM requests and their components, and to analyze them as regard performance and errors in the Log Viewer of the J2EE engine.
For more
information, see
Activity
Tracing in the portal administration guide, and SAP Note
697949