Kinds of Fulfillment Provisioning Checkpoint

Client Adapter Checkpoints

Fulfillment Provisioning applications use a driver module to receive requests from northbound interfaces and inject resulting service orders into the beginning of the provisioning flow. A northbound request may contain several frames, each frame generating a service order. Each frame is processed in a dedicated transaction, thus possibly implying the need for a specific checkpoint kind called "ca".

A client adapter checkpoint is created for multi-frame requests only, reused for each consecutive frames and deleted when the northbound request has been entirely parsed. At this point all the related service orders have been created and checkpointed internally.

Service Order Checkpoints

A service order checkpoint is created the first time a service order is checkpointed. The same file is reused for the lifetime of the service order. The service order must go through a commit point before it is destroyed, otherwise the checkpoint file is not destroyed.

Other Checkpoint Kinds

Fulfillment Provisioning uses several other checkpoint kinds but generally developers do not have to care about them.