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 | | Backends |
This node groups the performance and health data that relates to the back-end activities. A back-end is an external component, such as a database, an ABAP system via SAP JCo, another SAP CC instance or system. A back-end activity is the interaction with an external component. The back-ends are used during a front-end or an internal activity such as a job or a scheduled processing. See the associated nodes, "Frontends" and "SAP CC|Scheduler", for more information.
A back-end interaction could be considered at system or instance level. The back-end of an instance could be another instance of the same system and thus is not a back-end of the system, it is a resource consumption of the system.
| Front-End Activities | Instance Activities | Back-End Activities |
|---|---|---|
|
Outside the SAP CC cluster: Inside the cluster: File system: |
Outside the SAP CC cluster: Inside the cluster: File system: |
This node provides you with the lists of metrics that relate to
| Node | Definition | Details |
|---|---|---|
| DB | The database connections activities | SQL: per statement details |
| JCo | The JCo destinations activities | The JCo function execution related metrics |
| BulkWriter | The file system activities that write data in bulk mode |
|
| InternalMessage | The interinstance communications via the Message TCP technical interface of SAP Convergent Charging | |
| Message | The public communications via the Message TCP technical interface of SAP Convergent Charging | SAP CC client such as BART or Diameter Server systems |
Note
There is no metric defined in SAP CC at this level. Consider the subnodes in the metric hierarchy.
The possible subnodes are: