| Warning |
|---|
|
...
| Code Block | ||
|---|---|---|
| ||
cd / mkdir profoundjs cd profoundjs npm install profoundjs@beta |
Warning Messages
...
Profound.js is provided as an npm package hosted on npmjs.com. When installing npm packages into a directory that does not have a package.json file to describe your project, npm produces several warning messages that look like this:
|
These warning messages do not mean that the installation failed. They simply mean you did not have a package.json file to descibe your project.
If a package.json is not found, the Profound.js installation will create a default package.json file in your installation directory for you. You can then maintain this file to keep track of your project's version, description, other npm dependencies, and more. For more information about the npm package.json file, click here.
Completing the Installation
...
| Code Block | ||
|---|---|---|
| ||
node complete_install.js |
The For a new installation (when config.js file is not present in the installation directory), the complete_install.js script will prompt you for details on how to set up the Profound.js installation. Default options are shown in parentheses after each prompt; so if the default is appropriate, you can just press Enter. The prompts are shown below:
...
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.
When the process completes, a message like this will display on screen:
Warning Messages
Profound.js is provided as an npm package hosted on npmjs.com. When installing npm packages into a directory that does not have a package.json file to describe your project, npm produces several warning messages that look like this:
|
These warning messages do not mean that the installation failed. They simply mean you did not have a package.json file to descibe your project.
If a package.json is not found, the Profound.js installation will create a default package.json file in your installation directory for you. You can then maintain this file to keep track of your project's version, description, other npm dependencies, and more. For more information about the npm package.json file, click here.For an upgrade installation (config.js file is present), the complete_install.js script will proceed silently by default, using the existing configuration values. That is normally the desired behavior for an upgrade installation. However, it is possible to make the script prompt for the above values and update config.js first, like this:
| Code Block | ||
|---|---|---|
| ||
node complete_install.js --configure |
When the process completes, a message like this will display on screen:
If this message does not appear, then the installation is NOT complete.
Troubleshooting the Installation
...
To troubleshoot, review all messages on screen and in the installation log file. If the cause of the problem is not clear, contact Profound Logic Support at support@profoundlogic.com and provide ALL the messages from the screen along with a copy of the installation log file.
If errors occurred during the Completing the Installation step, then the installation is NOT complete. After resolving any problems, run run node complete_install.js again to complete the installation.