Adding and Working with Project

To add a project in environment:

1. Click the Add Project button.

2. Set project parameters identical to those on adding an environment.

After executing the operations the project is added to the projects list for further editing.

To edit project parameters:

1. Click the project name.

After executing the operation the project opens in the edit mode:

2. Change parameters:

• Name. Enter unique project name within one environment. The name must consist of Latin letters, numbers, underscores or hyphen. The box is mandatory.

• Comment. Enter the comment to the added project that is set at administrator discretion.

• Do not Store LDAP User Passwords. Select the checkbox to delete passwords of LDAP users from the project for higher security requirements.

NOTE. When the checkbox is selected, user TGT are not deleted.

• Autologin. Select mobile user autologin option in the drop-down list:

• LDAP. Autologin is executed via the LDAP server.

• Data Source. Autologin is executed via the data source server.

When the Data Source autologin option is selected, set the advanced parameters:

• Authentication. In the drop-down list select the data source server: SAP, Postgres Pro/PostgreSQL, Oracle, Microsoft SQL Server, 1C, JSON, WEB, Foresight Web as follows: Server <data source name>.

When the JSON or WEB data source is selected, make sure that corresponding autologin parameters are set in data source connection settings.

NOTE. The project enables the use of automatic registration of one of data sources.

• Groups. Select one or several groups of users available for autologin.

3. Click the Save button.

After executing the operations the project is edited and refreshed in the projects list.

To copy project to another environment:

1. Click the Copy button next to project name.

After executing the operation the project copy parameters are displayed:

2. Set parameters:

• Environment. Select environment in the drop-down list. The box is mandatory.

• Project Name. Enter name of the new project that will be copied to the selected environment, or leave the box empty to automatically generate project name. The name must consist of Latin letters, numbers, underscores, or hyphen.

3. Click the Copy button.

After executing the operations the project is copied to the selected environment.

NOTE. When a project is copied, all data is copied except for cache and data contained in local database resources.

To delete project, click the Delete button next to the project name.

After executing the operation it is asked to confirm project deletion. If the answer is yes, the project is deleted from the environment.

To export project to file:

1. Click the Export button next to the project name.

After executing the operation the project export parameters are displayed:

2. Set parameters:

• Encrypt Export Data. If required, select the checkbox to export project without encryption, after which data can be changed. For example, to import project to another server, change data source connection parameters. The checkbox is selected by default

• Password. Set password to encrypt export file.

NOTE. The parameter is available if the Encrypt Export Data checkbox is selected.

3. Click the Export button.

After executing the operations the project is exported to JSON(*.json) file and is further imported to the environment on this or other server. File name matches the project name on export.

NOTE. When a project is exported, all data is exported except for cache and data contained in local database resources.

A project may not be exported to file if it contains large amount of data (for example, by the number of users) or the system does not have enough RAM to execute export. To resolve this issue:

1. Set the timeout from 600 to 10000 seconds for proxy servers located before the mobile platform.

2. Set the RAM limit hyperhive_hhive_1 up to 2 Gb in the .env file:

HHIVE_RAM_LIMIT = <RAM volume>

If on installing Foresight Mobile Platform a fault-tolerant cluster based on OKD/OCP is created, execute the following operations:

1. Set timeout Ingress from 600 to 10000 seconds using the command:

oc annotate routes -n fmp --all --overwrite haproxy.router.openshift.io/timeout='<number of seconds>s'

For example:

oc annotate routes -n fmp --all --overwrite haproxy.router.openshift.io/timeout='10000s'

If additional proxy servers are located before Ingress, set timeout for them too, if required.

2. Set RAM limit for the fmp-dashboard pod up to 2 Gb.

After executing the operations the project should be exported to file.

To import project to environment:

1. Click the Import Project button.

After executing the operation the project import parameters are displayed:

2. Set the parameters:

• Project Name. Enter name of the new project that will be imported from file to the selected environment, or leave the box empty to automatically generate project name. The name must consist of Latin letters, numbers, underscores, and hyphen.

• Password. Enter password of the encrypted project file. The box is mandatory.

• Project File. Select project file using the Select File button. The box is mandatory.

3. Click the Import button.

After executing the operations the project is imported from the file exported at this or other server to the selected environment.

NOTE. When a project is imported, all data is imported except for cache and data contained in local database resources.