Review and Configure Retention Policies
File storage in the cloud might be constrained so it’s important to proactively manage limited file storage services by purging old instances and payloads.
In order to keep your database and storage resources from filling up, periodically purge artifacts from previous transfers. By default, Oracle Managed File Transfer Cloud Service checks daily at 8:00 AM for files that have been around longer than seven days and purges any that it finds. You can change these default values to suit your needs. How often you purge depends on your usage as does the length of time you retain the artifacts.
The tasks in the following topics describe how to change the retention value and the schedule.
Change the Purge Retention Policy
If you want to change the length of time you retain transfer artifacts
such as old instances and payloads, edit the purgeInstanceData.py
file
located on each MFT managed server.
Change the Purge Schedule
By default, Oracle Managed File Transfer Cloud Service checks daily at 8:00 AM for files that have been around longer than the retention value and purges any that it finds. You can change the schedule to suit your needs. How often you purge depends on your usage.
To read more about running Oracle Enterprise Scheduler WLST commands, see "Oracle Enterprise Scheduler Custom WLST Commands" in WLST Command Reference for SOA Suite (12.2.1.4 | 12.2.1.3 | Oracle 12.2.1.2 | Oracle 12.1.3).
To read more about using Oracle Enterprise Manager to monitor Oracle Enterprise Scheduler jobs, see "Managing Oracle Enterprise Scheduler Requests" in Administering Oracle Enterprise Scheduler. (12.2.1.4 | 12.2.1.3 | 12.2.1.2 | 12.1.3).