1.6

Cleanup Service preferences
The Clean-up Service defines how the Connect database and the "managed" temporary files
(referenced within said database) created during Connect production runs are cleaned up after
the production run has finished. The "managed" files include temporary data files, configuration
files and intermediate files created during the production process. They are longer be needed,
once the run has completed.
The values below define when the specified targets are to be set as ready for deletion, not
when they are actually deleted. The actual deletion occurs only when PlanetPress Connect is
started (if Run at application start up is selected), or when the Run Now button is pressed, or
as per the cron job scheduling.
Tip
The more items present in the database, and the larger they are, the more time and processing power
(CPU) that is required in cleaning them up. Thus a regular clean-up of the database (as often as
possible)is recommended. This is especially the case if items are not going to be retrieved from the
database at a later date. i.e. If the Connect job is not going to be re-run.
The clean-up can always be set to run outside of business hours (see the Run according to the
cron schedule option below), to reduce impact upon Production systems.
l
Enable clean-up service: Check to enable the clean-up services. When checked, either
or both of the Database clean-up and File clean-up services can be set individually.
If the box is not checked, then no clean-up will occur.
l
Run at application start up: Click to start the clean-up service when the Designer
module is opened, or the Managing Service is started.
l
Run according to the cron schedule: Enter the interval at which the clean-up service
runs.
To understand how to write a cron job schedule, please refer to the excellent Quartz
Scheduler reference page.
Page 589