2022.1

l
HTTP Data Submission: A custom application or a server sends the request to
PlanetPress Workflow using either a POST or GET command. The application or server
then waits for a response from PlanetPress Workflow.
PlanetPress 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 PlanetPress 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.
Tip
Essentially the "NodeJS Server Input" on page347 task does the same as the HTTP
Server Input task, but it uses a NodeJS Server (installed by Workflow) instead of
Workflow's custom server component. The NodeJS Server Input task is more secure,
more up to date and more standardized.
It is configured using its three settings dialogs in the Preferences (Workflow button
>Preferences).
Note
You can control access to the PlanetPress 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 the PlanetPress 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 PlanetPress Workflow. By default in most web
servers, port 80 is used and, when this is the case, it is not necessary to include it. For
Page 280