2019.1

concurrently, the number of engines in use may not match the number of available speed units.
When there are more speed units than there are engines in use, the Connect server distributes
the speed units and the maximum output speed to the engines proportionally.
For advice on engine settings and performance, see "Engine configuration" on page114 and
"Performance considerations" on page30.
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.
Printing and emailing from the Designer
To print or send email from within the Designer, the Connect service has to be running. The
service is started automatically when the Designer starts, but it may not be running if the
Connect Server and the Designer are installed on different computers. The Connect service
can be found on the Services tab in the Task Manager.
Page 155