Monitoring the PCD Cache 

The Java Systems Reports tool in the SAP NetWeaver Administrator provides a predefined monitor that allows you to monitor the cache of the Portal Content Directory (PCD).

The predefined PCD cache monitor is located in the monitor tree in the following path: Services → Portal Content Directory 

More information: Java System Reports (about using Java Systems Reports, activating a monitor, viewing monitoring data, and creating custom reports)

Once you have activated the PCD Cache monitor in SAP NetWeaver Administrator, you can also view the monitor using the monitoring architecture of the Computing Center Management System (CCMS).

In CCMS, use transaction RZ20 to view the JMX monitors. The PCD cache monitors are located in SAP J2EE Monitor Templates → Engine Services → <SID> → Portal Content Directory; where <SID> is your scenario description.

Monitored PCD Caches

In the default configuration, two caches are displayed in the monitoring tree:

●      Shared objects cache (xfs.data): Contains objects, in the XFS layer, which are shared among different portal users. For example, roles, pages, and iViews.

●      User objects cache (xfs.user): Contains objects, in the XFS layer, which store user-specific personalization data. One object exists per user in this caching level.

The XFS layer cache stores objects read from the database in complete units—per role. In addition, it caches internal nodes (and evicted together with the root node).

Monitored Values

The PCD cache monitor monitors the following values for each cache:

Value	Description
Cache hits	The number of requests served by the cache.
Cache requests	The frequency at which an object was requested from the cache.
Evicted objects	The number of objects removed from the cache as a result of garbage collection. A high number can indicate low cache efficiency due to a high rate of garbage collections.
Hit ratio	The percentage of cache requests served by the cache (calculated from the ratio between cache hits and cache requests). This is value is an important indicator for the efficiency of the cache.
Invalidated objects	The number of objects removed from the cache due to a write operation. Write operations on one cluster node lead to cache invalidations on all other cluster nodes. A high number can indicate low cache efficiency due to frequent write operations for objects that are often read at runtime.
Number of cached objects	The number of objects currently held in the cache. This is an approximated number since a delay may exist between the eviction of an object by garbage collection and the removal of a corresponding SoftReference object that is stored in the cache.