!--a11y-->
Monitoring KM with SAP Solution
Manager 
Just like the portal, you can monitor Knowledge Management using SAP Solution Manager. You can use SAP Solution Manager to call up information on the version, configuration, and status of Knowledge Management.

For information on monitoring Search and Classification (TREX), see SAP Note 697949.
CCMS provides the monitoring data, which you can display in SAP Solution Manager. In CCMS, you can use transaction RZ20 to launch the Alert Monitor functions. In SAP Solution Manager, you use transaction solution_manager. For more information about this, see service.sap.com/monitoring.
The Portal and Knowledge Management are connected to SAP Solution Manager (see SAP NetWeaver 2004s Supportability Setup Guide on the SAP Service Marketplace at service.sap.com/instguides ® SAP NetWeaver ® Release 2004s ® Operations).
In SAP Solution Manager and in CCMS, the following monitors are available:
KM Monitors in SAP Solution Manager and CCMS
Monitor |
Description |
Components |
Once you have launched transaction RZ20 in CCMS, navigate as follows: CCMS Monitor Sets ® SAP J2EE Monitor Templates ® Applications ® <%System ID%> ® <%Cluster nodes%> ® KMC ® Repository Framework ® Components. The monitor displays information about the status of the following objects: ● Filters ● Repository managers ● Repository services ● Services ● System information (displays the status of the content management system for the system node selected) The entries correspond as far as possible to the information that you can call up in the portal using the component monitor. The status of an object is displayed using colors and text. If an error has occurred, a message test helps you to localize the error and correct the configuration of the object in question in the portal, or to restart the component if necessary. Description: Provides a description of the item State: Specifies the status Availability: Specifies the availability as a percentage Startup Issue: Specifies which problems exist during startup Configuration Issue: Specifies which configuration errors exist Creation: Specifies the creation time Last Reconfiguration: Specifies the time of the last change to the configuration Next Automatic Restart: Specifies the time of the next restart |
Caches |
Once you have launched transaction RZ20 in CCMS, navigate as follows: CCMS Monitor Sets ® SAP J2EE Monitor Templates ® Applications ® <%System ID%> ® <%Cluster nodes%> ® KMC ® Repository Framework ® Caches. It displays information about the caches for Knowledge Management. Entry Count: Current number of entries in the cache Add Count: Number of new items that have been added to the cache since recording began + number of items whose lifetime was extended Insert Count: Number of new items that have been added to the cache since recording began. Insert Frequency: Number of new items that are added to the cache each second Remove Count: Number of items that have been removed from the cache since recording began. These items have been overwritten by new items, or have become invalid because they have exceeded the Entry Default Time to Live. Get Frequency: Number of accesses to the cache entries per second Hit Rate: Ratio of hits to accesses, specified as a percentage The higher the value, the more effective the cache. Size: Current size of cache in bytes The information displayed corresponds as far as possible to the information that you can call up in the portal using the cache monitor. The traffic light colors result from the value of the Hit Rate performance attribute. The threshold values that govern changes of the traffic light color are stored in the properties for the Hit Rate performance attribute.
The values displayed are only meaningful if there is a large enough number of cache accesses per unit of time. For example, if there are only a few hits over a longer period of time, the system calculates a very low Hit Rate or a Hit Rate of 0%. This results in a red traffic light. However, there is no serious error in this case. In such a case, the red traffic light can be put down to a statistical calculation based on too few measurements. We recommend analyzing the measurements only after an appropriate period of time with sufficient accesses. |

The monitors
are deactivated in the default setting and do not display the current values.
For more information about how you can activate monitors, see
Active and Inactive
Monitors. Once you have completed the measurement, you should deactivate
the monitors again for performance reasons.