Adeptia Suite keeps application logs/errors in log files and/or database based on the logging properties. These logs are used for viewing process flow logs and for debugging and troubleshooting. Adeptia Suite keeps process flow reports in the log database tables.
These logs can cause database issues if they accumulate over a long period of time. Adeptia Suite has Log Cleanup task that is scheduled to run at a specified time to clean up the repository logs older than specified number of days. This cleans unnecessary logs from server's hard disk.
By default, Log Cleanup is enabled and runs automatically at 3 AM daily. To change this time, you need to set the value in the abpm.appmanagement.logCleanupCronExpression property in the form of cron expression. At any point of time, you may choose to run the data and log clean-up instantly/manually as well.
By default, the logs older than 5 days are deleted during the Log Cleanup process. You can change the retain time for various logs such as Event Logs, Process Flow Logs, and many more. To change the retain time for various logs:
- Go to .../AdeptiaInstallFolder/AdeptiaServer-x.x/ServerKernel/etc.
- Open log-cleanup.properties file in the text Editor.
Change the retain time of the property associated with the particular log. The properties associated to various logs are:
Property Name
Logs
abpm.AU_LOG.logRetainTime
System Logs, Audit Trail Logs and Process Flow Logs
abpm.AU_TRANSACTIONDATA.logRetainTime
Process Flow Logs
abpm.AU_EVENTLOG.logRetainTime
Event Logs
abpm.AU_TASKLOGS.logRetainTime
Task History
abpm.AU_PROCESSVARIABLETRACKER.logRetainTime
Solution Dashboard
- To know how to change Adeptia Suite Properties, refer to Updating System Properties.
- Log Cleanup does not delete logs of those process flows that are in running/waiting state.
There are some folders, to store temporary data, are also get cleaned up either after successful execution of process flow or during log cleanup. The following table list the location, purpose of the folder, and the time when the folder gets cleaned.
Location | Purpose | Cleanup Process |
ServerKernel/web/Repository | Use to store repositories created during process flow execution | Cleaned during daily log cleanup |
ServerKernel/web/Archive | Use to store the repository cleaned during data cleanup | Cleaned during Archive log cleanup |
ServerKernel/web/Attachments | Use to store the web service and MIME/binary attachment files | Cleaned during daily log cleanup |
ServerKernel/logs/applicationlogs | Use to store the logs of process flow execution, activity creations and modification | Cleaned during daily log cleanup |
ServerKernel/web/edi | Use to store the source and target files displayed in the EDI logs FileIn and FileOut links | Cleaned during daily log cleanup |
ServerKernel/web/Archive/edi | Use to store the source and target files displayed in the EDI logs FileIn and FileOut link after cleanup | Cleaned during Archive log cleanup |
ServerKernel/web/routing | Use to store the source and target files displayed in B2B (Non-EDI) logs FileIn and FileOut links | Cleaned during daily log cleanup |
ServerKernel/web sapIdocLocation | Use to store the IDoc files, received by Adeptia Suite | Cleaned during daily log cleanup |
ServerKernel/temp Repository | Use to store the intermediate files during process flow execution | Cleaned after process flow execution |
ServerKernel/Recovery | Use to store the process flow intermediate files requires to re-execute the process flow if process flow aborted due to system failure | Cleaned automatically after successful execution of process flow after restarting the build |
ServerKernel/Re-processing | Use to store the process flow intermediate file requires to re-execute the process flow if process flow aborted due to the manual error | Cleaned automatically after successful execution of process flow |
Overview
Content Tools