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
| Property name | Description |
|---|
| abpm.archive.fetchsize | Number of records to be fetched at a time from result set cursor. |
| abpm.archive.pagesize | The total number of records to be fetched by the query in a single page. |
| abpm.archive.chunksize | Number of records to be processed in each thread. All the threads run in parallel fashion. |
| abpm.logs.archival.enable | Property to enable or disable the archival of the process flow repository and logs. Set this property is to yes if you want to archive the process flow repositories and logs before they are cleaned up by the cleanup process. |
| abpm.logs.b2b.retainTime | Property that defines the retain time for EDI and non-EDI transactions/templates. |
| 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. |
| 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. |
| abpm.logs.migration.retainTime | Property that defines the retain time for migration log table. |
| abpm.logs.retainTime | Property that defines the retain time for tables other than EDI, and migration. |
| abpm.archive.logRetainTime | Property that defines the retain time for archive tables. |
| 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. |
| 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. |
Logging
| Property name | Description |
|---|
| logging.level.root | Root Application logging level. For production server, it is recommended to use NOTICE log level. |
| logging.level.system | System logging level. For production server, it is recommended to use NOTICE log level. |
| logging.pattern.console |
|
Mail Notification
| Property name | Description |
|---|
| 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. |
Others
| Property name | Description |
|---|
| abpm.log.connection.retryTimeInterval | Time interval (in seconds) after which the next retry for log database will be done. |
