Installing Mobile Platform Server

To install a mobile platform server:

Download the standalone_compose_files_v23.05.01.zip archive.

NOTE. To get mobile platform server distribution files, contact technical support by sending a request to support@fsight.ru or technical support services that are available after registration at the website.

Place configuration files from the standalone_compose_files_v23.05.01.zip archive on the server:

.env - always required.
docker-compose.standalone.yml - to start selected instance.

Change the SERVER_NAME parameter in the .env file if domain server name differs from localhost:

SERVER_NAME = <IP address or DNS server name>

To specify several server names, use the space character, for example:

SERVER_NAME = 127.0.0.1 localhost

NOTE. It is relevant only for installing Foresight Mobile Platform 22.04 or later.

Place platform images next to files for server installation.
Enter the server console using the account with appropriate permissions.
Import Docker images to the local repository by executing the command for each archive in the folder:

% docker load -i <archive_name>.tgz

After successful import delete the archives.

Make sure that startup files are located in the current directory, and execute the command:

# For selected installation
% docker-compose -f docker-compose.standalone.yml up

After executing the operations a mobile platform server is installed. Open administrator console and activate license for working with a mobile platform server.

Changing Local Databases to External Ones

Local databases are created during mobile platform server installation:

maindb. It is used to store administrator console settings, API users accounts, data sources parameters, and other system information.
cachedb. It is used to store cache of data sources resources.

Local databases can be changed to external ones to solve the following tasks:

Use of Postgres Pro. PostgreSQL is used by default.
Accelerated handling of mobile platform server requests if the number of use is more than 10000. The number of users can be changed depending on the task.
Use of different statements for data backup and information protection. The StackGres operator is used by default for local databases.

When setting up external databases, PostgreSQL version must match with the PostgreSQL version in the product software package:

Without fault-tolerant cluster 22.04 - PostgreSQL 10.20.
Without fault-tolerant cluster 23.04 - PostgreSQL 10.23.
With fault-tolerant cluster 22.04, 23.05 - PostgreSQL 12.3.

Storing Information in External Databases without the Use of Fault-Tolerant Cluster

To store information in external databases without the use of fault-tolerant cluster:

Open the .env file for edit, which is located on a mobile platform server.
Set parameters in the postgres section:

POSTGRES_MAIN_HOST=main_db
POSTGRES_MAIN_PORT=5432
POSTGRES_MAIN_NAME=hhive
POSTGRES_MAIN_USERNAME=hhive
POSTGRES_MAIN_PASSWORD=hhive
POSTGRES_CACHE_HOST=cache_db
POSTGRES_CACHE_PORT=5432
POSTGRES_CACHE_NAME=hhive_cache
POSTGRES_CACHE_USERNAME=hhive
POSTGRES_CACHE_PASSWORD=hhive

Save changes in the file.

After executing the operations, external databases will be used instead of local ones to store information.

Storing Information in External Databases in Cluster

To store information in external databases in a cluster:

Open the values.production.yaml file for edit, which is located in the fmp folder on a mobile platform server.
Set parameters in the externalPostgres section:

externalPostgres:
    maindb:
        enabled: true
        host: <host>
        port: <port>
        database: "<external database name>"
        username: "<user name>"
        password: "<password>"
    cachedb:
        enabled: true
        host: <host>
        port: <port>
        database: "<external database name>"
        username: "<user name>"
        password: "<password>"

Save changes in the file.

After executing the operations, external databases will be used instead of local ones to store information in a cluster.