2018.1

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.
l
Local engines launched: Enter the total number of Weaver Engines desired on this
server. When changing the number of engines, it is necessary to save this dialog (Apply)
to actually apply the changes.
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.
l
Speed units launched: Read-only box indicating the number of speed units launched.
l
Limit in license: Read-only box indicating the maximum number of speed units useable
for producing output.
l
Reserved Count: Read-only box indicating the total number of "Reserved" engines, as
set in the Speed unit reservations topic below.
l
Memory per engine (mb): Specify the maximum amount of random access memory
(RAM) in megabytes that will be used per engine in order to make optimal use of the
machine's memory.
Note
This setting only controls the maximum size of the Java heap memory that an
engine can use; the total amount of memory that will used by an engine is actually a
bit higher.
Also keep in mind that the Connect Server and the operating system itself will need
memory to keep running.
Page 125