In this article:

Configuration and Setup

This article describes various settings to be determined after installation of BI server on Linux OS.

Repository Connection Settings

BI server in Linux supports connection to repositories created on Oracle, PostgreSQL and SQLite DBMS.

NOTE. Before setting up connection to repositories, see constrains when working with BI server on Linux.

Repository connection settings can be stored in the registry.reg file and/or in the Metabases.xml file. The registry.reg file can be obtained by exporting the Windows registry key, which stores repository information. To get the file, execute the following operations:

Export the registry key at the workstation with installed Windows OS.

Copy the registry.reg file to Linux home directory and edit if required. After this copy the file to the folder /opt/foresight/fp10.x-biserver/etc/registry.

It is assumed that the folder /opt/foresight/fp10.x-biserver/etc/registry contains the registry key [HKEY_LOCAL_MACHINE] or [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.

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 should be located in the folder /opt/foresight/fp10.x-biserver/etc. The Metabases.xml file is easier to edit in Linux OS, but this file has limitations because it cannot save credentials for repository database connection, for example, guest user credentials.

To apply changed settings for repository connection or new repositories, restart BI server.

Advanced Settings

Advanced settings are stored in the registry.reg or settings.xml file. The settings.xml file should be located in the directory /opt/foresight/fp10.x-biserver/etc.

The file enables the user to determine such settings as the number of BI server connections to DBMS server, and so on.

Environment Variables

Environment variables that are read on startup of BI server with Apache2 instance are located in the file /etc/opt/foresight/fp10.x-biserver/envvars.

Variables are added to the file in the format: <variable name>=<value>.

The following variables can be added:

Environment Variables	Description
PP_LOG=1	To display debug info about BI server performance to the /var/log/apache2-fp910.x/error.log file, add the PP_LOG variable to the end of the file or uncomment the existing string. The displayed information is described in the Working with Debug Info subsection.
PP_LOGTIME=1	To display time stamps in the debug info, which allow for tracking the time spent on execution of various operations, add the PP_LOGTIME variable and set it to 1.
CURLOPT_VERBOSE=1	To log the actions executed via the libcurl third-party library, create an environment variable with the 1 value. Messages are displayed to the file /var/log/apache2-fp10.x/error.log.
DISPLAY=:987	To change number of the display, on which graphics is rendered, edit the string (by default, output is set up via xvfb).
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.
LSFORCEHOST=<license server name or NO-NET>	If it is required to use network license, specify license server name; if it is required to use stand-alone license, specify NO-NET.
HOME=/root	To change the path, relative to which configuration files and a license file are searched, specify the HOME variable (by default, it matches home directory of the user, under whom the Apache2 parent process is started, that is, /root).
USER=root	To change the user, under whom data saved in the registry on DBMS authorization is decrypted, use the USER variable (it must match the user, under whom the Apache2 parent process is started. By default, it is root).
TNS_ADMIN=/opt/foresight/fp10.x-biserver	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).
PP_RETMEM=1	To force free the operating system memory on closing the repository, create the PP_RETMEM environment variable and set it to 1. The default value is 0. The volume of freed memory depends on the MALLOC_MMAP_THRESHOLD_ variable.
MALLOC_MMAP_THRESHOLD_=8192	To manage the operating system memory, create the MALLOC_MMAP_THRESHOLD_ environment variable and set it to 8192. The volume of freed memory will be returned to the operating system if the PP_RETMEM variable is set to 1.
PP_RETMEM_CO=1	To force free the operating system memory on closing repository objects, create the PP_RETMEM_CO environment variable and set it to 1. The 0 value is used by default, the memory is not force freed or it is force freed on closing a repository if the PP_RETMEM variable is defined.
KRB5RCACHEDIR=/opt/foresight/fp10.x-biserver/var/cache	To use integrated domain authentication in Linux OS. The *.rcache2 file is created in the specified folder when the mod_auth_gssapi works.

BI Server Files and Folders

Various BI server files will be located in the following folders:

Folder or file	Description
/opt/foresight/fp10.x-biserver/bin	Main files of BI server.
/opt/foresight/fp10.x-biserver/etc	Configuration files: envvars to set environment variables. Metabases.xml to set repository connection. scheduler.xml To start task scheduler. settings.xml to create parameters that are identical to registry parameters. registry/*.reg to set up registry files. TIP. It is recommended to provide access to write to files and folders in etc only for the operating system administrator.
/opt/foresight/fp10.x-biserver/var/cache	Files created at In-Memory data caching and caching of development environment objects.
/opt/foresight/fp10.x-biserver/var/log	Log files: axis2.log for logging basic service module. AuditError.txt For logging operations with objects in case of data write failure in access protocol. Scheduler.log for logging work of task scheduler.
/etc/apache2-fp10.x (for Debian-based distributions) /etc/httpd-fp10.x (for RedHat-based distributions) /etc/httpd2-fp10.x (for ALT Linux)	Configuration files of the Apache HTTP Server instance with BI server.
/var/log/apache2-fp10.x/error.log (for Debian-based distributions) /var/log/httpd/error-fp10.x.log (for RedHat-based distributions) /var/log/httpd2/error-fp10.x.log (for ALT Linux)	Errors and debugging messages of Apache HTTP Server instance with BI server.
/var/log/apache2-fp10.x/access.log (for Debian-based distributions) /var/log/httpd/access-fp10.x.log (for RedHat-based distributions) /var/log/httpd2/access-fp10.x.log (for ALT Linux)	Access history of Apache HTTP Server instance with BI server.
/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-fp10.x (Astra Linux)	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 with dpi 96).
/usr/share/fonts /usr/local/share/fonts	The fonts that can be used by BI server in work.