8.6

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.
Technical
As of PReS Workflow 8.1, it is now 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' properties, the following options will modify HTTPbehavior:
l Self-Replicating Process:This option is critically important when dealing with
HTTPprocesses, so check it now. Basically, this means that when HTTPrequests are
received, the process will duplicate itself up to the specified maximum number, in order to
simultaneously (and asynchronously)handle multiple requests. See " Process
Properties" on page651 for more details.
l As soon as possible:This option needs to be checked, otherwise requests will not be
handled as they come in (this option is meant to be used on scheduled processes that run
at intervals).
l Polling Interval (sec):This option determines how much time the HTTPServer Input
waits between the moment it finishes processing a request and the moment it picks up a
Page 174