Requirements for Operating System Settings

This section contains requirements for operating system settings necessary for Foresight Analytics Platform. Meeting these requirements will ensure proper installation and work of Foresight Analytics Platform.

Requirements for Settings before Installing Foresight Analytics Platform Activation

Before installing Foresight Analytics Platform check:

System time on the server and client computer. If required, correct it before installing Foresight Analytics Platform.

IMPORTANT. It is prohibited to change the system time on the client computer or server, if Prognoz Platform or Foresight Analytics Platform. System time change leads to cancellation of any license.

Administrator permissions. Administrator permissions are required to install BI server, web application back end, DBMS back end and license server.
In Linux operating system:

Temporary file storage Tmpfs. If the operating system uses Tmpfs, we recommend to see whether it is possible to not use Tmpfs, in order that temporary files were located on the disk. It is related with the fact that the Tmpfs system does not support attributes required for correct work of Foresight Analytics Platform.
Regional system settings should have the English locale. To do this, execute the command:

locale -a

If the en_US.UTF-8 locale is not displayed in the list, execute the command and select this locale in the interactive mode:

sudo dpkg-reconfigure locales

If required, make sure that the en_US.UTF-8 string is uncommented in the /etc/locale.gen file.

Depending on the Windows operating system type:

Windows server operating system: the Web Server role. When installing BI server and web application back end to a server Windows OS, add the Web Server role on the servers.
Windows client operating system: Internet Information Services (IIS). When installing BI server and web application back end to a client Windows OS, connect IIS services.

Temporary file storage settings. BI server can use temporary files during the work. Temporary files are deleted after they are no longer needed. Operating system built-in mechanisms are used to set up temporary file storage. In Linux OS, location of temporary files is controlled by the TMPDIR environment variable; in Windows OS - by the TMP environment variable.

NOTE. To get additional requirements applied during DBMS back end installation, see the documentation of corresponding DBMS.

Requirements for Settings for Working with Foresight Analytics Platform Activation

Working with Foresight Analytics Platform requires:

Linux OS Windows OS

Open access to ports, with which a DBMS works.
Start DBMS services.

The Users group permissions.

Open access to ports, with which a DBMS works.
Start DBMS services.
Start Microsoft .NET Framework 4.5.2 or later.
In order an Oracle client and Foresight Analytics Platform work correctly, it is necessary that in the Windows local security policy the user (group) is included in the Create Global Objects policy.

NOTE. To find out port numbers and necessary services, see the documentation of corresponding DBMS.

Working with Foresight Analytics Platform as part of DHTML application requires:

Linux OS Windows OS

Full permissions to the folder with installed Foresight Analytics Platform.
Open access to the port, via which the web server works. The 8110 port is used by default.

The Users group permissions.
Full permissions to the folder with installed Foresight Analytics Platform.
Permissions to create virtual directories.
Start Microsoft .NET Framework 4.5.2 or later.
Start IIS services. When installing BI server and web application back end, the installer creates necessary application pools and virtual directories.

Open access to the port, via which the web server works. The 80 port is used by default.

Interaction of Foresight Analytics Platform and license server requires open access to the licensing service port (8510 by default), with which Foresight Analytics Platform. The licensing service communicates with the license server via the 3189 port.

For correct printing of reports built using Foresight Analytics Platform tools in ALT Linux:

In the Apache2 service file /etc/systemd/system/httpd2-fp10.x.service change value of the PrivateTmp parameter that controls creating a directory for each process apache2-fp10.x (in the tmp directory):

PrivateTmp=false

Create the /tmp/apache2-fp10.x directory to store temporary files created as a result of working with the Qt library. Location of temporary files is controlled with the TMPDIR environment variable.

Ports and Protocols

The table contains ports and protocols that are used by various Foresight Analytics Platform components to communicate with other information resources of the system being created. Access to these ports should be opened according to the operating system, web server, and DBMS server in use.

System component	Default port	Protocol	Comments
DBMS	Oracle - 1521 Microsoft SQL Server - 1433 PostgreSQL - 5432	TCP	Port can be modified if DBMS supports work via various ports. The current port used for work can be received from DBMS administrator.
BI Server Task Scheduler InMemory MOLAP Server	Apache2 for Linux OS: HTTP - 8810 HTTPS - 443 IIS for Windows OS: HTTP - 80 HTTPS - 443	HTTP, HTTPS
Web Application Back End	Apache2 for Linux OS: HTTP - 8110 HTTPS - 443 IIS for Windows OS: HTTP - 80 HTTPS - 443	HTTP, HTTPS
Designer of Business Applications Back End	Apache2 for Linux OS: HTTP - 8210 HTTPS - 443 IIS for Windows OS: HTTP - 80 HTTPS - 443	HTTP, HTTPS
State Server	Redis - 6379 Memcached - 11211 Tarantool - 6379 Radix - 6379	TCP
License Server	Guardant - 3189	TCP
Licensing Service	HTTP - 8510 HTTPS - 8511	HTTP, HTTPS	The port can be changed in the settings.xml file.
Web Forms	HTTP - 9091	HTTP, HTTPS	The port cannot be changed in environment variables or in the system registry/settings.xml file. To work with web forms via the HTTPS protocol, see the Setting Up Web Forms Work via HTTPS section.

To view required ports in Linux OS, use the files:

/etc/apache2-fp10.x/ports.conf in Debian-based distributions.
/etc/httpd-fp10.x/conf/httpd-fp10.x.conf in RedHat-based distributions.
/etc/httpd2-fp10.x/conf/httpd2-fp10.x.conf in ALT Linux.