Versions Compared

Version Old Version 1 New Version Current
Changes made by

Gunjan Tulwani (Unlicensed)

Saurabh Gupta (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

Ghibli Business Integrator Adeptia Suite has a rerun feature to execute aborted process flows. After identifying the reason of for the failure, you can rectify and rerun the process flow for successful execution. The A process flows flow may be aborted due to any reason e.g.(for example, incorrect data mapping or schema definition). However, if it is aborted due to Kernel shutdown, the Recovery feature handles it automatically. All such uncompleted incomplete process flows which flows that are recoverable are recovered through the recoveryRecovery, and not rerun Rerun feature.         

Using Checkpoints

Using Checkpoints, you can reprocess your aborted process flows. Checkpoint is A checkpoint is an action that can be used while creating a process flow. However, you:

  • Cannot reprocess the Process process flows which do not have checkpoints.
  • Can add any number of checkpoints in a process flow.
  • Must not use it after an asynchronous activity, which is generating a source stream. Otherwise, after rerun, the source stream (generated by an asynchronous activity) will not be available for the target activity (the activity which will be consuming this stream).

Info
  • If an activity is asynchronous, process flow initiates the execution of that activity and subsequent activities as defined in the process flow without waiting for the completion of the first activity.
  • Repository file is not generated for the activities which that are used in Asynchronous mode.

Must change the Mode property of all the checkpoints used in the process flow to Rerun. See the Enabling Rerun Feature section for information. 

...

How does Rerun Works?

During execution of a process flow, at every checkpoint, the Process Flow stores its current state in a rerun file. There is one rerun file for each execution of a process flow. These rerun files are stored in a rerun folder defined in the abpm.reprocessing.repository.root property. 

If the process flow aborts, the rerun file will have the state of the process flow till the last checkpoint. If no checkpoint is reached, no rerun file is created and the process flow can never be reprocessed after failure. In the rerun file, only the state of the process flow is stored. Intermediate data of the process flows are stored in the repository folder. If your process flow has checkpoints, and the rerun is enabled, then when you rerun, the Kernel looks for the rerun file for that particular process flow instance. If it finds such file, it picks up the intermediate data from there and resumes the process flow from last checkpoint state.

The rerun file remains in the rerun folder unless the process flow execution is completed successfully. The Intermediate data gets deleted automatically by /wiki/spaces/AS/pages/5310943 or a user can delete it manually to free disk space. 

Enabling Rerun

Perform the following steps to enable rerun:

  1.  In your process flow, select each of your check points one by one.
  2. Change their respective Mode property to Rerun. This enables the rerun feature.