Migrating Checkpoints
Checkpoints should always be reloaded before starting the Fulfillment Provisioning application’s driver modules. Checkpoints are always re-injected after the following operations.
The provadmin command triggering migration is called migrate. This command will stop flow controllers, wait for them to be stopped, migrate the checkpoints and eventually automatically restart flow controllers.
Notice a checkpoint containing the same product and application versions than those defined in the Fulfillment Provisioning instance will just be skipped during a migration process.
provadmin migrate checkpoints [option1] [option2]...
|
Parameter |
Description |
|---|---|
|
nodename |
The path to the Fulfillment Provisioning node. |
|
cpnodename |
The checkpoint node name. |
|
types |
The checkpoint types (aka kinds) that should be loaded. An empty value (default case) means that every checkpoint kind should be loaded (except if the interface does not allow it). Each checkpoint kind owns a priority that will define the order in which checkpoint kinds will be loaded. |
|
chunkSize |
This parameter defines the maximum number of checkpoints that should be iterated before the low level transaction is commited and another one started to continue loading checkpoints. The default setting is 500. |
|
autoStartFC |
If set to true, flow controller instances will be automatically started when all checkpoints have been loaded so that orders are resumed immediately. |