Batch

Definition

The metrics related to the processing queue dedicated to the Batch Message Service

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 | SAP CC | Queue | Batch

Description

This node groups the performance and health data about the processing queue that is dedicated to the Batch Message Service. This specialized queue (BATCH_QUEUE) is available in the dispatcher, guider, and rater instances to provide the Batch Message Service that delivers the infrastructure of:

  • the offline charging services (OFCS) of SAP Convergent Charging via the Message TCP technical interface (in postpaid environments)
  • the convergent charging services via the Web Services technical interface (in a soft real-time environment or in offline environments)

You can monitor and troubleshoot the activity of this specialized processing queue (queue size) and of its assigned execution threads (average response time, CPU time, idle tme, responses per interval, and wait time).

Important Note

The queueing mechanisms and functions depend on the type of the instance in the SAP CC Core Server system:

  • In a dispatcher instance as frontend of the SAP CC system, the reported metric shows the use of the batch service client applications or systems via the Message TCP technical interface. They are the SAP CC BART Server system, mediation systems, and other client applications that request offline charging operations to the SAP CC system. The business operations are notably: acquire, batch charge, and blank charge. These client applications (or systems) implement the convergent charging services. Refer to the com.highdeal.cnd.message.BatchServiceClient class in the SAP CC 5.0 Java/XML API Reference (Core Library). Depending on the implementation and Customizing in your SAP system landscape, you only monitor a subset of operation types.
  • In the guider and rater instances, the reported metric shows the internal use of the Batch Message Service between the dispatcher instances and the other instances. The internal usage includes, for example, the batch service client, but also messages corresponding to charging operation requests initially received via the Web Services technical interface.

For more information about the monitoring and troubleshooting of the Batch Message Service, refer to the Message metric node in the metric hierarchy and see its Batch subnode in this user assistance.

Available Metrics

The reported metric is:

Monitored Application Data

The possible subnode is:

Additional Information

For more information, consult the following user assistance: