2022.1

Messenger plugin preferences
Apart from enabling communication between the various parts of PReS Workflow, the PReS
Workflow Messenger also manages local instances of the PReS Workflow Alambic.
The Messenger service uses the SSL 2.3 protocol.
Preferences
l
PReS Alambic options group
l
Let me set up how many instances to run: Select this option if you want to limit
the number of instances of the Alambic that PReS Workflow can run. Then enter the
number of instances, a value ranging from 1 to 32, in the box below. When this
option is not selected, PReS Workflow starts a minimum of three instances and a
maximum of eight, based on the number of CPUs available on the server. Note that
this does affects self-replicating processes. Self-replicating processes will create
threads in PReS Workflow service, while Alambic threads are under the PReS
Messenger service.
l
Close inactive instances after: If you want the PReS Workflow Messenger to close
inactive instances of the Alambic after a given number of minutes, enter a value in
this box. Enter a value of ”0” if you do not want the Messenger to terminate idle
instances of the Alambic.
l
Logging options group
l
Delete log files after: Enter the number of days after which to delete the Messenger
service logs. Each log covers a 24-hour period and is kept in the Log folder, which
is located in the installation folder.
l
Verbose log: Select this option if you want the log to contain a maximum amount of
information.
HTTP Server Input plugin preferences 1
The first set of HTTP Server Input plugin preferences controls the server protocol aspects of
the PReS Workflow HTTP Server Input tasks. This is where you enable and configure secure
communication for the HTTP Server.
Page 798