8.6

Table Of Contents
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 1 plugin preferences
HTTP server input 1 plugin preferences control the server protocol aspects of the PReS
WorkflowHTTP Server Input tasks. This is where you enable and configure secure
communication for the HTTP Server.
Technical
By default, the request XMLalso contains a CDATAsection which contains the raw input
data, effectively doubling the size of the incoming file. Due to technical restrictions, the
incoming XMLfile cannot be more than 400MB, which because of CDATA is reduced to
around 200MB. To help in this situation, you may elect to omit CDATA from the
attachment in this dialog. Please note that this limitation also affects incoming binary files
Page 698