2020.1

l
Self-Replicating Process: This option is critically important when dealing with HTTP
processes. 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847 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
new request. This should be put at 0 in order to process requests as soon as possible,
meaning immediately.
And finally, the HTTP Server Input task properties. While these are described in the "HTTP
Server Input" on page328 task properties page, here are a few considerations to keep in mind
when using this task:
l
The HTTP Action corresponds precisely to the name immediately following the first slash
of your address. That is to say, placing the action myaction here means the process
would be triggered by opening http://127.0.0.1:8080/myaction in your
browser.
l The HTTP service accepts both POST and GET requests. Other than the presence of file
attachments, there is little difference in how these are handled. This means that visiting
/myaction?id=12345&q=test would be the same as having a form with two <input>
fields named, respectively, id and q, and submitting them with the information "12345"
and "test". In both cases, this information is located in the XML envelope that is the
original input file of a process that starts with a Server Input task.
l When doing POST requests and uploading files, always make sure to include the
"multipart" option in the <form> tag:
<form action="http://127.0.0.1:8080/myaction" method="POST"
enctype="multipart/form-data">
Otherwise, file attachments will not be received, only their file names.
l The Mime Type option is better left at Auto-Detect unless the process requires it to be
forced to a specific type. This means that if a process can either return a PDF when
successful or an HTML page with an error message, it will not attempt to send an HTML
with a PDF mime type (which, obviously, would cause confusion).
l
There is no HTTP Server Output task (see below on how to end your process)
Page 280