1.5

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. For
PrintShop Mail Connect the Designer is the only choice.
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).
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. PrintShop Mail 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 higher
Page 280