Show contents 

Installing and Setting Up Foresight Analytics Platform > System Requirements > Requirements for Operating System Settings

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

Before installing Foresight Analytics Platform check:

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.

NOTE. See DBMS documentation to learn additional requirements for DBMS back end installation.

Requirements for Settings for Working with Foresight Analytics Platform

Working with Foresight Analytics Platform requires:

NOTE. See DBMS documentation to get precise numbers of ports and required services.

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

Interaction of Foresight Analytics Platform and license server in Linux OS and Windows OS:

To provide correct print of reports built using Foresight Analytics Platform tools when ALT Linux 10 is used:

PrivateTmp=false

Ports and Protocols

Below is the list of ports and protocols used by different analytics platform components to communicate with other information resources of the system being created. Access to these ports should be opened according to the operation system in use, web server, and DBMS server.

System component Default port Protocol Comments

Web application and desktop application. Communication with DBMS to get access to repositories

Oracle - 1521

Microsoft SQL Server - 1433

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 for Linux OS:

  • HTTP - 8810.

  • HTTPS - 443

Internet Information Services for Windows OS:

  • HTTP - 80

  • HTTPS - 443

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:

  • HTTP - 8110.

  • HTTPS - 443

Internet Information Services for Windows OS:

  • HTTP - 80

  • HTTPS - 443

HTTP, HTTPS  
Designer of Business Applications Back End

Apache for Linux OS:

  • HTTP - 8210

  • HTTPS - 443

Internet Information Services for Windows OS:

  • HTTP - 80

  • HTTPS - 443

HTTP, HTTPS  
State Server

Redis - 6379

Memcached - 11211

TCP  
License Server 5093, 5099 UDP  
Licensing Service 8510 HTTP

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 HTTPS protocol, see the Setting Up Web Forms to Work via HTTPS section

To view required ports in Linux OS, use:

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
  • 2383 on setting the default instance.
  • 2382 on setting named instance.
For details about port setup see the documentation.

See also:

System Requirements for Client Environment