Cache

Definition

The metrics related to the SAP CC caches

Technical Data

Consider the technical information about this metric subnode in the metric hierarchy:

Software Product and Version	SAP Convergent Charging 5.0
Path	SAP Convergent Charging | JMX | com.highdeal | Cache

Description

Several types of caches are stored in memory to improve the performance of the SAP CC system.

A missed object is a data object not found in the data cache.
A victimized object is an object removed from the cache to create sufficient space for another object.

The monitored data caches are:

• Provisioning Cache
  This cache contains customer master data: contracts and allowances, subscriptions, counters, and subscriber accounts. This data cache is only monitored in the rater instances of the SAP CC system. SAP recommends that this cache contains all the managed data. Victimization is a potential issue in this case.
• Guiding Cache (Access Data)
  This cache is used to determine the required routing data for transferring the incoming charging operation requests to the adequate rater instance in the SAP CC system. This instance is able to charge the customer service usage to the corresponding contract (or subscription) in the master data. Because the guider instances rarely use all the accesses, keeping all the accesses in memory is unnecessary. Note that victimization is not an issue in this case.
• Session Cache and Session History Cache
  This cache contains the charging sessions created during the execution in session-based mode of the charging process of chargeable items, and it also contains the history of the charging sessions. SAP recommends that this cache contains all the managed data. Victimization is a potential issue in this case.

Monitored Application Data

The possible subnodes are:

• Provisioning Cache
• Session Cache
• Session History Cache
• Shared Allowance Cache