2021.1

l <protocol>: Sets the communication protocol and has to be either HTTP or HTTPS. Any
other setting is invalid. As soon as HTTPS is set as protocol, the communication will
automatically run in protected mode (SSL).
Tip
For additional information about secure file transfer, HTTPS certificates and how to
request a countersigned certificate, please see this page: SSL HowTo.
l <host>: The host name or IP address of the target machine. This is either the computer
where the related Connect Workflow is running or a gateway machine.
l
<port>: The port entry is mandatory, even if the port should be one of the standard ones
(80 for HTTP or 443 for HTTPS).
l <path>: Optional additional URL path components.
l <http action>: The HTTP action name as defined in the related Workflow HTTP Input
plugin.
The Test button can be used to check if the URL is pointing to a machine with a correctly set up
Connect Workflow with a HTTP Input plugin and the OLCS Job Processor plugin.
If the test was successful, and the response status code is 200 OK, this will be indicated by the
green text "Server for job submission is ALIVE", "Interaction server is ALIVE". If there was no
response from the server, the message will be that the respective server "is DOWN, no
response from server". If there is a response from the server, but the response status code is not
200 OK, the response status code of the HTTP request will be given.
By unchecking Interactive mode you can set this specific printer to only send jobs to the
server, without further user interaction. In that case, the printer will not pop up a browser
window. Nevertheless, messages will pop up in the tray area, informing about transfer, success
or failure.
When the Interactive mode is disabled, the HTTP action for interaction field also becomes
disabled.
Accept all certificates: By default, if HTTPS is set as protocol (see above), the Printer Driver
will only accept valid certificates on the server side for the transfer. However in some cases a
self-signed certificate may be seen as sufficient for the transfer, e.g. during development and
testing, or when the server doesn't have a public address that can be known by (Root)
Page 20