2018.1

Table Of Contents
HTTP Server Workflow
An HTTP Server workflow is one that has one or more processes that always start with the
HTTP Server Input task and returns something to a client using a web browser. Each process
would have a specific task referred to as an "action", called from the browser itself.
HTTP Server Input tasks are typically used in one of the two following situations:
l
HTML Form Action: An HTML Form in the browser that may contain text and attached
files can be filled and sent to a process with the HTTP Server Input task.
l
HTTP Data Submission: A custom application or a server sends the request to PReS
Workflow using either a POST or GET command. The application or server then waits for
a response from PReS Workflow Tools.
PReS Workflow can serve both static and dynamic resources to a web browser, however it is
not meant to be used as a fully featured web server, as it is not built for responsiveness nor
guaranteed uptime. It is much better to have a common web server (for example, IIS or Apache)
to serve your contents and to have PReS Workflow available only to process things only it can
do. For more information on how to serve HTML and PDF generated by Connect through IIS,
watch the Connect with Evie - IIS series.
Note
You can control access to the PReS Workflow Tools HTTP Server via the Access
Manager.
Important Configuration, Setup and Options
Before starting to work with HTTP workflows, there are a few key points to keep in mind in
terms of configuration. First of all, the following options are available in PReS Workflow
Preference screen, under the HTTP Server Input 1 and HTTP Server Input 2 sections:
l
Port (default value: 8080 recommended): The port number is the one in which a
browser needs to make a request to PReS Workflow. By default in most web server, port
80 is used and, when this is the case, it is not necessary to include it. For example, if I
type http://www.objectiflune.com/ in my browser, it is actually accessing the address
http://www.objectiflune.com:80/ , but port 80 is always hidden. The reason port 8080 is
Page 176