2018.2

Note
Changes made to these settings will be applied on the run. Existing jobs will
be taken into account when determining if a job can run.
For instance, if the minimum records for a Large job is increased from 1,000 to
10,000 and a job of 2,000 records is already running, then this existing job will
now be considered a Medium job.
Likewise, if the minimum records for a Large job is decreased from 10,000 to
5,000 and a job of 7,000 records is already running, then this existing job will
now be considered a Large job.
All Server scheduling is actually handled in the Master Server.
Scheduling preferences per engine
Scheduling preferences can be applied to the distinct engines used in the Connect production
process. A DataMapper engine extracts data from a data file.A Merge engine merges the
template and the data to create Email and Weboutput, or to create an intermediary file for
Printed output. The intermediary file is in turn used by a Weaver engine to prepare the Print
output.
Each of these engines has its own Scheduling Preferences page. These are as follows:
l "Merge engine scheduling" below
l "Weaver engine scheduling" on page127
Merge engine scheduling
A DataMapper engine extracts data from a data file.A Merge engine merges the template and
the data to create Email and Weboutput, or to create an intermediary file for Printed output. The
intermediary file is in turn used by a Weaver engine to prepare the Print output.
This preferences page defines how many Merge engines are launched and how speed units
are allocated to different jobs when creating production output. By default the number of Merge
engines is set to two.
You can confirm how many Merge engines are running by checking Task Manager and
Page 124