Versions Compared

Version Old Version 19 New Version 20
Changes made by

R. Cabrera

R. Cabrera

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Reverted from v. 18


Warning
  • These installation steps apply to Profound.js 6 and later versions only.
  • Profound.js 6 requires either Node.js 14, 16 or 18.

...

For a new installation (when config.js file is not present in the installation directory), the complete_install.js script will prompt you for details on how to set up the Profound.js installation. Default options are shown in parentheses after each prompt; so if the default is appropriate, you can just press Enter. The prompts are shown below:

  • Specify Profound UI static files directory (/www/profoundui/htdocs):
    This provides the location of the Profound UI htdocs folder. On IBM i, if you installed Profound UI in its default location, you can simply press Enter to accept the default. Otherwise, specify the correct location of your htdocs folder. On other types of servers, you may leave the value as the default ("htdocs"), and the Profound UI static files will automatically be downloaded into the default directory for you. 

  • Specify port number for Profound.js server (8081):
    This specifies the port number Profound.js will run from.

  • Install with Git integration (y)?
    Answer 'y' to install necessary components for Git integration features. This question only appears on supported platforms. Currently, Git integration is only supported on Windows, Linux, and Mac.

  • Install Profound.js Connector IBM i ILE components (y)?
    If you are installing on IBM i, you will have the option of installing the Profound.js Connector, which allows native IBM i applications to interface with Profound.js. You can press Enter here to proceed, or type 'n' and press Enter if you don't want to install the Connector.

...

/profoundjs-base/instances/INSTANCE_NAME

  • Specify Node.js path for instance
    This question allows you to specify an alternate Node.js binary path for the instance. The default value is the path of the Node.js binary used to run the installation process. Values such as these can be used to select alternate Node.js versions:
    • /QOpenSys/pkgs/bin/node (IBM i system default Node version)
    • /QOpenSys/pkgs/lib/nodejs14/bin/node (Node.js 14)
    • /QOpenSys/pkgs/lib/nodejs16/bin/node (Node.js 16)

  • Autostart server instance when TCP/IP starts (y)?
    Press Enter to configure the server instance to autostart when TCP/IP starts, or type 'n' and press Enter if you don't want to autostart the instance.

    Integrate with separate Profound UI

    instance

    (n)?Press Enter to continue without configuring integration with Profound UI, or type 'y' and press Enter to configure Profound UI integration.
    Profound UI instance name (PROFOUNDUI)?
    This question only appears if you answered 'y' to the above question. Enter a Profound UI instance name to integrate with. This will set the configuration settings staticFilesDirectory and profounduiLibrary to the Profound UI instance's document root directory and installation library

    .


For an upgrade installation (config.js file is present), the complete_install.js script will proceed silently by default, using the existing configuration values. That is normally the desired behavior for an upgrade installation. However, it is possible to make the script prompt for the above values and update config.js first, like this:

...