RECOVERY
These properties are related to the recovery of the process flow , that was unable to complete due to an unexpected shutdown of the 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.
...
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 | Description | Used to enable Enable or disable recovery of a process flow after a system failure | Default Value. | yes | Possible Valuesyes | /or no | Selection CriteriaIf you want to enable process flow recovery, set the value as yes. Otherwise, set the value as no. For detailed information about process flow recovery, refer to the Recovery section of Adeptia Suite Developer Guide. |
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
Property Name | Description | Default Value | Possible Values | |
|---|---|---|---|---|
abpm.transaction.reprocessing.enable | Description | Used to enable Enable or disable recovery of process flow after the process flow aborts for any reason, except system failure.Default Value | yes | yes or no |
Possible Values | yes/no | |||
Selection Criteria | If you want to enable process flow reprocessing, set the value as yes. Otherwise, set the value as no. For detailed information about process flow reprocessing, refer the Reprocessing section of Adeptia Suite Developer Guide. |
...
Execution
| Property Name | Description | Default Value | Possible Values |
|---|---|---|---|
| abpm.transaction.activities.executionTime.enable | |||
| Description | |||
| Default ValueDisplays all executed services with execution time in the context file. | yes | yes or no |
...
ARCHIVAL
| Property Name | Selection CriteriaDescription |
|---|
ARCHIVAL
...
| Default Value | Possible Value | ||
|---|---|---|---|
| abpm.create.repository.archive.path | Description | Specifies whether to create the archive folder or not | ,if it | does not exist.
Default Value | yes | ||
Possible Values | yes/no | ||
Selection Criteria | Using this property you can choose, whether to create the archive folder, which is specified in the abpm.transaction.repository.archive.path property, or not, if the folder does not exist. |
...
Description | Option to enable or disable Archival of Process flow log |
|---|---|
Default Value | yes |
Possible Values | yes/no |
Selection Criteria | . |
...
| 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 |
...
Selection Criteria | Specifies whether to archive the logs on the same database, which is used to store the logs, or to use another database. | |
Default Value | 1 | |
Possible Values | 1 or 2 | |
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 | Description | Selection Criteria | Specifies whether to archive the logs record by record or in a batch. |
|---|---|---|---|
Default Value | no | ||
Possible Values | yes /no | ||
| 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 |
...
Selection Criteria | Specifies the number of records to be archived in one batch. | |
Default Value | 1000 | |
Possible Values | Any positive integer, which can be easily supported by the archival database. | |
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 |
...
Selection Criteria | Specifies whether to delete the records from the log table, if an error occurs in archival. | |
Default Value | no | |
Possible Values | yes /no | |
| 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 |
...
Selection Criteria | Specifies whether to send a mail, if an error occurs during log archival. | |
Default Value | yes | |
Possible Values | yes /no | |
| 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 |
...
Selection Criteria | Option to enable or disable the archival of the process flow repository. | |
Default Value | yes | |
Possible Values | yes /no | |
| 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 |