2018.1

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 Web output, 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
locating the mergeengine.exe entries in your process list.
Note: there will be an extra Merge and Weaver engine in your task manager if you run
Designer.
The Merge engine is responsible for the plugins Create Print Content, Create Email Content
and Create Web Content.
License restrictions only apply to the Merge engine when creating Email or Web content. They
do not apply for Create Print Content. This means you are allowed to start an infinite amount of
Merge engines on any given Connect Sever to run print jobs, but you will be restricted to a set
number of Merge engines for your Email and HTML jobs.
For an explanation of the various engines, the terminology and their settings, see "Engine
configuration" on page108.
For some performance tips, see "Performance considerations" on page27.
Note
Changes made to the following settings will be applied on the run (when the Apply button is
pressed), and do not require the OLConnect_Server service to be restarted.
l
Use one internal engine: Check this option to limit to a single internal engine. Only use
this option on computers that run below the recommended System requirements, or demo
machines. With external engines, both the engines and the server have more memory
and can run faster.
l
Total engines available: Read-only box indicating the current number of engines that are
active or available.
Page 120