Microservice Settings - ArchivalAndCleanup
The following groups contain Adeptia Connect microservices ArchivalAndCleanup properties that can be configured by going to Account > Settings > Microservice Settings. For more details on properties configuration, refer to the page Configuring the application properties.
[+] Archival And Cleanup
[-] Hide
| Property name | Description | Default value |
|---|---|---|
| abpm.archive.fetchsize | Number of records to be fetched at a time from result set cursor. | 500 |
| abpm.archive.pagesize | The total number of records to be fetched by the query in a single page. | 500 |
| abpm.archive.chunksize | Number of records to be processed in each thread. All the threads run in parallel fashion. | 500 |
| abpm.logs.archival.enable | Property to enable or disable the archival of the process flow repository and logs. Set this property to yes if you want to archive the process flow repositories and logs before they are cleaned up by the cleanup process. | yes |
| abpm.logs.b2b.retainTime | Property that defines the retain time for B2B transactions. | 0 |
| abpm.logs.db.retryErrorCodes | Error codes for which retry is performed in case an error occurs while executing the query for all the tables. You can enter multiple error code separated by comma. | 1205,60,1213,68 |
| abpm.logs.db.skipErrorCodes | Error codes for which no retry takes place in case an error occurs while executing the query for all the tables. You can enter multiple error code separated by comma. | 2627,1,1060 |
| abpm.logs.migration.retainTime | Property that defines the retain time for migration log table. | 0 |
| abpm.logs.retainTime | Property that defines the retain time for tables other than EDI, and migration. | 0 |
| abpm.archive.logRetainTime | Property that defines the retain time for archive tables. | 0 |
| abpm.logs.retryCount | The number of times the application retries running the query for log cleanup and archival in case the query execution fails. The number of times the retry happens in case of failure of execution of a query. | 5 |
| abpm.logs.retryInterval | Time interval (in seconds) after which the re-execution of query for transaction log and transaction data tables is performed if the query execution fails. | 2 |
[+] Log Database Configuration
[-] Hide
| Property name | Description | Default value |
|---|---|---|
| abpm.log.connection.retryTimeInterval | Time interval in seconds after which the next retry for log database will be done | 30 |
[+] Logging
[-] Hide
| Property name | Description | Default value |
|---|---|---|
| logging.level.root | Root Application logging level. For production server, it is recommended to use NOTICE log level. | INFO |
| logging.level.system | System logging level. For production server, it is recommended to use NOTICE log level. | NOTICE |
| logging.pattern.console | %d %-5p [%t] %5c %l - %m%n%ex |
[+] Mail Notification
[-] Hide
| Property name | Description | Default value |
|---|---|---|
| abpm.logs.sendNotification.onArchivalFailure | Option to send notification if archival process fails. | yes |