2019.1

A clean-up of the database is performed at regular intervals in accordance with the settings
(see "Clean-up Service preferences" on page993).
The File Store
Connect has its own File Store which it uses for transient files.
The Clean-up service takes care of removing obsolete files when those files are not marked as
permanent (see "Clean-up Service preferences" on page993).
Tip
The File Store is accessible for customer implementations. The Workflow configuration
tool implements three tasks that allow you to Upload, Download and Delete files in the
Connect File Store. The files can be accessed through the REST API, which means web
portals could potentially access the files directly without having to go through a Workflow
process (see The Connect REST API CookBook).
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125): it
can be increased depending on the capacity of the machine that runs the solution (see
"Performance considerations" on page30).
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128).
Note
The Proof Print function doesn't print via the Connect Server; it uses the Designer's
Page 135