2018.1

used by default is to prevent any interference with existing web servers installed or
activated on the same server as PReS Workflow.
l
Time-out (seconds): This determines how long the HTTP Server service will wait for the
process to finish, before returning a time out error back to the client browser. This means
that if a process takes more than 120 seconds (by default) to complete, the browser will
time out. While you can change this value, it is recommended to always keep your
processing to a minimum, since both browsers and users generally frown upon being
stopped for more than a minute, unless they are well aware of this processing time (and
even then...)
l
Enable server for SSL requests: This enables secure communication between the
browser and the server via HTTPS. By enabling this option, you will need to provide for
the proper certificates, key and password. While this configuration is beyond the scope of
this document, there are plenty of resources on the Internet to explain these systems.
l
Serve HTTP resources: This is where you enable static resources in PReS Workflow.
When enabling this option, the HTTP server will always look in the Resource Folder for
files requested inside of the Resource action name as a folder. This means that, if your
Resource folder is c:\PReS\http and your Resource action name is static,
pointing your browser to http://127.0.0.1:8080/static/css/style.css will
immediately load and return the file c:\PReS\http\css\style.css . This does not
require any process to work - everything is handled directly by the HTTP Server Input
and files are returned immediately. This feature is very useful when dealing with
stylesheets, images, browser JavaScript, or static html files that do not require any
processing.
Note
As of PReS Workflow 8.1, it is possible to serve a default HTML file when no action is
specified, for example http://localhost:8080/ . This is done by creating an index.html
file in the Resource Folder defined above. However, resources called by this
index.html must still use the Resource action name, for example a stylesheet would
still point to http://127.0.0.1:8080/static/css/style.css or more simply
static/css/style.css.
You also need to take into consideration the options inside each of your processes that start
with the HTTP Server Input task, as they will greatly impact how this process responds. In the
process's properties, the following options will modify HTTP behavior:
Page 177