To report a found bug,
please, select the text with the bug and click Report a Bug or
CTRL+ENTER.
Help
system 10.4 of 09/07/2024,
©
FORESIGHT
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.
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 was installed at least once. System time change leads to cancellation of any license.
Administrator permissions. Administrator permissions are required to install Foresight Analytics Platform desktop application, BI server and web application, 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.
Depending on the Windows operating system type:
Windows server operating system: the Web Server role. When installing BI server and web application to Windows server operating system, one should add the Web Server role.
Windows client operating system: Internet Information Services. When installing BI server and the web application to Windows client operating system, one should connect Internet Information 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. See DBMS documentation to learn additional requirements for DBMS back end installation.
Working with Foresight Analytics Platform requires:
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. See DBMS documentation to get precise numbers of ports and required services.
Work of Foresight Analytics Platform as part of DHTML application requires:
Full permissions to the folder with installed Foresight Analytics Platform.
Open access to the port, via which the web server works (port 8110 by default for Apache HTTP Server).
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 Internet Information Services. When installing the BI server and the web application the installer creates necessary application pools and virtual directories.
Open access to the port, via which the web server works (port 80 by default for Internet Information Services).
Interaction of Foresight Analytics Platform and license server in Linux OS and Windows OS:
Privileged user permissions to start or stop and set up license server.
Open access to ports 5093 (for client-server communication) and 5099 (for server-server communication) to work on the UDP protocol.
To provide correct print of reports built using Foresight Analytics Platform tools when ALT Linux 10 is used:
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.
Below is the list of ports and protocols that are used by different components of the analytics platform to communicate with other information resources of the system being created.
| System component | Default port | Protocol | Comments |
Desktop application. Communication with DBMS to get access to repositories |
Oracle - 1521 Microsoft SQL Server - 1433 Teradata - 1025 PostgreSQL/Postgres Pro/Postgres Pro Enterprise - 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. In Windows OS, Microsoft Office add-ins communicate with DBMS in the same way as the desktop application. |
| BI Server | Apache - 8810 for Linux OS Internet Information Services - 80 for Windows OS |
HTTP, HTTPS | |
| BI search service | 8080 | HTTP | Port number depends on settings of Apache Tomcat where Apache Solr is deployed. |
| Web Application Back End | Apache for Linux OS:
Internet Information Services for Windows OS:
|
HTTP, HTTPS | |
| State Server | Redis - 6379 Memcached - 11211 |
TCP | |
| License Server | 5093, 5099 | UDP |
To view required ports in Linux OS, use:
The file /etc/apache2-fp10.x/ports.conf for Debian-based distributions.
The /etc/httpd-fp10.x/conf/httpd-fp10.x.conf for RedHat-based distributions.
The file /etc/httpd2-fp10.x/conf/httpd2-fp10.x.conf for ALT Linux.
To communicate with SAP or Microsoft Analysis Services data sources, ports that are set in settings of corresponding software are used. For details see software guides.
| Software | Comments |
| SAP software family | The list of ports is available in the documentation at: https://help.sap.com/viewer/ports. |
| Microsoft Analysis Services |
|
See also:
System Requirements for Client Environment