Installing and Setting Up Foresight Mobile Platform

To work with Foresight Mobile Platform, install:

Mobile platform server. Mandatory component.
Relay server. The component is optional for cluster configuration of Foresight Mobile Platform and is used as additional data protection in the internal corporate network.

Servers are installed and set up by the administrator who manually controls server access in his own virtual infrastructure. This way ensures data protection and improved security.

System Requirements and Environment Requirements

To install and set up Foresight Mobile Platform, check correspondence with system requirements:

Virtual or physical server.
Configuration: 6 cores CPU, 8GB RAM, 50GB HDD.
OS: Ubuntu 22.04, Astra Linux SE 1.7.5, 1.7.6, 1.8.1 and CE 2.12, Rocky Linux 8.6.

NOTE. To further install standalone configuration of Foresight Mobile Platform and deploy server using Docker subsystem infrastructure in Astra Linux, one will require to connect to network repository.

Root OS user permissions (root).
Configured network subsystem by IP protocol.
SWAP sections in the disk are disabled.
Internet access during server deployment and preparation.

Installing Foresight Mobile Platform

Installation of Foresight Mobile Platform depends on the configuration:

Foresight Mobile Platform installation includes automatic installation of built-in services: PostgreSQL DBMS, MinIO, Elasticsearch, and Redis. To connect and use external services instead of built-in ones, see the Connecting to External Services section.

After Foresight Mobile Platform is installed, one can also set up mobile platform server.

Checking Mobile Platform Server Availability

To check mobile platform server availability:

Execute requests using the "status" API method:

curl "<http or https>://<IP address or DNS name of prepared server>/api/v1/status/"

Specify browser URL in the address bar depending on the protocol in use:

<http or https>://<IP address or DNS server name>/api/v1/status/

After executing one of the operations a JSON string is obtained with the result of mobile platform server availability check.

The successful result of mobile platform server availability check:

{"message":"Welcome to Foresight Mobile Platform.","time":"2019-03-19T12:35:53.390324"}

NOTE. A mobile platform server can be checked without authentication.

Ports and Protocols

Below is the list of ports and protocols that are used by various components of mobile platform to communicate with other information resources of the system being created.

System component	Port
Protocols
Administrator console and API (HTTP connection)	80
Administrator console and API (HTTPS connection)	443
LDAP	389
LDAP SSL	636
LDAP (global directory)	3268
Kerberos	88
SMTP	25
Connected data sources
SAP	33[<instance number>]
Postgres Pro/PostgreSQL	5432
1C	80
Oracle	1521
SQL Server	1433
SOAP	80
JSON	80
WEB	80
Foresight	80
Foresight Web	80
Other
CryptoPro DSS	80
Kafka	9002
Proxy for Push	80

IMPORTANT. The 443 port is mandatory for internet access.

Ports for internal network:

System component	Port
PosgreSQL (databases maindb, cachedb, localdb)	5432
Redis	6379
MinIO/Ceph	9000
Elasticsearch/OpenSearch	9200
Kibana	5601

To get list of ports used in Firebase Cloud Messaging and Apple Push Notification Service, see the official websites.

Technical Support Service

If you have questions about the use of Foresight Mobile Platform and supported versions, contact technical support by sending a request to support@fsight.ru or via technical support services that are available after registration at the website.