Monitoring

Use

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. 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 Support 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.

For more information, see Monitoring, Logging, and Tracing and Monitoring .

Procedure

Alert Monitoring with CCMS

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 Monitoring KM with SAP Solution Manager .
Caches

Detailed Monitoring, Problem, and Performance Analysis Tools

Trace and Log Files

Trace and log files are needed to analyze problems.

Knowledge Management uses the log mechanisms of the Application Server Java (AS Java). System information is written to the defaultTrace.trc file.

Content	File	Path
System information	`defaultTrace.trc`	`...\usr\sap\<SAP_System ID>\<Java_instance_name>\j2ee\ cluster\server<n>\log\`
Audit information on repository events	`applications.log`	`...\usr\sap\<SAP_System ID>\<Java_instance_name>\j2ee\ cluster\server<n>\log\`
Configuration changes	`applications.log`	`...\usr\sap\<SAP_System ID>\<Java_instance_name>\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 .

Operating System Monitors

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.

For more information, see the documentation about monitoring in the CCMS.

Workload Monitors

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.

For more information, see the documentation about monitoring in the CCMS.

Software Component Monitors

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 Start of the navigation path System Administration Next navigation step Support Knowledge Management End of the navigation path in the portal.

Monitor Utility	Description
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 statuses and statistics for active caches and allows you to empty caches manually.
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.