Skip to end of metadata
Go to start of metadata

On IBM i

Instance Configuration File

Profound.js instance configuration files are created by the installer on the IFS at /profoundjs-base/INSTANCE_NAME/conf. Instance configuration files can have the following directives: -

  • path - Specifies the path to the 'start.js' file in the Profound.js installation directory. This directive is set by the installer and does not normally need to be modified. However, it can be adjusted if the Profound.js installation directory is moved after installation.

  • autostart - Specifies whether or not the instance automatically starts when TCP/IP is started. The installer prompts the user for this setting and sets the directive, but it can be adjusted to change the setting after installation. Set to '1' to auto start. Set to '0' or remove the directive to disable auto start.

  • nodePath - Specifies the path to the Node.js binary/executable.This is used to select the desired version of Node.js. On IBM i, Profound.js can run on both Node.js 6 (provided by licensed program 5733-OPS) and Node.js 8  (provided by 'yum' package manager in PASE). By default, Profound.js instances run on Node.js 6 and the installer does not set this directive. The directive can be added to select Node.js 8 by setting to /QOpenSys/pkgs/bin/node.

    Note: Profound.js 4.5.0 or higher is required to use Node.js 8. Profound.js 4.6.1 is the last version that will run successfully using Node.js 6.

  • ccsid - Specifies the CCSID to be used for the submitted Profound.js server job.
    This configuration is set by the installer during upgrade/install of Profound.js version 4.8.0 or higher.

  • nodeArgs - This allows you to pass arguments to Node.js when starting your instances with STRTCPSVR command.
    Multiple arguments can be specified by separating them with a space on the same configuration line. Spaces within argument values are not supported at this time.

    e.g. To set the Node.js memory limit to 8GB: -

    Note: This configuration is available on Profound.js version 4.8.0 or higher.


Directives are specified one per line with an equal sign separating the directive name and value. Directive names are case-sensitive.



Starting Instances

Profound.js instances can be set up at installation time to start automatically when TCP/IP is started.

To start all Profound.js instances, use this command:

To start an individual Profound.js instance, use the following command:

If the instance name is something other than PROFOUNDJS, substitute the instance name for PROFOUNDJS in the above command.

Ending Instances

To end all instances:

To end an individual instance named PROFOUNDJS manually:

On your local PC or another server

To start Profound.js on your local PC or a non-IBM i server using Node, or if you have opted not to control the instance using the STRTCPSVR/ENDTCPSVR commands, use the following command from your Profound.js installation directory:

In a Unix shell or a command prompt window, you can use Ctrl-C keyboard shortcut to end the process. 

If running on Windows, see Allowing Connections in Windows Firewall

  • No labels