Installing and Setting Up Foresight Mobile Platform

To work with Foresight Mobile Platform, install:

Mobile platform server. Mandatory component.
Relay server. The mobile platform server can use Relay server for additional protection of internal corporate network data. The use of a Relay server is optional.

Servers are installed and set up by the customer 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 and CE 2.12, Rocky Linux 8.6.

NOTE. To further deploy and prepare the server using infrastructure of the Docker subsystem in Astra Linux SE 1.7 and CE 2.12, one will require to connect to network repository.

Root OS user permissions (root).
Configured network subsystem by IP protocol.
Internet access during server deployment and preparation.

Installing Foresight Mobile Platform

To install Foresight Mobile Platform:

Check if system time is correct. If the user changes system time after the installation, Foresight Mobile Platform does not guarantee logging and scheduled task execution correctness.
Deploy and prepare a mobile platform server depending on the OS in use:

Install a mobile platform server and a Relay server if required.

NOTE. To provide correct work, mobile platform server and Relay server version must match.

Open administrator console and activate license for working with a mobile platform server.

After executing the operations a mobile platform server is ready for integration with data sources and mobile application development. Set up mobile platform server work using the administrator console.

To update Foresight Mobile Platform, see the Updating Foresight Mobile Platform section.

To deploy a fault-tolerant cluster, see the Preparation and Deployment of Fault-Tolerant Cluster Based on OKD/OCP, Preparation and Deployment of Fault-Tolerant Cluster Based on Kubernetes, and Preparation and Deployment of Fault-Tolerant Cluster Based on Deckhouse sections.

IMPORTANT. A fault-tolerant cluster based on Kubernetes or Deckhouse is compatible with Foresight Mobile Platform 23.12 or later.

To set up additional parameters on installing Foresight. Mobile Platform, see the section:

TIP. To increase administrator console performance on adding a number of user credentials it is recommended to set up the number of displayed credentials.

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 URL in the browser address field 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
Local file storage (minio)	9000
Main DB (PosgreSQL)	5432
Cache database (PosgreSQL)	5432
Local database (PosgreSQL)	5432
Kibana	5601
Elasticsearch	9200
Redis	6379

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

Scheme of interaction between system components with specification of ports

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.