Package com.highdeal.cnd.message

Interface ISessionStartChargingOperation

All Superinterfaces:
IExternalDataSettable, IReservationRenewalListenerIdSettable, ISessionDefaultAttributeHolder, ISessionOperation, ISessionReservation
All Known Implementing Classes:
SessionChargingOperation
public interface ISessionStartChargingOperation extends ISessionReservation, ISessionDefaultAttributeHolder, ISessionOperation, IReservationRenewalListenerIdSettable, IExternalDataSettable
This 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 createSessionStartOperation(..) method in your charging client.

Tip

You use this Java interface for synchronous communications via the Message TCP technical interface of SAP Convergent Charging. Consult the ISessionStartChargingAsyncOperation interface for ultra-speed asynchronous communications.

Implementation in Your Client Application

You implement the session-based charging service in an online and real-time environment and with synchronous communications.

Customizing

  1. During a customer session, you call the prepareReserve(..) method to create the relevant single reservation operation request. Each call adds a new reservation operation request in the container operation request.
  2. You call the execute() method to 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:

Sync. Comm.
createSessionStartOperation(..)

Tip

Do not use the SessionChargingOperation Java class to develop your Java-based client application.

Advanced Implementation

The following advanced implementation activities are possible. Refer to the Notes on SAP CC Implementation section for more information about:

Notes on SAP CC Implementation

This section provides you with some implementation instructions for advanced features.

Advanced Implementation: Enabling Reservation Renewal

Use the IReservationRenewalListenerIdSettable interface to enable the reservation renewal functiona and specify the identifier of the ReservationRenewalListener at multiservice session start.

This identifier is used:

  • To specify the reservation renewal listener that handles the renew reservation notifications for this session
  • To specify a backup listener (in case the first one fails)
  • Because the charging client used to manage the charging sessions (start/update/stop) is not necessary the charging client that will handle the renew reservation 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.

Advanced Implementation: Specifying External Data for Notification Listeners

Use the IExternalDataSettable interface to specify the external data to be included in the renew reservation notifications by the connected SAP CC system.

See Also: