I. Report installation root directory
The path of the report installation root directory is: %FR_HOME%\, and the folders contained in the directory are as shown in the figure below:
The contents of each folder are shown in the following table:
| Folder | Contents |
|---|---|
| .install4j | Picture of designer |
| bin | Various executable files, startup directory, startup programs including designer, built-in server, documentation, and Demo |
| designerbackup | After using the online update plugin to upgrade, back up the old version of the JAR package by date |
| iisFilter | File for IIS integration, filter used by IIS server |
| jre | Java runtime environment |
| lib | Part of the JAR package that the designer depends on |
| logs | Store system GC logs, which can reflect the load of the system |
| plugins | Store plugin files |
| server | Server configuration information |
| webapps | Web application content, built-in report project, including documents and all templates in Demo |
| uninstall.exe | Double click to uninstall FineReport |
After the designer is installed, by default, a .FineReport100 file will be generated in the C:\Users\<user name>\ directory of the Windows system, as shown in the following figure:
This folder contains FineReportEnv.xml, which is the configuration file of the designer. It saves the settings in the menu bar "File>Options" of the designer, as well as some information about the working directory and the layout of the designer.
II. WEB-INF directory
The path of the WEB-INF folder in the report project is: %FR_HOME%\webapps\webroot\WEB-INF\, and the folders contained in the directory are as shown in the figure below:
The contents of each folder are shown in the following table:
| Folder | Content | Whether can be deleted |
|---|---|---|
| assets | Report background image, chart-related resources, help files and property files for reused components Template version management stored historical version templates | No |
| assist | Some auxiliary tools, such as phantomjs for new charts Temporary files generated by cloud operation and maintenance | No |
| classes | Compiled executable class files such as program datasets | Yes, deleting it may cause errors in the template used in the class file in the built-in demo template, but does not affect the deployment and use of the project |
| config | Some configuration information, such as external database configuration information | No |
| embed | Platform configuration information and platform information, decision-making platform configuration information built-in database finedb | No |
| lib | The JAR package that the web application depends on: Contains product JAR packages, plugin JAR packages, some third-party dependent JAR packages, database-driven JAR packages, etc. | No |
| plugins | Plugin configuration files | Yes, it can be deleted without using the plugin |
| reportlets | Designer built-in demo template | No |
| resources | Designer registration file, template encryption file | No |
| schedule | The result report generated after the scheduled task runs | Yes, but the result report of the scheduled task mounted to the decision platform after deletion is inaccessible |
