Consider the technical information about this metric subnode in the metric hierarchy:
| Software Product and Version | SAP Convergent Charging 4.1 |
| Path | SAP Convergent Charging | SAP CC | Message | Stateful | Charge |
In a dispatcher instance, this node groups the performance and health data about the end-to-end processing of a charging operation request that is received by this dispatcher instance via the Online Charging Services (OCS).
In a rater instance, this node groups the performance and health data about the business processing of a charging operation request that is rooted by a dispatcher instance in the monitored SAP CC Core Server system.
The operation request message is initially received via the Message TCP technical interface in a real-time charging scenario (high performance, high volume). In this situation, the dispatcher instance is part of the frontends of the rater instance; see the corresponding activity and reported metrics. The rater instance is part of the backends of the dispatcher instance; see also the corresponding activity and reported metrics.
| Operation | Technical Interface | Global Service | Business Service | Implementation (Development or Customizing) | |
|---|---|---|---|---|---|
| Immediate Charging (for Direct Debiting) | Message TCP | Online Charging Services (OCS) | Event-Based Charging Without Credit Control (*)
(*): before digital service delivery |
Your mediation system or your client application implements the following SAP CC Java API: charge(..) Tip See the SAP CC Java/XML API Reference (Core Library) or the documentation of your customized mediation application (or system). |
|
The reported metrics are:
The possible subnode is:
SAP CC Application Help (aka SAP CC Library) about the convergent charging services provided by SAP Convergent Charging
Implementation and Development: SAP CC Java/XML API References about the com.highdeal.cnd.message Java package