RECOVERY
These properties are related to the recovery of the process flow that was unable to complete due to an unexpected shutdown of Kernel. When you create a process flow, by default the process flow is created as a recoverable process flow. Implicit checkpoints are added before and after each activity of the process flow.
On reaching each of the checkpoints, the state (data, context variables) of the process flow is written to a file in the recovery directory. When the system is restarted after failure, it checks the recovery directory, finds out the recoverable process flow, and restarts the process flow execution from the last saved successful checkpoint. The recovery information saved in the recovery folder remains intact unless the process flow is recovered and completed.
After the process flow is executed, this information is deleted. There is one file for each process flow. If the recovery option is set to NO, the recovery information is saved but recovery is not done. If you enable the recovery property, the failed process flows are recovered.
Property Name | Description | Default Value | Possible Values |
|---|---|---|---|
abpm.transaction.recovery.enable | Enable or disable recovery of a process flow after a system failure. | yes | yes or no |
REPROCESSING
Property Name | Description | Default Value | Possible Values |
|---|---|---|---|
abpm.transaction.reprocessing.enable | Enable or disable recovery of process flow after the process flow aborts for any reason, except system failure. | yes | yes or no |
Execution
| Property Name | Description | Default Value | Possible Values |
|---|---|---|---|
| abpm.transaction.activities.executionTime.enable | Displays all executed services with execution time in the context file. | yes | yes or no |
ARCHIVAL
| Property Name | Description | Default Value | Possible Value |
|---|---|---|---|
| abpm.create.repository.archive.path | Specifies whether to create the archive folder or not if it does not exist. Set this property to yes, if you want to archive the process flow logs before they are cleaned up by the cleanup process. If you set this property to no, then the logs are not archived before cleanup. | yes | yes or no |
| abpm.logs.archival.enable | Enable or disable Archival of Process flow log | yes | yes or no |
| abpm.logs.archival.database | Specifies whether to archive the logs on the same database, which is used to store the logs, or to use another database. Set this property to 1, if you want to archive the logs in the same database, where the logs are being stored. In this case, for every log table, an archive table is created in the log database and logs are archived in these tables. | 1 | 1 or 2 |
| abpm.logs.archival.batch.enable | Specifies whether to archive the logs record by record or in a batch. If the values is no, records are archived one by one. If the value is yes, the records are archived in batches. | no | yes or no |
| abpm.logs.archival.batch.size | Specifies the number of records to be archived in one batch. Its value specifies the number of records, which are archived in one batch, when abpm.logs.archival.batch.enable property is set to yes. | 1000 | any integer |
| abpm.logs.deleteData.onArchivalFailure | Specifies whether to delete the records from the log table, if an error occurs in archival. If the value is no, then records from main log tables are not deleted when there is any error during archival. If the value is yes, then records from main log tables are deleted, even if there is any error during archival. It is recommended to keep this property as no. | no | yes or no |
| abpm.logs.sendNotification.onArchivalFailure | Specifies whether to send a mail, if an error occurs during log archival. If the value is no, then no mail notification is sent in case of any error during log archival. If the value is yes, then mail notification is sent to the email address configured for the admin user, in case of any error during log archival. If this property is set to yes, then make sure that the Mail Server Parameter properties are configured properly. | yes | yes or no |
| abpm.data.archival.enable | Option to enable or disable the archival of the process flow repository. Set this property is to yes, if you want to archive the process flow repositories before they are cleaned up by the cleanup process. If you set this property to no, then the repositories are not archived before cleanup. | yes | yes or no |