8.5

l
Log level group
l
Startup and shutdown: Select to only track when the PReS Workflow service is started and
stopped.
l
Task failure: Select to only track when tasks in the processes running in a PReS Workflow
configuration fail.
l
Task success and failure with details: Select to track when the tasks in processes running in
PReS Workflow succeed and fail, with details. Details can include why tasks fail and how
successful tasks are executed.
l
All events with details: Select to log everything that happens in PReS Workflow. This includes
when it starts and stops, the success and failure of tasks, and details on the success and failure
of tasks.
l
Add time stamp to all processes events:
l
Delete log files after: Select how many days log files are kept before being deleted.
l
Maximum numbers of replicated processes:
Messenger Plug-In 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.
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.