8.4
Table Of Contents
- Table of Contents
- Welcome to PReS Workflow 8.4.1
- Basics
- Features
- The Nature of PReS Workflow
- About Branches and Conditions
- Configuration Components
- Connect Resources
- About Data
- About Documents
- Debugging and Error Handling
- The Plug-in Bar
- About Printing
- About Processes and Subprocesses
- Using Scripts
- Special Workflow Types
- About Tasks
- Task Properties
- Working With Variables
- About Configurations
- About Related Programs and Services
- The Interface
- Copyright Information
- Legal Notices and Acknowledgements
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 HTMLfile 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
HTTPServer Input task, as they will greatly impact how this process responds. In the process' properties,
the following options will modify HTTPbehavior:
l Self-Replicating Process:This option is critically important when dealing with HTTPprocesses, so
check it now. Basically, this means that when HTTPrequests 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 520 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 HTTPServer 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 HTTPServer Input task properties. While these are described in the "HTTP Server Input"
on page 173 task properties page, here are a few considerations to keep in mind when using this task:
l The HTTPAction 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 HTTPservice accepts both POSTand GETrequests. 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 XMLenvelope that is the original input file.