Resource Migration

Normally, you'll need to deploy the FR decision-making system in a test environment first to ensure that everything works well, before migrating it into the production environment. In previous versions, however, this process only supports migrating all the system configurations at once and was not able to tell the differences between two instances. Consequently, we have added incremental migration support for report files and platform configurations in version 10.0.

1. Go to Resource Migration

1) Login to the Local Decision-making Platform via Server ->  Platform Management from FineReport designer.

2) Go to Manage -> Intelligent Operations -> Resource Migration to see the interface.

2. Resource Export

1) The default resource type is "Catalog", and the available options are nodes and relating configurations mounted in the system directory.

2) Choose the resources you'd like to export and select if you need to "Export permission configuration at the same time", then export the file (including nodes, node configurations, permissions) and save it locally. The default file name is resource.zip.

3. Resource Import

Note: it is suggested to backup the system before importing resources. The backup file migrated to MySQL requires utf8_bin collation.

• Only one compressed file is allowed in each upload.

• The system will parse the imported file to get the Type, Platform Path, Physical Resources, Permissions Information and Import Mode.

Let's try to import the file exported in Step 2.

• Conflict detection:

During the import process, the system will check the resources to detect whether there is a conflict with the existing resources. This feature will perform checks in line with the original names of the resources as well as their platform paths. If the imported data conflict with the system, the import mode will be displayed as "Cover Import" with records unselected. In the case of no conflict, it will be displayed as "Direct Import" and selected. Click  to see detailed information.

• Missing path: the information will be auto-completed.

• Permissions information: click on "Details" to check the permission and see if a department, role or user is missing in the process.

• In the case of import failed, the reason for failure will be displayed (for example, different file types for files with the same name and path in both resources). Resources will be applied immediately with a successful import.