2018.2

The engines
DataMapper engine/s. A DataMapper engine extracts data from a data file. The number of
DataMapper engines is configurable (DataMapper Engine Scheduling).
Merge engine/s. A merge engine merges data with a template using the scripts in the template,
in order to create (Print,Email or Web) content items.
The number of merge engines is configurable (see "Merge engine scheduling" on page124): it
can be increased depending on the capacity of the machine that runs the solution (see
"Performance considerations" on page31).
Weaver engine s. The Weaver engines create Print output from Print content items. It takes the
settings made in Print presets or in the Print Wizard into account.
The number of Weaver engines is configurable as well (see "Weaver engine scheduling" on
page127).
Note
The Proof Print function doesn't print via the Connect Server; it uses the Designer's
internal engines.
Speed units
The number of 'speed units' is the maximum number of Merge engines or Weaver engines that
are allowed to work in parallel. The output speed of all engines together is limited to a certain
number of output items (web pages, emails, or printed pages) per minute. How many speed
units you have and what the maximum total output speed will be is determined by your licence
and any additional Performance Packs you might have.
There is one important twist: when generating Print output, the limit imposed by the number of
speed units, only applies to the Weaver engines; when creating Emailor Web output, the limit
applies to the Merge engines only (the Weaver engine is not involved). Nevertheless, in
situations where Print and Email or Web output are being created at the same time, all Merge
engines and Weaver engines count towards the maximum number of speed units. (DataMapper
engines are not taken into account.)
Each Merge engine and each Weaver engine needs at least one speed unit. However, since
the number of engines is configurable, and since small, medium and large jobs may run
Page 150