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: -

 

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

path=/profoundjs/start.js       
autostart=1                     
nodePath=/QOpenSys/pkgs/bin/node
ccsid=37

 

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:

STRTCPSVR SERVER(*PJS) INSTANCE(*ALL)


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

STRTCPSVR SERVER(*PJS) INSTANCE(PROFOUNDJS)

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:

ENDTCPSVR SERVER(*PJS) INSTANCE(*ALL)


To end an individual instance named PROFOUNDJS manually:

ENDTCPSVR SERVER(*PJS) INSTANCE(PROFOUNDJS)

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:

node start.js

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