To report a found bug,
please, select the text with the bug and click Report a Bug or
CTRL+ENTER.
Help
system 9.2 Update 14 of 08/12/2020,
©
FORESIGHT
In this article:
This article describes various settings to be determined after installation of BI server on Linux OS.
BI server in Linux supports connection to repositories created on Oracle, PostgreSQL and SQLite DBMS.
Repository connection settings can be stored in the registry.reg and/or Metabases.xml file. The registry.reg file can be obtained by exporting a Windows registry key, which stores information about repositories. To get the file, execute the following operations:
Export registry key at the workstation with installed Windows OS.
Copy registry.reg file to Linux home directory and edit if required. After this, if the file was obtained from the registry key [HKEY_LOCAL_MACHINE], copy it to the folder /opt/ Foresight /fp9.2-biserver/bin. If the file was obtained from the key [HKEY_CURRENT_USER], copy it to the folder /root/.config/Foresight/Foresight Analytics Platform/registry/.
It is assumed that the bin folder with the platform contains the registry key [HKEY_LOCAL_MACHINE], and the root folder /root/.config/Foresight/Foresight Analytics Platform/registry contains the registry key [HKEY_CURRENT_USER]. It automatically stores saved repositories from the HKEY_CURRENT_USER key on using the PP.Util utility to save confidential credentials for database connection. The BI server must have access to registry.reg files.
Registry export result is saved in the UTF-16 encoding, but BI server in Linux can work with a file in the UTF-16 and UTF-8 encoding. The file can be converted into UTF-8 encoding to facilitate editing in Linux, and the "vi" editor can work with the file in the UTF-16 encoding.
The Metabases.xml file must be located in the folder with the platform /opt/Foresight/fp9.2-biserver/bin, BI server must have access to the file. Metabases.xml can be easier edited in Linux, but this file have limitations because it cannot save credentials for connecting to repository database, for example, guest user credentials.
To apply changed settings for repository connection or new repositories, restart BI server.
Advanced settings are stored in the registry.reg or settings.xml file. The settings.xml file must be located in the directory /root/.config/Foresight/Foresight Analytics Platform (the directory may differ if the HOME environment variable is changed).
The file enables the user to determine such settings as the number of BI server connections to DBMS server, and so on.
Environment variables that are read on startup of BI server with Apache2 instance are located in the file /etc/opt/Foresight/fp9.2-biserver/envvars.
Variables are added to the file in the format:
export VARIABLE_NAME=VALUE
The following variables can be added:
| Environment variables | Description |
| export PP_LOG=1 | To output debug info about BI server performance to the file /var/log/apache2-fp9.2/error.log, add the variable to the end of the file (or uncomment the existing string). |
| export DISPLAY=:987 | To change number of the display, on which graphics is rendered, edit the string (by default, output is set up via xvfb). |
| export LSHOST=lserver1~lserver2 | The LSHOST variable is used to specify network name or IP address of license network servers, servers are enumerated via the "~" character. |
| export LSFORCEHOST=NO-NET | To specify the use of local stand-alone license, set the LSFORCEHOST variable. |
| export HOME=/root | To change the path, relative to which configuration files and a license file are searched, specify the HOME variable (be default, it matches home directory of the user, under whom the Apache2 parent process is started, that is, /root). |
| export USER=root | To change the user, under whom data, that is saved in the registry on DBMS authorization, is deciphered, the USER variable is used (it must match the user, under whom the Apache2 parent process is started, by default, it is root). |
| export TNS_ADMIN=/etc/opt/foresight/9.2 | On using Oracle DBMS based repositories, set the TNS_ADMIN variable and specify the path to the folder with the tnsnames.ora file (the Apache2 child process must have access to the file). |
NOTE. When working in Red Hat Enterprise Linux OS or CentOS OS and when using systemd as initialization system, the export command is not necessary to be written for correct setup. In this case, the following string are added to the file: DISPLAY=:987.
Various BI server files will be located in the following folders:
| Folder or file | Description |
| /opt/Foresight/fp9.2-biserver/bin | Main files of BI server. |
| /opt/Foresight/fp9.2-biserver/logs/axis2.log | Communication history of BI server. |
| /etc/opt/Foresight/fp9.2-biserver | Additional configuration files of BI server instance, such as the envvars file to determine environment variables of Apache HTTP Server. |
| /etc/opt/Foresight/httpd-fp9.2 (Astra Linux) /etc/apache2-fp9.2 (Debian and Ubuntu) /etc/httpd-fp9.2 (RHEL) |
Configuration files of the Apache HTTP Server instance. |
| /var/opt/Foresight/httpd/logs/error-fp9.2.log (Astra Linux) /var/log/apache2-fp9.2/error.log (Debian and Ubuntu) /var/log/httpd/error-fp9.2.log (RHEL) |
Errors and debagging messages of Apache HTTP Server instance. |
| /var/opt/Foresight/httpd/access-fp9.2.log (Astra Linux) /var/log/apache2-fp9.2/access.log (Debian and Ubuntu) /var/log/httpd/access-fp9.2.log (RHEL) |
Access history of Apache HTTP Server instance. |
| /root/.config/Foresight/Foresight Analytics Platform | Common configuration files of BI server (the path may differ on changing the HOME environment variable). |
| /etc/init.d/Foresight-httpd-fp9.2 (Astra Linux) /etc/init.d/apache2-fp9.2 (Debian and Ubuntu) /etc/init.d/httpd-fp9.2 (RHEL) |
init-script of Apache HTTP Server instance startup. |
| /etc/init.d/Foresight-xvfb | init-script of virtual display (X virtual framebuffer, by default it is started on the display No. 987 dpi 96). |
| /opt/Foresight/fp9.2-biserver/bin/in/fonts /usr/share/fonts /usr/local/share/fonts |
The fonts that can be used by BI server in work. |
After installing BI server, some applications can also be available, which are included into the software package:
axis2_http_server. Test application used on debugging of developed applications. To start up, execute the command:
PP_LOG=1 DISPLAY=:987 ./axis2_http_server
UpdateManager. The application for installing pefx files containing updates for repository objects. For details see the Executing Update subsection. To start up, execute the command:
DISPLAY=:987 ./UpdateManager
PP.Util. The application executing various auxiliary operations on BI server setup. For details see the PP.Util.exe subsection. To start up, execute the command:
PP_NODISPLAY=1 ./PP.Util
Scheduler. Task scheduler that controls task startup process. For details see the Task Scheduler subsection. To start up, execute the command:
DISPLAY=:987 ./Scheduler
echoid. The utility for getting a computer fingerprint is required on requesting a license. For details see the Getting Computer Fingerprint subsection.
lsdecode. The utility for getting information about license file.
lsinit. The utility for initializing licensing subsystem.
See also:
Installing BI Server on Linux OS | System Registry Settings | Settings.xml | Metabases.xml | Advanced Settings