Configure PostgreSQL external database

1.1 Edition

1.2 Function introduction

After the BI system is configured with an external database, it can ensure the stability of the BI system in case of a cluster environment or a large amount of data.

Users can configure external databases of PostgreSQL type in the data decision system by installing the "PostgreSQL external database" plug-in.

Note: if an external database is configured, do not easily modify the user name and password of the external database, otherwise the project will fail to start.

       For modification, please refer to：Modify the external database account password .

1.3 matters needing attention

If the report project is configured with a virtual directory, that is:Direct access to data decision system through IP in Tomcat，Before installing the plug-in, you need to modify the server configuration file.

Open% Tomcat_ Modify the home% \ conf \ server.xml file and reload = false, as shown in the following figure:

Prepare the database to which the platform data will be migrated. It is recommended that you create an empty database (see Section 2.2 of this article for the database size).

Note: different finebi projects cannot share the same external database, otherwise the data may be disordered.

2.1 Database version:

The types and versions supported by the external database are shown in the following table:

2.2 Hardware configuration

Note 1: the occupied space needs to be adjusted in combination with the usage. It can be configured according to the size of the webapps / Webroot / WEB-INF / embedded / finedb folder, and the future use size can be estimated according to the actual size, increasing by 1-2 times.

Note 2: the recommended memory is the memory reserved for the engineering configuration library.

Note 3: the external database shall be in the same network segment as the Bi project as much as possible to avoid network fluctuation and other problems.

This method is applicable to configuring external database for the first time after entering the data decision system.

3.1 Installing plug-ins

Click to download the plug-in：PostgreSQL external database

For plug-in installation method, please refer to：Plug in management

3.2 Access platform

The administrator logs in to the data decision system and clicks "Manage > System > General > external database > to be configured", as shown in the following figure:

3.3 Configure external database

Input the corresponding information of the actual database and configure the external database. As shown in the following figure:

The description of each setting item is shown in the following table:

3.4 Configuration succeeded

After waiting for a period of time, a pop-up prompt will pop up: the target database has been successfully enabled. Click detemine. As shown in the following figure:

Note 1: do not refresh the page during migration.

Note 2: there is no need to restart after the database configuration is successful.

This method is applicable to migrating to a new database after the external database has been configured.

4.1 Installing plug-ins

Click to download the plug-in：PostgreSQL external database

For plug-in installation method, please refer to：Plug in management

4.2 Access platform

The administrator logs in to the data decision system and clicks "Manage > System > General > external database > configured", as shown in the following figure:

4.3 Configure external database

Input the corresponding information of the actual database and configure the external database. As shown in the following figure:

The description of each setting item is shown in the following table:

Description of the "migrate data to the database to be enabled" button:

1）Check "migrate data to the database to be enabled"

• When the database is switched, the data of the original external database will be imported into the new database, and the historical data backup file will not be generated under the project.

• If platform data already exists in the new database, the original platform data will be cleared before importing data. The prompt is shown in the following figure:

2）Uncheck "migrate data to the database to be enabled"

• If the new external database is empty, it prompts that the current data must be migrated to the target database.

• If the new external database is not empty

      Before migration, the configuration information of the original database will be automatically backed up, and the db.properties.bak file will be generated in the webapps \ Webroot \ WEB-INF \ config directory. As shown in the following figure:

       The Bi project of version 5.1.15 and later will automatically detect whether the jar package version corresponding to the data in the target database is consistent with the jar package version of the current project.

       If it is inconsistent, a prompt will pop up: unable to enable! Project version required to enable the new database: XXX. Current project version: XXX. Please ensure the project version is consistent!

      If the jar package version is consistent, directly enable the new database. After the migration is successful, the prompt is as shown in the following figure:

4.4 Migration succeeded

After waiting for a period of time, a pop-up prompt will pop up: successfully switched to the target database! If there are data differences between the old and new databases, the system operation may be affected. It is recommended to restart the sprint to ensure normal use.

Click "determine" and restart the Bi project. The migration is successful. As shown in the following figure:

Note: do not refresh the page during migration.

Tips：