FineOps provides a visual Project Migration function to help you complete FanRuan project migrations, including but not limited to:
1. Upgrading a FineReport project to a FineBI project.
2. Converting a project not deployed via FineOps into a FineOps-deployed project.
3. Converting a non-ITAI project into an ITAI project.
4. Migrating projects across versions.
Log in to FineOps as the admin and choose Maintenance Center > Project Migration. The page contains six tabs:
It is an independent function for migrating Swift log data, with checkpoint-based resumption supported.
This function is not described in this document.
Use this section to determine whether a project can be migrated with this tool before starting.
To avoid wasting target server resources, check each item first. Proceed to pre-migration preparation only after all requirements are met.
The target project must be a FineOps-deployed project. The support status of each combination is as follows:
When you migrate a non-FineOps-deployed source project to a FineOps-deployed project, compatibility may be affected. Before migration, confirm compatibility issues. For details, see Pre-migration Compatibility Notes.
FineOps-deployed projects offer isolation, portability, flexibility, scalability, and controllability, and can reduce maintenance and resource costs. Therefore, migration is supported only to FineOps-deployed projects.
Middleware requirements depend on the source project's ITAI type and deployment method:
FineOps-deployed source project: There is no additional requirement.
Non-FineOps-deployed source project: The project middleware must be BES or TongWeb on a Linux/Windows server.
Non-FineOps-deployed source project: The project middleware must be Tomcat on a Linux/Windows server.
Customized functions in an ITAI project may not work after conversion to a non-ITAI project, so migration from an ITAI project to a non-ITAI project is not supported.
FineOps-deployed projects use Tomcat, BES, or TongWeb middleware. To ensure there are no compatibility issues after migration, non-FineOps-deployed source projects must use the corresponding middleware listed above.
The source project's main application version must meet the minimum version requirement, and the target project version cannot be earlier than the source project version.
FineBI/FineReport
Minimum version requirement: FineBI 6.0/FineReport 11.0.6.
FineDataLink
Version range requirement: FineDataLink of V4.2.19.2 to V4.2.X, or FineDataLink of V5.0.12.2 or later versions.
The standalone project and cluster project indicate whether the project uses a cluster architecture (that is, whether it is connected to cluster components such as the state server and file server), not the number of FineBI, FineReport, or FineDataLink applications. A mismatch in the number of applications between the source project and target project does not affect migration.
The FineOps project migration tool supports two migration methods, namely export-import migration and automatic migration.
Automatic migration is divided into direct transfer migration and relay transfer migration.
Recommended priority: direct transfer migration > relay transfer migration > export-import migration.
1. If the source project and target project cannot be connected to the same FineOps platform, you must choose export-import migration.
For example, a non-ITAI project and an ITAI project cannot be connected to the same FineOps platform, so export-import migration is the only option.
If the source project, target project, and the same FineOps platform cannot communicate over the network, export-import migration is also the only option.
2. If the network is unreachable, automatic migration will use relay transfer migration. Otherwise, it uses direct transfer migration by default.
The server where the target project is located must be able to access the server where the source project is located through SSH. Otherwise, automatic migration uses relay transfer migration.
The server where the target project is located must be able to access the source project's file server (if any) through SSH. Otherwise, automatic transfer migration automatically uses relay transfer migration.
For FineOps and projects that will be deployed or have already been deployed, check network connectivity between the corresponding servers.
1. Project-to-FineOps connectivity (required for all migration methods)
The server where FineOps is deployed must be able to communicate with the server where the source project is located.
The server where FineOps is deployed must be able to communicate with the server where the target project is located.
2. Project-to-project connectivity (required for automatic migration > direct transfer migration)
The server where the target project is located must be able to access the server where the source project is located through SSH.
The server where the target project is located must be able to access the source project's file server (if any) through SSH.
Prepare SSH connection information for any node of the source project. The prepared user must have read permissions.
If the preceding requirements cannot be met, the file transfer path for automatic migration changes, and relay transfer migration is automatically used instead of direct transfer migration. This increases migration time and difficulty. You are advised to ensure that these requirements are met.
Direct transfer migration path: source project - transfer files via SSH -> target project.
Relay transfer migration path: source project - compress files and transfer archive -> FineOps - transfer archive -> target project - decompress the file.
3. Project disk space (required for automatic migration > relay transfer migration and export-import migration)
For the disk directory where the mounting directory of every application component or the webroot directory of the source project is located, remaining available disk space must be greater than 50 GB, to ensure enough space for exported or compressed migration packages.
For the disk directory where the mounting directory of every application component of the target project is located, remaining available disk space must be greater than 50 GB to ensure enough space for imported or extracted migration files.
4. FineOps disk space (required for automatic transfer migration > relay transfer migration)
The disk directory where the mounting directory of the FineOps ' OPS component is located must have more than 50 GB of remaining available space to ensure enough space for compressed migration packages.
1. If FineOps has not been deployed:
Deploy it according to FineOps Deployment.
1. ITAI projects require FineOps ITAI edition and cannot be connected to FineOps standard edition.
2. If you use export-import migration with two FineOps platforms, make sure the versions of the two FineOps platforms are the same. Otherwise, import may fail.
2. If FineOps has already been deployed:
This document provides migration plans based on the latest version of the project migration tool.
Upgrade FineOps to the latest version according to Upgrading FineOps over the Internet or Upgrading FineOps on the Internal Network.
1. Historical versions of the project migration tool may not support some applicable project migrations, and their usage may differ.
The target project must be a FineOps-deployed project. Non-FineOps-deployed projects cannot be used as target projects.
If the target project has not been deployed, see New Project Deployment.
If the target project has already been deployed, you are advised to upgrade the target project to the latest version according to Upgrading O&M Projects over the Internet or Upgrading O&M Project on the Internal Network.
The source project may not yet be connected to FineOps.
Connect FineOps to the source project according to Connecting to Existing Projects.
Project migration may involve cross-version upgrades and depends on the upgrade image project-migration. If the image is missing, you cannot select the target project normally.
1. Log in to FineOps that is connected to the target project as the admin, choose Maintenance Center > Project Migration > Pre-migration Check, and check whether the target project can be selected normally.
2. If the target project cannot be selected, the corresponding version of the project-migration image is missing.
3. You are advised to upgrade FineOps to the latest version to obtain the built-in project-migration image.
4. Or you can contact FanRuan technical support to obtain the project-migration image package, and upload the image to the image repository of FineOps where the target project is located according to Pushing a Single Image to the Repository.
The version of the System O&M plugin affects how the project migration tool is used. Be sure to upgrade it to the latest version.
1. Ensure FineOps has been upgraded to the latest version, namely, V2.26.0 or later.
2. Log in to the source project and target project separately.
3. Choose System Management > Plugin Management and upgrade the System O&M plugin to the latest version. For example, if the FineOps version is V2.26, the plugin version should be V3.26.
The following operations may upgrade the source and target projects, change their configurations, and copy files.
As a precaution, perform a full project backup before operations, including the project, external configuration database, cluster components, and so on.
You are advised to create project snapshots on the servers where the source and target projects are located, for version control, rollback, and locating changes that caused issues.
If project snapshots cannot be created, at least back up both the source and target projects on FineOps. For details, see Project Backup.
Before migration, both the source project and target project must be alive and available, and they cannot be the same project.
The pre-migration check verifies whether the source and target projects are compatible and whether they meet migration requirements.
If the pre-migration check fails, Export Migration Package and Automatic Migration cannot be performed.
You must execute the pre-migration check.
1. Log in to FineOps as the admin and choose Maintenance Center > Project Migration > Pre-migration Check.
2. Select projects:
If both projects are connected to the same FineOps platform, select them at the same time for comparison.
If they are connected to different FineOps platforms, check them separately, and then download the results locally for comparison.
3. Click Start Inspection. The page refreshes every three seconds to display the progress. Do not switch to another page, or the check may be interrupted.
4. After the check is complete, click Download Inspection Report, and then evaluate and process risk items according to the following sections.
Regardless of which migration plan is selected, the configuration database will be migrated and adjusted, so consistency between the two projects' configuration databases must be checked.
Requirement: The target project must have an external database enabled as its configuration database.
Solution: See Cluster Management to configure an external configuration database for the project.
Requirement: The configuration databases used by the source and target projects must meet the required database types and versions.
Solution: See Cluster Management to replace the project with a compliant external configuration database.
Requirement: If the source and target projects use MySQL configuration databases, they must use the utf8mb3 character set.
Reason:
The character set encoding of the configuration databases used by the source and target projects should be consistent, or garbled text may occur after migration.
FanRuan configuration databases support only utf8mb3 (also called utf8) and do not support utf8mb4.
Solution:
If the source project uses utf8mb4, contact FanRuan technical support to locate and modify four-byte characters in the configuration database, so migration to a target configuration database using utf8mb3 is not affected.
If the target project uses utf8mb4, see Cluster Management to replace it with a compliant external configuration database.
Requirement: The collation of the source and target projects' configuration databases must be case-sensitive.
Collation should be consistent, or data queries, file references, and other operations may not match after migration, affecting normal project operation.
FanRuan configuration database supports only case-sensitive collation and does not support case-insensitive collation.
If the source project's collation is case-insensitive, contact FanRuan technical support for assistance.
If the target project's collation is case-insensitive, see Cluster Management to replace it with a compliant external configuration database.
Requirement: The configuration database users used by the source and target projects must have full DDL privileges on the configuration database, such as privileges to create, modify, and delete database structures, to satisfy configuration table schema and configuration information adjustments.
Solution: Consult the corresponding documentation of the database you use and grant DDL privileges to the database users.
The migration tool helps migrate necessary files, so you do not need to migrate them manually.
Directories that are always migrated include resources, classes, dpworks, config, and plugins in Project installation directory/webroot/WEB-INF.
Directories that can be selected for migration include (which are not migrated if unselected): reportlets, schedule, assets (excluding temp_attach), and assets/temp_attach in Project installation directory/webroot/WEB-INF. (If these directories are not migrated through the tool, after the migration finishes, manually upload files from the source project to the corresponding folder in the mounting directory of every project node in the target project.)
Content Description:
In the source project's /webroot and /webroot/WEB-INF paths, user-created folders are considered directories beyond the migration scope and must be migrated manually.
The inspection report lists file counts and file sizes for all user-created folders in the source project's /webroot and /webroot/WEB-INF paths.
Suggested Action:
1. Before migration, evaluate the source project and:
If it does not affect template resource references, merge directories beyond the migration scope into /webroot/help.
2. If they cannot be merged into help before migration, after the tool finishes:
Use Developer Mode to add corresponding mounting directories to the target project.
Manually migrate those directories to the corresponding mounting directory of every target project node.
In the source project's /webroot and /webroot/WEB-INF paths, some folders are created by FanRuan applications and are not migrated by default.
Non-migrated directories include (which are not listed in the inspection report if they do not exist):
upm, scripts, logs, backup, help in Project installation directory/webroot
embed, cache, assist, local, spark_temp, treasures in Project installation directory/webroot/WEB-INF
These directories contain logs, cache, rollback files, and similar content. Evaluate migration impact and necessity yourself.
For example, manually migrating the embed folder causes the source and target projects to connect to the same external configuration database after migration, causing abnormal project operation.
If custom resource files are stored in these directories, handle them using the same method of handling directories beyond the migration scope.
Non-official JAR packages include customized function JAR packages and third-party driver packages not officially provided by FanRuan. They are not migrated by default.
The inspection report lists non-official JAR packages in /webroot/WEB-INF/lib and /webroot/WEB-INF/customlib of the source project.
1. Before migration, evaluate the impact on this content. FanRuan cannot guarantee that these JAR packages will still work after migration.
2. After the migration tool finishes, manually upload all listed non-official JAR packages to the customlib folder in the mounting directory of every project node in the target project.
3. After the target project starts, confirm each non-official JAR function works.
Static resources are JS, CSS, HTML files, and so on, usually referenced by template files.
The inspection report lists JS, CSS, HTML, and other static resources in /webroot and /webroot/WEB-INF of the source project.
1. Before migration, evaluate the impact on this content. FanRuan cannot guarantee whether reference paths in templates will change after migration.
2. After the target project starts, confirm corresponding templates can still be previewed and used normally.
Non-market plugins refer to plugins without FanRuan official signatures, possibly third-party customized plugins.
The inspection report lists custom plugins in /webroot/WEB-INF/plugins.
1. Before migration, evaluate the impact on this content. FanRuan cannot guarantee that plugins will still work after migration.
2. After the target project starts, confirm corresponding plugin functions are normal.
The default servlet for FanRuan projects is webroot/decision.
You may have changed the default servlet because of short-domain access, security considerations, project-name changes, and similar reasons.
The inspection report lists the source project's servlet.
1. If the source project's decision part was modified:
Before migration, log in to the source project and change the servlet path name to decision under System Management > System Setting > General.
2. If the source project's webroot part was customized:
The migration tool automatically adjusts the target project's project name during migration to match the source project.
You can later change the access path in Developer Mode.
The following sections describe the migration steps for automatic migration and export-import migration.
1. Migration operations are mutually exclusive. Only one migration task can be executed at a time.
2. During migration, the selected source and target projects cannot be changed.
3. When you re-enter the page, the system automatically restores progress display for unfinished tasks.
This section illustrates how to achieve export, transfer, import, and upgrade with one click. It applies when both projects are connected to the same FineOps platform.
Log in to FineOps as the admin and choose Maintenance Center > Project Migration > Automatic Migration.
1. Select the source project and target project.
If a project does not meet the requirements in the "Applicable Project" section, it cannot be selected.
2. Select migration content.
This determines whether tasks under System Management > Task Schedule in the source project are migrated to the target project.
If Scheduled Task is not selected, new scheduled tasks must be manually created in the target project after migration.
If Scheduled Task is selected, task configurations and execution plans are migrated to the target project. This may cause the source and target projects to trigger the same task at the same time. After migration, evaluate whether to pause the scheduled tasks in the source project.
3. Select migration directories.
These include reportlets, schedule, assets (excluding temp_attach), and assets/temp_attach in /webroot/WEB-INF of the project.
Migration of these directories is recommended. However, since the files may be large and tool-based migration may be less efficient, you can decide whether to use the tool or copy and paste them manually for migration.
If selected, the migration tool migrates these files during migration, but the migration will take longer. Wait until the migration is complete.
If not selected, after the migration tool finishes, you need to manually upload the files from the source project to the file server of the target cluster project, or to the corresponding folder in the mounting directory of the target standalone project's application node.
It stores FineReport templates (not applicable to FineDataLink projects).
If it is not migrated, all FineReport templates in the project will be lost.
It stores files generated by FineBI/FineReport scheduled tasks (not applicable to FineDataLink projects).
If it is not migrated, result reports mounted to the decision-making platform by scheduled tasks cannot be accessed.
It stores FineReport template backup files and serves as the general shared persistent directory.
If the project does not use FineReport templates, or does not need to restore historically developed FineReport templates, the VCS folder does not need to be migrated.
Other folders are required for normal project operation. If they are not migrated, normal use will be affected.
It stores FineBI data table information and FineReport read/write cache.
This folder stores original Excel file information for the project. If it is not migrated, original Excel files will be lost.
It also stores read/write (image) cache. If it is not migrated, the template background image will be empty during previewing.
4. Enter direct transfer configuration.
This is the key point that determines whether automatic migration uses direct transfer migration or relay transfer migration.
If you want to use direct transfer migration, enter SSH connection information for any node of the source project. The prepared user must have read permission. The SSH connection test applies to both project SSH connectivity and file server connectivity. If the connection fails, the page displays the failure reason, such as connection failure or no permission for the help path.
If you want to use relay transfer migration, skip this step.
5. Click Start Migration.
Based on the SSH information, the tool automatically checks network connectivity from the target project to the source project and its file server, determines the final transfer plan, and completes the following in sequence:
Direct transfer migration: source project - transfer files via SSH -> target project.
Relay transfer migration: source project - compress files and transfer archive -> FineOps - transfer archive -> target project - decompress the file.
After migration is complete, you can view the result on the page and download the migration report.
This section applies when the two projects cannot be connected to the same FineOps platform, or when the migration files are very large.
Exporting a Migration Package
Log in to FineOps that is connected to the source project as the admin and choose Maintenance Center > Project Migration > Export Migration Package.
1. Select the source project.
Ensure the project meets the requirements in the "Applicable Project" section. Otherwise, the package cannot be imported into the target project later.
2. Select migration directories.
These include reportlets, schedule, assets (excluding temp_attach), and assets/temp_attach in/webroot/WEB-INF of the project.
3. Click Start Export.
Wait for the migration package export to complete, and then locate the corresponding migration package according to the prompt.
For FineOps-deployed projects, the exported migration package is stored in /help/migration/integrate in the mounting directory of any project node in the source project.
For non-FineOps-deployed projects, the exported migration package is stored in /webroot/help/migration/integrate in any project node of the source project.
Uploading the Migration Package
Manually copy the migration package obtained in the previous section to the target project.
1. For FineBI projects:
Upload the migration package fr-bi.zip to Every project mounting directory/bi-web/help/migration/integrate of the target project. If this directory does not exist in help, create it manually.
Decompress the migration package bi-engine.zip to obtain a classes folder, then upload the classes folder to the polars folder in the mounting directory of every Engine - Calculation Node component of the target project. If the directory does not exist, create it manually.
2. For FineReport projects:
Upload the migration package fr-bi.zip to Every project mounting directory/fr/help/migration/integrate of the target project. If this directory does not exist in help, create it manually.
3. For FineDataLink projects:
Upload the migration package fdl.zip to Every project mounting directory/fdl/help/migration/integrate of the target project. If this directory does not exist in help, create it manually.
Importing a Migration Package
Log in to FineOps that is connected to the target project as the admin and choose Maintenance Center > Project Migration > Import Migration Package.
1. Select the target project.
Ensure the project meets the requirements in the "Applicable Project" section. Otherwise, the package cannot be imported.
3. Click Start Import.
The migration tool imports the resource package manually uploaded in the previous section into the target project. Wait for migration to complete.
Choose Maintenance Center > Project Migration > Migration Record to view historical migration details.
1. Records are sorted in reverse chronological order with the following information displayed: serial number, operation time, end time, operator, source project, target project, migration type (automatic/manual), status (success/failure), and remark.
2. You can download migration reports of successful records.
3. Error information is displayed for failed migrations. Only failed automatic migrations support Retry Import. Failed manual export and manual import do not support retry.
4. After you click Retry Import, you will be redirected to the Automatic Migration tab page with the migration progress dialog.
Check the migration records to see whether any files were not migrated successfully, and manually migrate them if needed.
According to the customized content check in the "Checking Customized Content" section, manually migrate the required content to the corresponding location in the target project.
Manually migrate any migration directories not selected during migration to the corresponding location in the target project.
Determine whether to pause the scheduled tasks in the source project if Scheduled Task is ticked for migration.
After successful migration, the target project is stopped and must be started manually.
1. Log in to FineOps as the admin, select the target project, and choose Maintenance > Component Management.
2. Perform one-click Start for the FineBI - Application Node/FineReport/FineDataLink component.
3. Confirm that all bi-web/fr/fdl containers start and are in the running status.
1. Log in to the target project as the admin and choose Public Data > Global Update.
2. Execute Global Update Now to extract the latest data and store it in the correct storage path.
1. The target project version must not be earlier than the source project version, and the target project cannot be a non-FineOps-deployed project.
2. If the pre-migration check fails, export and automatic migration will be rejected.
3. Migration operations are mutually exclusive. Only one migration task can run at a time, and project selection cannot be changed during migration.
4. Import operations restart the target project. The business tasks of the corresponding project shut down during FineDataLink migration.
5. Direct transfer migration depends on SSH connectivity. If SSH is unavailable, the process automatically degrades to relay transfer migration, increasing both migration time and difficulty.
6. When using relay transfer migration or export-import migration, ensure the remaining disk space on related disks is greater than 50 GB.
7. When using two FineOps platforms for export-import migration, ensure the versions of the two FineOps platforms are the same.
8. Warning: Do not manually migrate the embed folder. Doing so causes both projects to connect to the same external configuration database, resulting in abnormal project operation.
9. Migration involves configuration changes and file copying. Before operation, be sure to perform a project backup or project snapshot.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy