Interface ISessionStartChargingAsyncOperation
- All Superinterfaces:
IExternalDataSettable,IReservationRenewalListenerIdSettable,ISessionAsyncOperation,ISessionDefaultAttributeHolder,ISessionReservation
- All Known Implementing Classes:
SessionChargingOperation
Java interface defines necessary methods for implementing the beginning of a multiservice session during session-based charging operations:
you prepare
the expected reservations for an end customer and you trigger the start operation by executing the object returned by the
createSessionStartAsyncOperation(..) method
in your charging client.
Tip
You use this Java interface for asynchronous communications via the Message TCP technical interface
of SAP Convergent Charging.
Consult the information available about the synchronous communications; The implementation is easier.
See the ISessionStartChargingOperation interface.
Implementation in Your Client Application
You implement the session-based charging service in an online and real-time environment and with asynchronous communications.
Customizing
-
During a customer session, you call
the
prepareReserve(..) methodto create the relevant single reservation operation request. Each call adds a new reservation operation request in the container operation request. -
You call the
execute() methodto send the container operation to the connected SAP CC system. The SAP CC system processes the reservation operation requests included in the container operation.
Note
In your implementation code, you use this interface as result of the method:
| Async. Comm. |
|---|
createSessionStartAsyncOperation(..)
|
Advanced Implementation
The following advanced implementation activity is possible.
Notes on SAP CC Implementation
This section provides you with some implementation instructions for advanced features.
Advanced Implementation: Enabling Reservation Renewal
The IReservationRenewalListenerIdSettable interface is used to precise the ReservationRenewalListener identifier at session start.
This identifier is used:
- To specify the ReservationRenewalListener used to handle the Renew Reservation notifications for this session
- To specify a backup ReservationRenewalListener (in case the first one fails)
-
Because the
charging clientused to manage the charging session (start/update/stop) is not necessary thecharging clientthat will manage the notifications for this session
This identifier can match no (or not yet) registered ReservationRenewalListener in the SAP CC system.
In that case, there is no impact on the current session-based charging scenario.
Notifications are sent (or resent) to the charging client until the TTL last. Session operations are not blocked.
-
Nested Class Summary
Nested classes/interfaces inherited from interface com.highdeal.cnd.message.ISessionDefaultAttributeHolder
ISessionDefaultAttributeHolder.TransactionSelectionCriteriaNested classes/interfaces inherited from interface com.highdeal.cnd.message.ISessionReservation
ISessionReservation.SessionReservationResolution -
Method Summary
Methods inherited from interface com.highdeal.cnd.message.IExternalDataSettable
setExternalDataMethods inherited from interface com.highdeal.cnd.message.IReservationRenewalListenerIdSettable
setReservationRenewalListenerIdMethods inherited from interface com.highdeal.cnd.message.ISessionAsyncOperation
executeMethods inherited from interface com.highdeal.cnd.message.ISessionDefaultAttributeHolder
getCleanUpResultType, getResultType, isFilterTransaction, setCleanUpResultType, setFilterTransaction, setResultTypeMethods inherited from interface com.highdeal.cnd.message.ISessionReservation
prepareReserve