Adeptia Connect maintains the archival of various log files on a separate server. These archival logs file can cause issues if they accumulate over a long period of time. Adeptia Connect has an archival log cleanup task that you can schedule to run at a specific time to clean up the archived files that are older than a specified number of days. By default, cleanup of archival logs happens after 15 days. It deletes all the logs and repository files that are older than 15 days.
To configure the archival logs cleanup:
- Click Accounts > Settings.
- Expand the Server Node Settings in the left panel.
- Select the server node.
- Click Edit.
- Click
to expand Maintenance. Click
to expand Archive Cleanup Properties.Change the value of the following properties as per your need.
Property Name
Description
abpm.appmanagement.archiveLogCleanupCronExpression Define the time in the Cron expression when you want to run the archive log cleanup. For example, for 8 PM you need to define 0 0 20 * * ?. For information on Cron expression, click here. abpm.appmanagement.archiveLogCleanupPropertiesFile Define the name of the archive log cleanup properties file. archiveLog-cleanup.properties file contains the retain information about different log tables. By default, this file is located in .../AdeptiaServer-x.x/ServerKernel/etc folder. It is recommended not to change the value of this property. - Click Save to save the changes.
- Restart Kernel and WebRunner.
To change the properties of archiveLog-cleanup.properties file, go to .../AdeptiaServer-x.x/ServerKernel/etc/archiveLog-cleanup.properties file and change the properties as per your requirements. The below table shows the list of retain-time property of various logs within the log-cleanup.properties file.
Property Name
Logs
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.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. It is recommended to define same retain time for different logs to maintain the consistency within all logs. However, you can define different retain time for different logs.
- Save the file.
- Restart Kernel and WebRunner.