Resource Migration Directory

1. Version 

2. Application scenarios

When using a data decision-making system, the test environment system is often used for deployment and development, and it is determined that there is no problem before migrating to the formal system.

Therefore, it is necessary to incrementally migrate dashboards, business packages, etc. from the test environment to the formal environment.

When using the FineBI data decision-making system, it is generally developed and deployed on the test environment system first, and then migrated to the formal system after confirmation.

FineBI supports incremental migration of template files and platform configurations from test systems to production systems.

3. Function introduction

Log in to the data decision-making system with Super Control, click "Manage> Intelligent Operations > Resource Migration", which is divided into two parts: "Resource Export" and "Resource Import".

This article only introduces the operation method when the migration resource type is "Catalog".

4. Notes

1) The resource migration function is only supported by super administrators. Even if the sub-administrator is assigned the authority of intelligent operation and maintenance, resource migration cannot be performed.

2) For formal projects, you need to purchase the "Intelligent Operations" function point to use the "Resource Migration" function.

3) Please ensure that no one else uses the super administrator account during the resource migration process, otherwise some execution requests may be cancelled.

4) It is not recommended to synchronize to the company project in the form of resource migration after the personal PC project development template.

Because there is no administrator maintenance on the personal PC side, resource migration often fails due to out-of-sync JAR packages or out-of-sync resource and configuration issues, resulting in high operation and maintenance costs.

1. Confirm the version

Before migrating resources, please ensure that the versions used by the FineBI projects for importing and exporting resources are the same.

The administrator can view the version number under "Manage > Registration > Version Information", as shown in the following figure:

If the versions are inconsistent, you can upgrade to ensure that the versions are consistent. For details, see: Upgrade Guide Index .

Note: BI projects of version 5.1.15 and later cannot be uploaded if the project corresponding to the uploaded resource is inconsistent with the current project version during resource import.

       Tip: Unable to import, the project version required for the resource to be imported: XXX. Current project version: XXX. Please make sure the project version is the same!

2. System Backup

back up both the test system and the official system , as shown in the following figure:

Note: The MySQL database to which the backup is migrated needs to select the collation of utf8_bin.

3. Confirm database case

If the system is configured with an external database , before resource migration, please make sure that the "Database Default Character Validation Rules" of the official system and the test system are "Case Sensitive".

Take Mysql as an example:

1) Make settings

Setting method: If an external database is configured, connect to the FineDB database, open the FINE_CONF_ENTITY table, set the character verification rule to utf8_bin, and enter the command as follows:

ALTER TABLE fine_conf_entity MODIFY id VARCHAR( 255 ) CHARACTER SET utf8 COLLATE utf8_bin; #Set the default validation rule of the column
ALTER TABLE fine_conf_entity DEFAULT CHARACTER SET utf8 COLLATE utf8_bin; #Set the validation rule of the table

2) View the setting result

As shown below:

4. Confirm data connection

• If data connection migration is required, you need to ensure that a data connection has been created in the official system before resource migration and import, and the data connection name must be the same as that of the test system, otherwise the resource cannot be successfully migrated.

• If you are migrating a dashboard created by a server dataset, you need to ensure that a server dataset with the same name has been created on the official system before migrating.

5. Confirm User Type

During the resource migration process, the user type of the creator of the dashboard needs to be consistent.

For example, if the creator of the dashboard in the test system is a BI data analysis user, it also needs to be added to the BI data analysis user in the formal system.

6. Migrating custom maps

If a custom map is called in the template, you need to copy the map json file to the official project.

Under the path of %FineBI%/webroot/WEB-INF/assets/map/image , copy the json file to be migrated to the corresponding path of the official project, as shown in the following figure:

1. Select directory

After the administrator logs in to the system, go to "Manage > Intelligent Operations> Resource Migration", select "Resource Export", and select the directory/dashboard to be exported, as shown in the following figure:

The exportable resources are:

• Base tables and self-service datasets used by the dashboard

• Dashboard configuration, original name, escaped name, user, mount directory, public link, sharing status, etc.

Note: Not all dashboards/data under the system will be exported. Does not exist in exported resources if not hanging out the dashboard. Be sure to hang out of the dashboard before proceeding.

2. Select dependent resources

After selecting the directory, you need to select the dependent resources. As shown below:

For example, when a dashboard is migrated from the test system to the official system, the user Alice has the permission to view the dashboard and the business package, but the user demo does not, so he needs to export his resources first.

At this point, the resource information of the data table (including the base table and self-service data set) used by the dashboard is obtained. As shown below:

You can select the corresponding data table resources to export at the same time. If the data table resource required by the dashboard already exists in the official system, you can choose not to export it here.

Dashboard-dependent resource support export scopes are:

• Directly used analysis table, basic table

• The analysis tables used, the underlying tables, and the related tables traversed on the association path. Linkage between      components and filtering of components by controls, export related tables in the shortest path

• If the dependent resource is from my self-service dataset , it can also be selected when exporting. During subsequent import, it will also be imported to the corresponding user's My Self-Service Dataset

3. Simultaneous export

Users can choose whether to export the following:

After exporting, the resources.zip file will be generated, as shown in the following figure:

1. Upload files

The super administrator logs in to the data decision system and selects "Management System > Intelligent Operation and Maintenance > Resource Migration > Resource Import", as shown in the following figure:

Note1: system backup before importing resources . The MySQL database to which the backup is migrated needs to select the collation of utf8_bin.

Note 2: Only a single compressed file is allowed to be uploaded at a time.

The system will obtain the resources contained in the imported file, including types, platform paths, physical resources, permission information, and import methods.

Example: When the resource is exported, the name of the table is called "Analysis Table 1" when it is created, and later changed to "Internet Analysis Channel Statistics". When the resource is imported, it will conflict with the "Analysis Table 1" in the imported project. As shown below:

2. Import files

Check the resources to be uploaded, click Import, and click OK. As shown below:

If the import fails, the reason for the failure will be displayed (for example, the export project and the import project have the same name and path but different types); if the import is successful, the resource will take effect immediately. As shown below:

Note: Since the IP port number of the corresponding environment configuration will change, the public link of the dashboard after the resource migration needs to be shared again.

3. Data update

If the imported base table resource is "extracted data", the data needs to be updated before importing into the new system before the corresponding dashboard can be viewed normally.

data update under the corresponding service package , or directly perform global update . After the update, you can see that the imported data tables are displayed normally, as shown in the following figure:

Note 1: For versions before 2020-01-15, if the dashboard uses Excel data, you need to enter the data business package used by the resource, select Update Excel under the corresponding data table, and re-upload the Excel table of the source data and update.

Note 2: If the imported data table is an Excel data set or a self-service data set made with an Excel data set as the base table, a business package update or a global update must be performed.

If the imported data table is a database table or an SQL data set, you can perform single table update on the imported table.

If the data update operation is not performed, when previewing the relevant dashboards, it will prompt "The self-service data set used by the current component is abnormal and cannot be displayed normally". As shown below: