Fanruan FineReport version upgrade

Recently, there is a need to upgrade the Fanruan report version from 9 to 10, and record the upgrade process for future reference.
Precondition: Successful deployment of Fanruan 10 on the server

版本区别
fineReport 9.0 http://IP:Port/WebReport/ReportServer?reportlet=abc.cpt
fineReport 10.0 http://IP:Port/webroot/decision/view/report?viewlet=abc.cpt

Note: The paths accessed by the two versions are different, such as generating Java package names, report names, etc.
Where modifications are required, please refer to the following items

1) Modify the name of the Java package

The war package read in FineReport 9 version is WebReport.war, and changed to webroot.war after upgrading FineReport 10
Modification method:
can be modified in pom.xmlfinalNameLabel properties, as shown below.

<finalName>webroot</finalName>
2) Replace the report name parameter

The key of the report name of FineReport 9 is directly fromreportletreplace withviewletThat's it.

3) Replace the path

In FineReport 9 version readsReportServerRouting, to FineReport 10 version becomes/decision/view/report, spliced ​​according to its rules, otherwise it cannot be accessed.

Turn off template authentication

When the template authentication is turned on, the login status will be verified. In the management system - template management - authentication configuration, template authentication is turned off, and the request for reading the report is not verified and accessed directly.
insert image description here
Security protection can also be closed, in Security Management - Security Protection, as shown in the figure below.
insert image description here

Editor font changes

After installing the editor of version 10, I found that the default font is really small, which is a test for the user's eyes.

Change method
1) Right click on the Fansoft icon on the desktop - properties page
2) On the Compatibility tab, selectChange DPI settings, check the Override high DPI scaling behavior, selectsystem
3) Restart the editor.
insert image description here

exception handling

1) Problem: The template cannot be found in the directory management-add template, and the built-in template cannot be previewed.
Solution: Templates are generally stored inreportletsUnder the folder, ensure that the folder exists before you can select it. If the cluster is configured, check it in the corresponding path.

Guess you like

Origin blog.csdn.net/u012190388/article/details/130778077