/
Replicating a Profound.js Instance (IBM i)

Replicating a Profound.js Instance (IBM i)

Overview

This page lists what must be replicated in order to reproduce a working Profound.js instance on another IBM i system, for example when using a high-availability product to maintain a backup system.

Do not replicate the /profoundjs-base/key file if it exists. License keys are system specific and only work on the system the key was issued for. Apply a key for the target system instead (see Applying License Keys for Profound.js).

Profound.js Objects to Replicate

  1. The entire /profoundjs-base directory structure on the IFS, excluding the key file noted above;

  2. The PJS_BASE library;

  3. The PROFOUNDJS user profile;

  4. The QUSRSYS library – the definition of the *PJS server type used by STRTCPSVR/ENDTCPSVR is stored in table QATOCSTART in this library;

  5. Any Profound.js installation directories on the IFS – these are the directories the npm install profoundjs command was run from;

  6. Any Profound.js Connector libraries – these are prompted for during installation and default to PROFOUNDJS.

Profound UI

We also recommend replicating the Profound UI installation associated with the instance. Profound.js relies on some components installed with Profound UI, and the installer prompts for the library where Profound UI is installed.

Replicate the Profound UI instance that corresponds with the library given during the Profound.js installation (see Replicating Profound UI).

Replication Software

If you use MIMIX or other replication software, see MIMIX and Replication Software for known installation issues.