Installing Foresight Analytics Platform web application in Linux OS is executed using a special script, which automatically installs web application components using PostgreSQL.
The script is available for the following Linux OS versions:
install_astrase1.7.sh for Astra Linux SE 1.7.
install_astrase1.8.sh for Astra Linux SE 1.8.
install_redos7.3.sh for RED OS 7.3.
install_rocky8.sh for Rocky Linux 8.
install_alt10.sh for ALT Linux 10.
NOTE. To get the script, contact technical support by sending a request to support@fsight.ru or use technical support services, which are available after registration at the website.
To install the web application:
Grant access permissions to execute the script as the root user. Specify script name without extension according to OS version instead of the <script name> substitute:
chmod +x <script name>.sh
The example of the command for Astra Linux SE 1.8:
chmod +x install_astrase1.8.sh
Run the script. Specify script name without extension according to OS version instead of the <script name> substitute:
./<script name>.sh
NOTE. The script contains predefined parameters of the web application with default values. See the list of web application parameters and if required replace default values before running the script.
After executing the operation the "dialog" utility is installed to display the installation graphic interface, and the dialog box opens for selecting web application component setup type.
Select the web application component setup type:
Complete. Automatic installation of all web application components except for license server and designer of business applications:
Install all components (PostgreSQL DBMS).
Custom. Manual selection of components to be installed:
BI server with a PostgreSQL client.
Web server.
BI server and web server with a PostgreSQL client.
PostgreSQL DBMS.
License server.
NOTE. License server is installed via RMS. To install a Guardant-based license server, see the Guardant License Server and Features of Its Use section.
Designer of business applications.
NOTE. Before installing the designer of business applications one should install all web application components, the Designer of Business Applications extension in the repository, and create a business application in the object navigator. To execute the script, change values of the METABASE_ID and DBA_ID parameters.
After executing the operations, web application components are installed depending on the selected setup type:
| Component | Result |
| PostgreSQL DBMS back end | After one of the following setup types is selected: Install All Components (PostgreSQL DBMS), BI Server with PostgreSQL Client, BI Server and Web Server with PostgreSQL Client or PostgreSQL DBMS, a PostgreSQL repository will be added for the OS in use and PostgreSQL 11 will be installed. |
| BI server | After one of the following installation types is selected: Install All Components (PostgreSQL DBMS), BI Server with PostgreSQL Client or BI Server and Web Server with PostgreSQL Client, the directories will be created:
When installing BI server, a request is formed to get computer locking code to create a perpetual license. If the answer is Yes, the computer locking code is displayed and saved to the locking_code.txt file. The file is created at the script level. Features of BI server installation:
If required, execute the command to manage BI server:
sudo systemctl start/restart/stop apache2-fp10.x
sudo systemctl start/restart/stop httpd-fp10.x
sudo systemctl start/restart/stop httpd2-fp10.x |
| Web server | After one of the following installation types is selected: Install All Components (PostgreSQL DBMS), Web Server, or BI Server and Web Server with PostgreSQL Client, the directories will be created:
If required, execute the command to manage web server:
sudo systemctl start/restart/stop apache2-fp10.x-web
sudo systemctl start/restart/stop httpd-fp10.x-web
sudo systemctl start/restart/stop httpd2-fp10.x-web The web server is available at: http://<IP address or DNS server name>:8110/fp10.x/r/ |
| License server | After the License Server setup type is selected, the following will be created:
If required, execute the command to manage the license server: sudo systemctl start/restart/stop lserv64 |
| Designer of business applications | After selecting the Designer of Business Applications installation option the following folders are created:
If required, execute the command to manage the designer of business applications:
sudo systemctl start/restart/stop apache2-fp10.x-dba
sudo systemctl start/restart/stop httpd-fp10.x-dba
sudo systemctl start/restart/stop httpd2-fp10.x-dba The designer of business applications is available at: http://<IP address or DNS server name>:8210/dba/ |
The web application works via the HTTP protocol by default. To set up web application work via the HTTPS protocol, see the Setting Up Web Application to Work via HTTPS section.
To change web application parameter values that should differ from default values, open the script for edit. Web application parameters are used as variables in the following script block:
############## Variables that can be changed
# Licensing type - the LSFORCEHOST variable in the file /opt/foresight/fp10.x-biserver/etc/envvars
SET_LSFORCEHOST="NO-NET" # to determine a license application order (stand-alone or network)
# Repository identifier
METABASE_ID="ANALYTICS_PLATFORM"
# IP address or DNS name of DBMS server database
DATABASE_SERVER="127.0.0.1"
# DBMS server port
DATABASE_PORT=5432
# Number of DBMS connections
MAX_CON=500
Configuration of the pg_hba.conf user authentication file.
PG_HBA_CONNECTION_STRING="host all all 0.0.0.0/0 md5"
# File with repository source data
REPO_FILE="./fp_repo/scheme.sql"
# Credentials of PostgreSQL administrator role
PG_ADMIN_ROLE=postgres
PG_ADMIN_PASSWORD=postgres
# Credentials of schema owner
OWNER_METABASE_ROLE=FP_ADMIN
OWNER_METABASE_PASSWORD=FP_ADMIN
# Credentials of service user
SEC_ROLE=AUDIT
SEC_PASS=AVbGm86ugD9tpBjK577NPHgw
# BI server URL if BI server and web application back end are located on different physical servers
BI_SERVER="localhost"
# Database identifier
METABASE_DBNAME="ANALYTICS_PLATFORM"
# Directory containing BI server and web server distribution files
FP_DIST_DIR="./fp-dist"
# Directory containing license server distribution files
LSERV_DIST_DIR="./fp-lic-dist"
# Log file of installation process
LOG_FILENAME="fp-install.log"
# Business application identifier
DBA_ID=OBJ224
Description of variables:
SET_LSFORCEHOST. Method for searching license:
If the license server is not installed, specify NO-NET as a variable value to search a stand-alone license. It is used by default.
If the license server is installed, specify license server name in the variable value to search for a network license.
METABASE_ID. Unique repository identifier. Default value: ANALYTICS_PLATFORM.
DATABASE_SERVER. IP address or DNS name, under which the DBMS database server is registered. Default value: 127.0.0.1.
DATABASE_PORT. DBMS server port. Default value: 5432.
MAX_CON. Number of DBMS connections. The PostgreSQL/Postgres Pro configuration file contains basic settings by default. This parameter changes the value of max_connections. Recommended number of DBMS connections - 500.
PG_HBA_CONNECTION_STRING. Configuration of the pg_hba.conf user authentication file. Default value: host all all 0.0.0.0/0 md5, authentication is available for any user by means of login and password.
REPO_FILE. Path to the scheme.sql file with repository source data. Default value: ./fp_repo/scheme.sql.
PG_ADMIN_ROLE. DBMS administrator name with the SUPERUSER privilege. Default value: postgres.
PG_ADMIN_PASSWORD. DBMS administrator password. Default value: postgres.
OWNER_METABASE_ROLE. Name of created database user. Default value: FP_ADMIN.
OWNER_METABASE_PASSWORD. Password of created database user. Default value: FP_ADMIN.
SEC_ROLE. Name of created service user. Default value: AUDIT.
NOTE. The P4AUDIT service user name is reserved by the system and cannot be used.
SEC_PASS. Password of created service user. Default value: AVbGm86ugD9tpBjK577NPHgw.
BI_SERVER. IP address or DNS server name, on which BI server is installed. It is used if BI server and web application back end should be located on different physical servers. Default value: localhost.
METABASE_DBNAME. Identifier of created database. Default value: ANALYTICS_PLATFORM.
FP_DIST_DIR. Path to the folder with BI server and web server distribution files. Default value: ./fp-dist.
LSERV_DIST_DIR. Path to the folder with license server distribution files. Default value: ./fp-lic-dist.
LOG_FILENAME. Name of a *.log file that will be used for logging during web application installation. Default value: fp-install.log. The file is created at the script level.
DBA_ID. Identifier of business application in the object navigator.
See also: