NodeJS Server Input plugin preferences 1

The first set of NodeJS Server Input plugin preferences controls the server protocol aspects of the OL Connect Workflow NodeJS Server Input tasks. This is where you enable and configure secure communication for the NodeJS Server.

Click the OL Connect Workflow button and then the Preferences button, to open the Preferences dialog. The NodeJS Server Input 1 preferences page can be found under Plug-in.

Note: Workflow's NodeJS and ppNode folders can be found in %PROGRAMFILES%\Objectif Lune\.

  • Port: Select the port to use. The task's default port is 9090. Port numbers > 9999 are possible.
    Note that it is possible to use both the NodeJS Server and the standard HTTP Server simultaneously, provided that they are not set to listen to the same port. See HTTP Server Input plugin preferences 1.
  • Time out: Set the timeout period in seconds. The default value is 120 seconds.
  • Enable server for HTTPS requests: Check this option to accept secured, encrypted requests from web clients. The encryption protocol is TLS 1.3 (or 1.2, if the option Force outgoing encrypted connections to use TLS 1.2 or lower in the Preferences (Network behavior preferences) is checked).
    • Forward all HTTP traffic to HTTPS: When the server is enabled for HTTPS requests it doesn't listen on the port specified for HTTP anymore. However, you can enable this option to forward all HTTP traffic to HTTPS.
      Note that this option does not affect proxies. All routes set as proxy in Workflow will be forwarded to the target specified in the proxy list (see NodeJS Server Input plugin preferences 2).
  • HTTPS Port: Select the port to use. The task's default HTTPS port is 8443, so as not to interfere with the standard HTTPS port (443). Port numbers > 9999 are possible.

    Note: The Root certificate, Certificate and Key files must be in the PEM format (ASCII base64 encoded). Files in DER format, the binary encoded version of the PEM format, cannot be used to configure Workflow, although they may have the same file extension (e.g. .crt, .cer). Please check the format of your files, using a tool like: https://www.httpcs.com/en/ssl-converter.

  • Root certificate: Enter the absolute path to the Root Certificate, or click the Browse button and select the file in the Browse dialog. The file generally ends with a .crt extension.
  • Certificate: Enter the absolute path to the site Certificate, or click the Browse button and select the file in the Browse dialog. The file generally ends with a .crt extension.

    Note: If the Root Certificate and Certificate file are identical, this is considered a self-signed certificate, which is considered unsecured by most browsers.
    For more information about certificates see: Obtaining a certificate.

  • Key: Enter the absolute path to the Private Key File. This file generally ends with a .key extension.
  • Password: Enter the password (or passkey) for the Private Key File.
  • Verbose log: Select to enable to keep a verbose log. Note that a communication log is generated whether or not this option is selected. If you use a secure connection, the log will contain extra information.
  • Disable SOAP Server: Check to disable all SOAP Server functionality.