2021.1

The engines
DataMapper engines. A DataMapper engine extracts data from a data file. The number of
DataMapper engines is configurable (Engines preferences).
Merge engine/s. A merge engine merges data with a template using the scripts in the template,
in order to create content items.
The number of merge engines is configurable (see Engines preferences): it can be increased
depending on the capacity of the machine that runs the solution (see "Performance
considerations" on page28).
Weaver engines. A Weaver engine creates 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 Engines preferences).
Note
The Proof Print function doesn't print via the Connect Server; it uses the Designer's
internal engines.
The REST API
The Connect server receives REST commands (see The Connect REST API CookBook),
normally either via the Workflow service or from the Designer. This design allows the Connect
functionality to be used by other applications. The server forwards the commands to the
appropriate engine and returns the results to the caller. The results are the id's of the items
(records, content items, job etc.) that are stored in the Connect database (see below). All
Connect tasks except the Create Web Content task integrate the results in the Metadata in
Workflow.
The figure below shows the communication between Connect tasks and the Connect server in
a Print process.
Page 131