2021.2

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 Quartz Scheduler
tutorial: http://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/tutorial-
lesson-06.html.
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.
l Database Clean-up Service:
l Allow database clean-up service: Select this checkbox to enable the database
Clean-up settings, and enable the actual clean-up.
l Threads to use for database deletions: The number of Threads to be used
in the clean-up. PlanetPress Connect is a multi-threaded application, and the
clean-up is likewise.
Tip
The default number of threads is considered the best compromise for
running both clean-up and production jobs simultaneously. If experience
suggests that the clean-up is not running efficiently, then upping the
number of threads here would be recommended. Conversely, if
production appears to be suffering courtesy of the clean-up process,
then reduce the number of threads here.
In general, higher end machines (those with multiple cores) will allow a
Page 850