Page Comparison

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:

1. Login to Adeptia Connect.
2. Go to Configure Tab and click Developer Studio.
3. Click Proceed to access Developer Studio.
4. Click Administer > Setup > Application Settings > Update System Properties.
   Image Removed
   Expand Maintainance > Archive Cleanup Properties.
   Image Removed
   

   Change the value Click Account > Settings.

5. Expand Microservice Settings, and then select ArchivalAndCleanup in the left panel.
   Image Added
   

6. Expand the property category, Log Archival.
   Image Added
   

7. Change the values 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.

   
   

8. Click Save to save the changes.
9. Restart Kernel and WebRunner.

10. 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.

    
    

    Note
    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.

    
    

11. Save the file. Click Update to save the changes.
12. Restart Kernel and WebRunner. Is this step required