Monitoring
Various components, applications, and services are delivered with the Knowledge Management capabilities of SAP NetWeaver. 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. 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 Knowledge Management are integrated into the Monitoring workset of the portal. This workset is available to system administrators by default.
If all relevant prerequisites are met, you can monitor parts of Knowledge Management and TREX using the CCMS or in the SAP Solution Manager (see SAP NetWeaver 7.0 Supportability Setup Guide on the SAP Service Marketplace at service.sap.com/instguides ® SAP NetWeaver ® Release 7.0 ® Operations).
More information:
Monitoring,
Logging, and Tracing and
Monitoring Technology
and Logging
Proactive, automatic monitoring is the basis for the reliable operation of your SAP system environment. SAP provides you with the infrastructure and recommendations for the setup of alert monitoring. This allows you to recognize critical situations within Knowledge Management as quickly as possible.
The following monitors are available for monitoring Knowledge Management. You access them using transaction RZ20 in the CCMS.
Monitor Utility |
Description |
Components |
These monitors are
available in the CCMS in the transaction RZ20. You can also display the monitors in the SAP
Solution Manager using transaction solution_manager. For more information about these monitors,
see
|
Caches |
Trace and log files are needed to analyze problems.
Knowledge Management uses the logging mechanisms of the J2EE Engine. System information is written to the defaultTrace.trc file.
Important Log and Trace Files
Content |
File |
Path |
System information |
defaultTrace.trc |
.../usr/sap/<SAP_System ID>/JC<J2EE Engine Instance>/j2ee/cluster/server<n>/log/ |
Audit information on repository events |
applications.log |
.../usr/sap/<SAP_System ID>/JC<J2EE Engine Instance>/j2ee/cluster/server<n>/log/ |
Configuration changes |
config_audit.<n>.log |
.../usr/sap/<SAP_System ID>/JC<J2EE Engine Instance>/j2ee/cluster/server<n>/log/ |
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.
No operating system monitors are included in the standard delivery.
However, you can set up a monitor in the CCMS that displays the free memory space on the server used for managing the documents and folders of a file-system repository manager. The required data for this can be provided by the SAPOSCOL program.
More information:
Operating
System Monitor,
Filesystems
Monitor, and
Editing Monitors and
Monitor Sets
No workload monitors are included in the standard delivery.
However, you can set up a monitor in the CCMS that displays the workload of all nodes in a KM load-balancing environment. The required data for this can be provided by the SAPOSCOL program.
More information:
Performance
Overview Monitor and
Editing Monitors and
Monitor Collections
Monitors for technical components are needed to analyze problems.
The table below lists the monitors that are available in the portal to monitor Knowledge Management functions. To launch the monitors, choose System Administration ® Monitoring ® Knowledge Management in the portal.
Knowledge Management Monitors in the Portal
Monitor Utility |
Description |
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. |
|
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. |
|
Displays statuses and statistics for active caches and allows you to empty caches manually. |
|
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. Note that this information is not logged in the J2EE Engine log (see above). |