Page tree
Skip to end of metadata
Go to start of metadata

The Profound.js installer can be used to create multiple Profound.js instances. For example, you may want a Production Instance, a Development Instance, and a QA Instance.

You can install these different instances by creating separate directories and running the 'npm install profoundjs' command from within the different directories. You should select a different port number for each instance.

The Profound UI static files directory can either be shared between different instances, or a separate directory (Profound UI installation) can be setup for each instance.

When installing Profound.js on IBM i, it is recommend that you select a unique name the Profound.js Connector library and instance when prompted. The Profound.js installer will create both a base library and an connector/instance library as shown below:

PJS_BASE library

This library will contain a lot of the core IBM i objects for running Profound.js:

/profoundjs-base directory

This directory will contain a logs folder for each Profound.js instance, which will contain stderr / stdout log files pertaining to each instance:

<PJS Connector Library>

The library specified on install (in this case PJS_INST1) will be created, and will contain copies of the objects required to run each individual instance:

When calling Profound.js modules from an interactive Genie session, this library should be added to the session's library list.

Profound.js Environment Variables in a Genie session

Environment variable PROFOUNDJS_COMM_HOST and PROFOUNDJS_COMM_PORT specify which instance to connect to when calling Profound.js modules from a Genie session.

For more information on how to setup Genie for calling Profound.js modules and how to configure these environment variables, click here.

  • No labels