...
To provide a fast and efficient charging capability, the SAP CC Online agent relies on the Asynchronous Charging Client (AsynchStatefulServiceClient). For further information about the SAP CC AsynchStatefulServiceClient API, see the SAP AsynchStatefulServiceClient documentation.
| Note | ||
|---|---|---|
| ||
The SAP CC APIs that the SAP CC Online agent depend on do not support setting the itemImmediatelyLoaded flag for ChargingOutputContext. As a result, the SAP CC Online agent cannot support scenarios such as CIT creation via charging requests. |
In order to reduce the number of connected clients on a SAP Convergent Charging core server, a pool of shared clients exists on the side. It means that all the workflows running in the same EC or ECSA will not instantiate their own connection with SAP Convergent Charging, but instead use one shared client.
Based on its configuration (Host, Port, Timeout and Flow Control), the SAP CC Online agent will pick a mapping client up from the pool when the workflow is initialized. If there is no client matching a particular configuration, a new client will be added to the pool. For further information about how to configure the client, see 9.69.1.2 1 SAP CC Online Agent Configuration.
| Note | ||
|---|---|---|
| ||
Due to the asynchronous behavior of the client, requests and answers are not grouped together, and the order of the requests and answers cannot be guaranteed. However, they share a unique ID for the workflow execution. |
...