Notice After the Upgrade

Version

Application Scenario

This document introduces what you should do and pay attention to after the major version upgrade.

Migration of the External Database Configured on the Original Server After the Upgrade

After the upgrade tool is used, the external database is turned into built-in FineDB databases. If you need to migrate the external database to your own database, you can refer to External Database Configuration.

Strictly follow the codes and other instructions for table creation according to the corresponding database document, otherwise the migration will be unsuccessful.

Note:

1. The upgrade tool reads the data to generate a built-in database for upgrade and modification, modifying no data in the original external database.

2. To be independent from the external database in the old version and not affect the previous environment, you can create a database under the same user where the original external database is created for migration. When the FineReport 11.0 can run stably, you can delete the external database of FineReport 10.0.

Difference Between the External Database and Data Connection

1. Data connection

Data connection is established to obtain data from databases in the report template. The data (usually your own business data) can be used in the designer for template creation.

2. External database

External database refers to migrating the configuration database FineDB, which contains information such as project directories, permissions, and users, to one's own database in order to improve performance or facilitate management.

This database is very important and cannot be modified at will. For details about FineDB, see FineDB Database Introduction.

Remote Design

1. The FineReport 11.0 project can only be connected through the FineReport 11.0 designer. So after the upgrade, you need to install the FineReport 11.0 designer by clicking https://www.finereport.com/en/download2.

2. For details about remote design connection methods, see Remote Design.

Synchronizing Data and Templates of FineReport 10.0 in FineReport 11.0

Synchronizing Data Connection and Other Configurations

You can replace the finedb folder in the FineReport_11.0\webapps\webroot\WEB-INF\embed path in FineReport 11.0 with the finedb folder in the FineReport_10.0\webapps\webroot\WEB-INF\embed path in FineReport 10.0. After replacement, restart the designer.

Synchronizing Report Template Files

You can copy all template files in the FineReport_10.0\webapps\webroot\WEB-INF\reportles path in FineReport 10.0 and paste those files in the FineReport_11.0\webapps\webroot\WEB-INF\reportles path in FineReport 11.0. This operation does not require a restart.

Synchronizing Plugins and JAR Packages Between the Designer and the Server

When you connect the designer to the server for remote design, the JAR package versions of the designer and server must be consistent. Otherwise, a series of problems will be caused during the design process. If the JAR packages of the server and the designer do not match, a pop-up window appears: "Remote Design will be partially affected by inconsistent versions." when you switch the working directory to the remote server in the designer (by directly switching in the menu or by clicking OK in the working directory configuration pop-up window), or when the designer connected to the remote server starts. For details, see FAQs of Version Mismatch Between JAR Packages and Plugins.

The FineReport 11.0 report server cannot be added in DataAnalyst V10. Therefore, you need to download the DataAnalyst V11 because online updates are not available currently. Apps with OEM (Original Equipment Manufacturer) customization need to be re-customized. For details, see App OEM Introduction.

1. To download the DataAnalyst V11, you can click https://www.finereport.com/en/download2 or scan the QR code as required.

2. Apps that have been packaged in FanRuan Market need to be repackaged. For details, see App OEM.

The Report Detection function is added in FineReport 11.0.3 and later versions and Report Frontend Exception Prompt is enabled by default. The related exceptions are shown in the following figure. To stop receiving prompts, you can disable Report Frontend Exception under System Management > System Setting > General. For details, see section "Report Detection" in General.

You need to contact the business personnel (business@fanruan.com) to obtain the migration program for official authorization migration.

Unprocessed Official Authorization of the Old Project Before the Upgrade

Send an email in the following format to the business personnel.

Note:

Indicate the special circumstances (if any) in the email.

List	Content	Note
Sender	The email address specified in the contract	If you do not use the email address specified in the contract to send the email, the migration will be rejected.
Recipient	business@fanruan.com	/
Title	Official Authorization Document of Company Name's Registration for FineReport	If you do not mark the company name in the email, the registration will be rejected.
Body	Company name: Company name Project name: Project name Contract signing date: YYYY/MM/DD Registration method: Local Machine Info	Other information like concurrency and the number of users will be registered according to the   signed contract.
Attachment One	The FanRuan.lic file in the %BI_HOME%/webroot/WEB-INF/resources path of the   old report project	/
Attachment Two	The .rif file exported from the new report project	Do not open   the generated RegistrationInformation.rif   file, otherwise, the file will be damaged and cannot be used for   registration.
Attachment   Three	The page screenshot (in System   Management > Registration   Management) of the old report project	1. The server address must be included in the screenshot and the project   must be operated normally. Note: The old report project needs to be started normally on the original server. Otherwise, the registration information cannot be migrated. You can only contact with the sales personnel to apply for authorization again. 2. Registered Successfully   (the mark for successful registration) must be displayed on the Registration Management of the   screenshot. Note: The registration information cannot be migrated if the registration of the current project is unfinished, temporary, or expired. You can contact the sales personnel for additional purchase or communication.

Since authorization migration requires a screenshot displaying the successful registration of the official authorization in the old project, you need to restore the original project, or install the deployment package on the server to register the original official authorization first before migration if you have not processed the official authorization of the old project before the upgrade. This step is cumbersome, and you can contact FineReport official technical support for assistance.

Destroyed Original Authorization Before the Upgrade

Send an email to the business personnel according to the upgrade team's requirements.

Use the email address specified in the contract and send the registration information to FineReport business personnel (business@fanruan.com). The email format is shown as follows.

Note:

Indicate the special circumstances (if any) in the email.

The report access method does not change when the project upgrades from 10.0 to 11.0. Access links of the platform and template change when the project upgrades from 9.0 or 8.0 to 11.0. The report access method for the project 11.0 is as follows:

1. Platform access URL: http://IP address:Port number/webroot/decision (webroot is the project name and decision is the Servlet name)

2. Template access URL: http://IP address:Port number/webroot/decision/view/report?viewlet=xxx.cpt or xxx.frm

3. Administrator username and password: Username and password that are customized initially. If you forget the username or password, you can refer to Modifying/Forgetting the Password as Admin.

4. System parameter: System Parameter

5. Built-in function summary: Designer Function Summary

6. Description of the important configuration file FineDB table structure in the report project: FineDB Table Structure

7. SSO: Frontend SSO Interface