2019.1

The Weaver Engine is used to convert one specific job into the Print output of your choice. A
single Weaver engine can only ever convert one specific job to whatever output you want.
When you want to create output for multiple jobs in parallel, you will need to increase the
number of Weaver engines.
Too many engines will waste precious RAM and CPU cycles to idle processes, whilst too few
could create a bottleneck.
Each Weaver engine requires a speed unit from the available speed unit reservation pool. If no
speed unit is available, the job will be queued even if an engine is available.
For an explanation of the various engines, the terminology and their settings, see "Engine
configuration" on page114.
For some performance tips, see "Performance considerations" on page30.
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 Engine information:
l
Total engines available: Read-only box indicating the current number of engines
that are available.
On the main Server of a PReSConnect cluster, this would also include all engines
in the cluster (Server Extensions).
l
Local engines launched: Read-only box displaying the current number of engines
that have been launched on this machine.
It is recommended that you increase the number of Weaver engines to at least 2
engines when using the PCL, PS or AFP inputs within the DataMapper.
The amount of engines available on this machine is set in the Engine Setup
Preferences page.
l
Expected remote engines: Only available for editing on PReSConnect Server
when Clustering is active (as determined by Connect license).
l
Speed units launched: Read-only box indicating the number of speed units
launched.
Page 129