Installing Foresight Analytics Platform Web Application on Linux OS (PostgreSQL DBMS)

Installing Foresight Analytics Platform web application in Linux OS is executed using a special script, which automatically installs web application components using PostgreSQL.

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.

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.

NOTE. Before installing all web application components select the Licman Licensing Service and Guardant License Server installation option. If the licensing service and license service have been already installed, change the LICMAN_SERVER variable if required.

NOTE. License server setup is executed manually. If the license server has been already installed, change the GUARDANT_SERVER variable if required.

After executing the operations, web application components are installed depending on the selected setup type:

Changing Web Application Parameter Values

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

# 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 licensing service and license server distribution files

LSERV_DIST_DIR="./fp-lic-dist"
LICMAN_SERVER="localhost"
GUARDANT_SERVER="localhost"

# Log file of installation process

LOG_FILENAME="fp-install.log"

# Business application identifier

DBA_ID=OBJ224

Description of variables:

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 configuration file contains minimum 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 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 licensing service and license server distribution files. Default value: ./fp-lic-dist.
LICMAN_SERVER. IP address or name of the DNS server, on which licensing service is installed. Default value: localhost.
GUARDANT_SERVER. IP address or name of the DNS server, on which license server is installed. Default value: localhost.
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.

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 DBMS 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: /opt/foresight/fp10.x-biserver. Main files of BI server. /etc/apache2-fp10.x. Configuration files of the Apache2 instance with BI server for Astra Linux. /etc/httpd-fp10.x. Configuration files of the Apache2 instance with web server for RED OS and Rocky Linux. /etc/httpd2-fp10.x. Configuration files of the Apache2 instance with BI server for ALT Linux. Features of BI server installation: When the full setup type is selected, the DBMS back end is prepared, a new database (METABASE_DBNAME) and a new repository (METABASE_ID) are created. When the custom setup type is selected, a permission to create a new database (METABASE_DBNAME) and a new repository (METABASE_ID) is requested on the DBMS server (DATABASE_SERVER). To create a database and a repository, the PG_ADMIN_ROLE and PG_ADMIN_PASSWORD variables should contain credentials of DBMS administrators corresponding to the server. If required, execute the command to manage BI server: Astra Linux: sudo systemctl start/restart/stop apache2-fp10.x RED OS and Rocky Linux: sudo systemctl start/restart/stop httpd-fp10.x ALT Linux: 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: /opt/foresight/fp10.x-webserver. Main files of web server. /etc/opt/foresight/fp10.x-webserver. The additional configuration file envvars of web server instance to set Apache2 environment variables. /etc/apache2-fp10.x-web. Configuration files of the Apache2 instance with web server for Astra Linux. /etc/httpd-fp10.x-web. Configuration files of the Apache2 instance with web server for RED OS and Rocky Linux. /etc/httpd2-fp10.x-web. Configuration files of the Apache2 instance with web server for ALT Linux. If required, execute the command to manage web server: Astra Linux: sudo systemctl start/restart/stop apache2-fp10.x-web RED OS and Rocky Linux: sudo systemctl start/restart/stop httpd-fp10.x-web ALT Linux: 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/
Licensing service	After the Licman License Server and Guardant License Server setup type is selected, the folder will be created: /opt/foresight/licman. Main files of the licensing service: the licman utility and the settings.json configuration file. If required, execute the command to manage the licensing service: sudo systemctl start/restart/stop licman.service
License server	After the Licman License Server and Guardant License Server setup type is selected, the folder will be created: /opt/guardant/grdcontrol. Main files of license server. Guardant Control Center is used to work with licenses. Guardant Control Center is available at: http://<IP address or DNS name of server>:3189/
Designer of business applications	After selecting the Designer of Business Applications setup type the following folders will be created: /opt/foresight/fp10.x-dba. Main files of designer of business applications. /etc/opt/foresight/fp10.x-dba. The additional configuration file envvars of designer of business applications instance to set Apache2 environment variables. /etc/apache2-fp10.x-dba. Configuration files of the Apache2 instance with designer of business applications for Astra Linux. /etc/httpd-fp10.x-dba. Configuration files of the Apache2 instance with the designer of business applications for RED OS, Rocky Linux. /etc/httpd2-fp10.x-dba. Configuration files of the Apache2 instance with the designer of business applications for ALT Linux. If required, execute the command to manage the designer of business applications: Astra Linux: sudo systemctl start/restart/stop apache2-fp10.x-dba RED OS and Rocky Linux: sudo systemctl start/restart/stop httpd-fp10.x-dba ALT Linux: 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/