1.5

(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.
Note
If the Product managing the service is set to Designer, then the Designer must be
running at the time that the cron job is scheduled, for the clean-up to run.
l
Product managing the service: Select which of the applications will run the service.
Note
The Server Engine is set as the default as it is generally considered the best
option.
This is particularly the case when using a scheduled cron job, as the Sever Engine
is always running, whilst the Designer might well not be at the scheduled time (in
which case the clean-up will fail to run).
Page 575