Recovery (Magic xpi 3.x)
The Recovery system lets you recover data lost due to a system crash. You can set the Recovery policy for each flow during the project development stage. However, if the flow is called from another flow, it will use the recovery policy of the original flow.
The Recovery system keeps track of all currently executed components. A Recovery system runs on each Magic xpi Server in the integration project and operates in Start and Ongoing modes.
|
Start
|
When a Magic xpi Server starts up, the Recovery system searches for uncompleted flows created due to a Magic xpi Server restart. The Recovery system tries to reactivate uncompleted flows according to their Recovery Policy property: Abort, Restart, or Save Point. You define this policy in the Magic xpi Studio's Flow Properties dialog box.
|
|
Ongoing
|
The Recovery system constantly checks to see whether a currently executed flow or component has exceeded the execution timeout setting. The Recovery system notifies the MSG system and responds according to the Flow Recovery policy. You define this in the Editor.
|
The Recovery system has an execution database that saves component execution-time and completion information for all the currently executed flows. When a flow component or flow has completed its execution, the entry is removed from the Recovery system database.
Entries left in the Recovery system database after a crash represent the point at which the flows stopped. These entries are used by the Magic xpi Server to restart the integration processes from the point at which they stopped.
For more information about Magic xpi's recovery scenarios, click here.
|
Note:
|
The Server does not execute a recovery policy when a Trigger component gives an error.
|
|
Storing Recovery Data
Called Flow Recovery Policy
Flow Timeouts
