I. Overview
1. Function introduction
In order to meet the new needs of customers and improve the shortcomings of some functions of the previous version, our products are constantly updated and iterated.
If you need to fix some problems in the previous version and add new product features, you need to upgrade to the current latest version.
FineReport 10.0 has a built-in one-key upgrade function, which makes the upgrade more convenient.
2. Upgrade logic
Note 1: 8.0 upgrade to 10.0, first upgrade to 9.0, then upgrade to 10.0. For 8.0 upgrade to 10.0.
Note 2: Before the user upgrades, in order to avoid file loss due to upgrade failure, please back up the required files before upgrading. Backup can refer to: backup and restore.
1)There is no built-in upgrade function between FineReport 9.0 and 10.0, users can complete it through the upgrade tool.
2)The upgrade between version 10.0 is generally a fixed JAR package update, and there may also be cases where JAR packages are added or deleted. The automatic update function of JAR package versions after 2019-12-05 has changed.
For versions before 2019-12-05, automatic update is not convenient enough. When you need to add or delete JAR packages, you can only perform manual update operations.
For versions after 2019-12-05, automatic updates can automatically add or delete JAR packages.
3)In order to prevent the risk that subsequent updates may cause the JAR package to be removed, there are some restrictions when updating the version before 2019-12-05.
The JAR package is automatically updated and upgraded before 2019-12-05, and it can only be updated to the version of the JAR package at 2019-12-05.
The JAR package is updated and upgraded in 2019-12-05 and later versions, and the upgrade to the current latest version is allowed.
Example: The current version JAR package time is 2019-05-20, and the latest version JAR package time is 2020-04-26. Users can only upgrade to the version with the JAR package time of 2019-12-05 before continuing to upgrade to the version 10.0 with the JAR package time of 2020-04-26.
II. 9.0 upgrade 10.0
To help users upgrade from version 9.0 to version 10.0 more smoothly, we provide an independent auxiliary upgrade program that can upgrade the 9.0 Web project to the 10.0 project, including compatibility of JAR packages, various configuration files, and FineDB data tables. upgrade.
The auxiliary upgrade tool does not need to be installed, it is click-to-use, simple and convenient.
Note 1: The upgrade tool currently only supports jdk1.8, users should ensure that their jdk is version 1.8 when upgrading.
Note 2: After 9.0 upgrade to 10.0, it is recommended that the new version of the external database is different from the old version; if users want to use the same external database, they need to delete all the project information of the old version in the external database, otherwise it may cause some problems due to the inconsistent table structure.
III. JAR package upgrade after 2019-12-05
1. Designer upgrade
1)Direct update and upgrade
Open the designer, click the menu Help>Update&Upgrade, the new version number will appear in the latest JAR column, and there will be an update button below, as shown in the following figure:
Note: The "Update&Upgrade" function is not supported in the remote design state.
After the update is triggered, the system prompts to save important information, as shown in the following figure:
When the designer is updated, there will be a delay of several seconds due to the need to obtain and parse the comparison JS. The update information is obtained, as shown in the following figure:
Follow the prompts to update, the progress of downloading the JAR package is displayed below, as shown in the following figure:
Wait for the preparation work to be completed, the system will automatically restart immediately.
After restarting, the latest JAR column is displayed as "lateset version already", and the 10.0 version update is completed.
2)Plugin management triggers an upgrade
When the new plugin manager is opened, as shown in the following figure:
Click on the Server>plug-in management, if it is detected that the JAR package of jxbrowser does not exist, a mandatory upgrade prompt box will pop up, as shown in the following figure:
Click OK or close the prompt box, and you will be redirected to the update interface. The subsequent update steps are shown in chapter III.1.1).
Note: When the designer is manually updated to version 10.0.18, the JAR package of jxbrowser needs to be added jxbrowser-7X.jar, jxbrowser-swing.jar, jxbrowser-XX.jar (XX refers to the system version) stored in %FR_Home%/ Under lib, the JAR package of the original jxbrowser needs to be retained. Please contact FanRuan technical staff for the JAR package.
2. Server upgrade
Open the decision-making platform, click the Update Now button in Manage>Intelligent Operations>Backup and Restore>Update Upgrade, wait for the JAR to be updated, and restart the Web server after success.
Note: After the platform is updated and upgraded, you need to shut down the Tomcat process through Ctrl+C / kill. There are certain risks in using other methods.
IV. JAR package upgrade before 2019-12-05
1. Designer upgrade
1)Method 1: Update JAR package online
Open the designer, click the menu Help>Update&Upgrade, the new version number will appear in the latest JAR column, and there will be an update button, as shown in the following figure:
Note: The "Update&Upgrade" function is not supported in the remote design state.
Follow the prompts to update, the progress of downloading the JAR package is displayed below, as shown in the following figure:
Wait for the preparation work to be completed, and click Restart now.
After restarting, the latest JAR column is displayed as "latest version already", and the 10.0 version update is completed.
2)Method 2: Manually update the JAR package
Ask FineReport technicians for 13 upgrade JAR packages:
fine-accumulator-10.0.jar, fine-activator-10.0.jar, fine-core-10.0.jar, fine-datasource-10.0.jar, fine-decision-10.0.jar, fine-decision-report-10.0, fine- report-designer-10.0.jar, fine-report-engine-10.0.jar, fine-schedule-10.0.jar, fine-schedule-report-10.0.jar, fine-swift-log-adaptor-10.0.jar, fine- third-10.0.jar, fine-webui-10.0.jar
fine-report-designer-10.0: This JAR package contains all the functions of the FineReport designer and must be updated and stored under %FR_Home%/lib, as shown in the following figure:
Other JAR packages: When upgrading to the version, you need to put the remaining 12 JAR packages under %FR_Home%/webapps/webroot/WEB-INF/lib, as shown in the following figure:
Note: After updating the JAR package, the designer needs to be restarted to take effect, and the JAR package cannot be placed in the wrong position, otherwise the designer cannot be opened.
3)Method 3: Management upgrade of decision-making platform
Click the Update Now button in Manage>Intelligent Operations>Backup and Restore>Update Upgrade, wait for the JAR to be updated, and restart the designer after success. As shown below:
2. Server upgrade
Note 1: Please check Upgrade Compatibility first when upgrading the version. Some version upgrade methods may be different.
Note 2: The JAR version on the server and the designer must be the same, otherwise it may cause the local preview of some templates to be normal, and there will be problems with the preview under the server.
1)Method 1: Manually update the JAR package
The user can manually replace and update the JAR package after obtaining it. The operation mode is the same under linux system and windows system.
Users can ask for the following 12 upgrade packages from FineReport technicians, or copy them in the installation directory %FR_Home%/webapps/webroot/WEB-INF/lib after installing the latest version of the designer.
fine-accumulator-10.0.jar, fine-activator-10.0.jar, fine-core-10.0.jar, fine-datasource-10.0.jar, fine-decision-10.0.jar, fine-decision-report-10.0.jar, fine-report-engine-10.0.jar, fine-schedule-10.0.jar, fine-schedule-report-10.0.jar, fine-swift-log-adaptor-10.0.jar, fine-third-10.0.jar, fine- webui-10.0.jar
After obtaining it, replace the previous 12 JAR packages under the server project %TOMCAT_HOME%/webapps/webroot/WEB-INF/lib, and restart the server to complete the upgrade.
Note: After the JAR package is updated, the server needs to be restarted to take effect. Under Linux system.
2)Method 2: Management upgrade of decision-making platform
Click the Update Now button in Manage>Intelligent Operations>Backup and Restore>Update Upgrade, wait for the JAR to be updated, and restart the Web server after success. As shown below:
Note: After the platform is updated and upgraded, you need to shut down the Tomcat process through Ctrl+C / kill. There are certain risks in using other methods.
