2018.2

NodeJS Server Input
NodeJS Server Input tasks are used to receive HTTP requests and to send replies to the
servers from which the requests were made.
Essentially this 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 is
more secure, more up to date and more standardized.
For instance:
l PUT and DELETE actions can be posted to the server
l The NodeJS Server can serve multiple static resources at once.
l Port numbers > 9999 are allowed.
l You can specify a HTTPS port separately.
l A Proxy list can be used to setup end points for redirecting requests to another server.
This could be useful if for example the Connect server is on another server which could
change; when it changes you’d only have to modify the proxy list instead of the
configuration.
The NodeJS Server is only started automatically by Workflow when NodeJS input plugins are
detected in the configuration. If no NodeJS input plugins are present, the service ("ppNode") is
not started by Workflow; it can still be started manually, but will only serve static resources and
redirect requests to other servers.
Before using this plugin
Configure the NodeJS Server using its three settings dialogs in the Preferences (Workflow
button >Preferences): "NodeJS Server Input plugin preferences 1" on page709, "NodeJS
Server Input plugin preferences 2" on page711 and "NodeJS Server Input plugin preferences
3" on page712.
Note
Although Workflow can serve both static and dynamic resources to a web browser, 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 recommended to use a common web server (for example, IIS
or Apache) to serve your contents and to let Workflow process things only it can do.
For more information on how to serve HTML and PDF generated by Connect through IIS,
Page 271