Overview
Version
Report Server Version
| Functional Change |
|---|
| 11.0 | / |
11.0.10 | 1. Deleted the engine and charmapsvg folders. 2. Migrated the FineReport Reuse folder to FR installation directory\WEB-INF\local. 3. Migrated the border_images and shadow folders to FR installation directory\WEB-INF\local. |
Function Description
This document will introduce the structure of the report installation directory and the contents stored in each folder.
Directory Related to Designer
The installation root directory path of the report is FR installation directory. The following figure shows the folders contained in the directory.
The following table describes the content stored in each folder.
Level One
| Level Two | Description |
|---|
.install4j | / | Designer images |
bin Various executable files and startup directories, including the startup programs for the designer, built-in server, documentation, and Demo | demo.exe | Demonstration program |
designer.bat | Designer startup script |
designer.exe | Designer startup exe |
designer.vmoptions | Designer memory configuration file |
error.log | Error log |
error.ltxt | Error log |
out.log | Log |
restart.class | Program restarter |
restart$1.class | Program restarter |
restart.exe | Program restarter |
restart.vmoptions | Program restarter configuration |
designerbackup | / | After upgrading using the online update plugin, the old version of the JAR packages will be backed up by date. |
iisFilter | / | It stores files generated during IIS integration and filters used by the IIS server. |
jre It supports the use of the Java app in the Java runtime environment. | bin | Content related to JDK |
lib |
ASSEMBLY_EXCEPTION |
LICENSE |
THIRD_PARTY_README |
lib | / | It is used to store some JAR packages that the designer depends on during runtime. It can also store user-customized JAR packages or import external JAR packages. |
logs | / | It stores system GC logs, which can reflect the system loading status. |
plugins | / | It can store plugin files. |
server | / | It stores server configuration information. |
webapps | / | It stores the Web application content, including a built-in report project that contains all templates from the documentation and Demo. The following table describes the details. |
uninstall.exe | / | You can double-click the file to uninstall FineReport. |
Directory Related to Report Project
Project-related folders are stored under FR installation directory\webapps\webroot. The following table shows the folders contained in the directory.
Root Directory
| Level One | Level Two | Description | Whether It Can Be Deleted |
|---|
help | / | / | It stores the built-in demo. You are advised to store any new external resources or related files in this folder. | Yes |
logs | / | / | It stores logs. | Yes |
scripts | / | / | It stores the plugin store script. It is also used for compatibility rollback in v11.0.4 and later versions. | No |
upm | / | / | It is used for compatibility rollback. | Yes |
WEB-INF | assets | / | It stores background images for reports, chart-related resources, help and attribute files for reusable components, and historical version templates stored for template version management. | No |
analyze | It is related to the new computing engine and stores analytical data and cache data from templates. |
clouds | It is related to cloud-based operations and maintenance |
componet | It stores help files and attribute files for reusable components. You are not advised to move or delete this folder. You can try to copy the entire assets folder as a whole during migration. |
check | Inspection reports |
drivers | Files related to driver management |
GeoJSON Introduction | It stores the chart resource files and is used for upgrading compatibility. |
map | It stores the map data, where geographic refers to world map data and image refers to custom image map data. |
temp_attach | Temporary directory for file uploading from the platform. |
tools_plugin | Operation and maintenance tool - inspection files generated by public data management |
scripts | It is used to support compatible upgrades and version rollbacks. |
upm | It stores the plugin management page and resource files (New and old plugin management), which are used to support compatible upgrades and version rollbacks. |
assist | / | It stores some auxiliary tools, such as PhantomJS required by new charts, and temporary files generated by cloud-based operations and maintenance. | No |
btrace | Positioning tool |
clouds | Cloud temporary directory |
update | Temporary directory for update |
removing_files.log | The log |
cache | / | Cache directory |
|
classes | / | Compiled executable class files, such as program datasets | If you delete this folder, errors may occur in built-in demo templates that use these class files, but the project deployment and usage will not be affected. |
config | / | It stores some configuration information, for example, external database configuration details. This folder appears only when certain configuration data is recorded. | No |
embed | / | It stores platform configuration and information, including the built-in database finedb for decision-making platform configurations. | No |
lib | / | It stores JAR packages that the Web application depends on for running, including product JAR packages, plugin JAR packages, some third-party dependency JAR packages, database driver JAR packages, and so on. | No |
local | / | It stores the migrated and post-generated folders.
After previewing the new engine template, the shadow and engine files are regenerated in the local folder. | Yes |
plugins | / | Plugin configuration file | It can be deleted if the plugin is not used. |
resources | / | It stores the designer registration file and template encryption file. | No |
reportlets |
| It stores built-in demo templates in the designer. | No |
schedul | / | It stores the result file generated by Task Schedule. | After deletion, the result report mounted to the decision-making platform by Task Schedule cannot be accessed. |
treasures | / | The storage directory of tracking information files | No |
Cache File
After the designer is installed, a .FineReport110 folder will also be generated by default under C:\Users\<username>\ directory on Windows systems, as shown in the following figure:
The file FineReportEnv.xml in the folder is the designer configuration file. It saves the settings configured in the designer menu bar under File > Option, as well as information such as the working directory and designer layout.
Previous：Generate Security Key File Button
