Versions Compared

Version Old Version 7 New Version 8
Changes made by

David Russo

David Russo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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

...

On IBM i, this is done using a PASE shell (not QShell). The best way to use a PASE shell is to connect to your IBM i server via SSH using a Unix-style terminal emulator, such as PuTTY or Git Bash for Windows. This provides a friendlier interface for working with Node.js and other Unix-style commands on the command line. For more information on configuring SSH, follow this link: https://wiki.midrange.com/index.php/SSH. Alternatively, you can start a PASE shell from a TN5250 session by running the command CALL QP2TERM.

Once you are on a shell command line, there are a few simple commands that will start the installation.

...

The next step is to enter the directory (using the cd command) and run the Node Package Manager (npm) install process for Profound.js using the command "npm install profoundjs@beta". This will download all package dependencies and install the product.

...

  • 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.js 14)
    • /QOpenSys/pkgs/lib/nodejs16/bin (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.

...