In practical use, there are scenarios where the FineReport project needs to be integrated into the FineBI system.
Integrating FineReport into FineBI allows these two software products to be merged into a single system, requiring only one set of application services to maintain.
After the integration, the user and permission systems, portals, and management systems of both FineBI and FineReport are unified. Users only need to log in to one platform.
You can choose the appropriate integration solution as needed.
You have not deployed any projects.
You want to deploy a project with both FineBI and FineReport functions.
1. Deploy a FineBI project, which includes FineReport-related JAR files by default.
2. When registering the license, purchase FineReport-related function points.
3. When creating FineReport templates, use the designer to remotely connect to this FineBI project.
For details, see Remote Connection Between the FineReport Designer and the FineBI Project.
You already have a FineBI project (with dashboards or platform configurations).
You want to add FineReport-related functions.
1. You do not need to redeploy the project. The FineBI project already includes FineReport-related JAR files by default.
2. Purchase additional FineReport-related function points for the license
3. When creating FineReport templates, use the designer to remotely connect to this FineBI project
You already have a FineReport project (with templates, but no platform configurations).
2. Follow the steps in this document.
You already have both a FineReport project and a FineBI project (with dashboards, templates, and configurations).
You want to merge the two projects into one project.
Follow the steps in this document.
You already have both a FineReport project and a FineBI project (with dashboards, templates, and platform configurations).
You want to keep both projects without integration, but you want to unify portal access to templates/dashboards.
You can use the Multi-Product Connection Tool plugin to mount templates across projects.
Based on project access volume and data volume, increase the memory, CPU, disk, and other configurations of the FineBI project to ensure the integrated project runs properly.
For details, see Confirming Server Configuration of the FineBI Project.
Before operation, ensure that the versions of FineBI and FineReport are compatible.
1. Confirming FineBI module version compatibility
Log in to FineBI as the admin and choose System Management > Registration Management > Version Information.
Check the versions of the report module and BI module, and refer to FineBI and FineReport Version Compatibility Instruction to confirm version compatibility.
2. Confirm FineBI and FineReport version consistency
Log in to the decision-making platform as the admin and choose System Management > Registration Management > Version Information.
Check the report module version of FineReport and compare it with the report module version of FineBI from the previous step to confirm they are exactly the same, down to the JAR package level.
If the versions are inconsistent, upgrade or downgrade one of the projects to ensure consistency; otherwise, integration will not be possible.
For details about minor version upgrade guidelines, see Guide to Update Project Minor Versions and How to Upgrade Non-Containerized FineBI Within 6.0.x (Minor Versions).
The configuration database refers to FineDB. The solution in this document can only retain the configuration database of the FineBI project.
For FineReport project configurations, back them up or take screenshots for archiving, and manually reconfigure them after integration.
You can refer to Closing or Restarting the FineBI Project to shut down both FineReport and FineBI projects.
Copy the relevant files from the FineReport project to the corresponding locations in the FineBI project.
If there are duplicate files, you are advised to keep the FineBI files and not overwrite them.
/webroot/WEB-INF/lib
Function: Crucial for the project, it stores the original/externally imported JAR packages, providing all the basic functions of the project.
Copy required: yes
If there are duplicate files, be sure to keep the FineBI files and do not overwrite them.
/webroot/WEB-INF/plugins
Function: It stores plugin-related files.
Copy required: yes. Otherwise, plugin-related functions will be affected.
/webroot/WEB-INF/reportlets
Function: It stores FineReport templates.
Copy required: yes. Otherwise, all the templates in the project will be lost.
If there are duplicate files, evaluate each one individually or create a directory under reportlets to store them
/webroot/WEB-INF/resources
Function: It stores report information and configuration information.
Copy required: optional
Do not copy the FanRuan.lic file from this directory to the FineBI project.
Copying the license file across projects may cause both old and new projects to be unable to use the license.
If license migration is needed, perform it after project integration is complete.
/webroot/WEB-INF/schedule
Function: It stores files generated by scheduled tasks.
Failure to copy it will cause the result reports from the scheduled tasks mounted to the decision-making platform to be inaccessible.
/webroot/WEB-INF/classes
Function: It stores default and custom class files called by the project.
Custom class files may exist. Failure to copy it will affect normal project operation.
/webroot/WEB-INF/assets/temp_attach
Function: It stores read and write cache paths.
This folder contains read/write (image) caches for the project. Failure to copy it may result in empty background image previews in FineReport templates.
/webroot/WEB-INF/assets/vcs
Function: It stores backup files of FineReport templates.
If the project does not require a rollback of the historical development of the FineReport template, there is no need to copy and paste it.
/webroot/WEB-INF/assets/other_files
Function: They store generally shared persistent directories.
It stores the files required for the normal operation of the project. Failure to copy it will affect the normal use of the project.
/webroot/backup
Function: It stores historical backup files of the project.
Copy required: optional. You do not need to copy and paste backups that can be stored in the original directory.
/webroot/help
Function: It stores custom content of the project.
The folder contains custom maps, custom functions, customized CSS, customized JS, and other files. Failure to copy it will cause abnormal template previews.
/webroot/logs
Function: It stores Swift logs.
If you do not copy and paste it, LogDB (the historical operation logs of the project) will be lost. There will be no data under Platform Management > Platform Log.
You do not need to copy and paste it if historical usage information is not required.
If there are duplicate JAR files, keep the original FineBI ones and do not replace them
If related configurations are exported in the "FineReport Configuration Database Backup" section, you can choose to import them into the FineBI project as needed.
If you need to migrate the FineReport project license to FineBI, additional FineBI-related function points must be purchased. Contact our sales personnel for confirmation.
Do not directly place the FineReport project license file into the FineBI project.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy