- Created by Rohan Dhanwade, last modified by Ashhad Alam on Jan 24, 2023
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 5 Next »
Property name | Description | Default value | Possible value |
---|---|---|---|
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 | 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. + Enable or disable Archival of Process flow log | ||
abpm.logs.b2b.retainTime | Property that defines the retain time for EDI and non-EDI. | ||
abpm.logs.db.retryErrorCodes | Comma separated error codes for which retry shall be performed in case there is any error while executing query for all tables. | ||
abpm.logs.db.skipErrorCodes | opposite of above | ||
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.logs.retryCount | Number of times the utility shall try running the delete query for all tables in case there is an error in executing it. Error codes for which retry shall be performed needs to be specified in property 'abpm.logs.delete.retryErrorCodes' | ||
abpm.logs.retryInterval | Time interval(in seconds) after which the re-execution of delete query for transaction log and transaction data tables will be performed if the first execution of the query fails. | ||
abpm.AC_AUDITTRAIL_LOG.logRetainTime | Property that defines the retain time for AC_AUDITTRAIL_LOG. | ||
abpm.archive.dataRetainTime | Defines the retain time for archive data. If the value is left blank then retain time specified for log will be taken as data retain time. | ||
| Property that defines retain time for archive log(in days) for different log solution groups. For each entry in abpm.appmanagement.log.solutionGroupNames, provide this property. Syntax is abpm.archive.solutionGroupName.logRetainTime. If this property is not specified, then default retain time of 30 days will be considered for this group. | ||
abpm.archive.logRetainTime | Defines the retain time for archive log. If the value is left blank then it takes 30 days as the default retain time. | ||
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 |
| 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 |
| Property that defines the retain time for EDI. | ||
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 |
| Enable or disable Archival of Process flow log | yes | yes or no |
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.skipErrorRecordOnArchival | Option to continue archival process in case an error occurs during archival process. Error codes for which archival process shall be continued further needs to be specified in property 'abpm.logs.archival.skipErrorCodes' | ||
abpm.logTables.archive.chunks.size | To archive data in chunks. Only positive integer will be a valid value. Use maximum value 999 in case of Oracle. | ||
adeptia.group.names | Group Names (comma separated). |
| |||
| |||
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
|
| |||
| |||
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 |
Property name | Description | Default value | Possible value |
---|---|---|---|
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 |
- No labels