After installing FineBI, you can see the installation files by entering the installation directory. The FineBI installation file is essentially a software, Tomcat. This article will introduce the structure of installation directory in detail.
The content of each file is shown as follows:
File
Content
.install4j
Pictures of FineBI
bin
l For the directory where the startup files of BI project are located, you can modify the memory size and encoding way of BI allocation in finebi.vmoptions.
l The ROOT folder in this directory includes all data forms and temporary data forms. It is also the storage location for updating data by default. You can adjust its location by yourself. For details, see Data Update Composition and Storage.
l The output.log folder in this directory stores the information output when visiting the front end.
l The log related files in the bin folder can be cleaned up.
jre
It supports the use of the Java app in the Java runtime environment.
lib
It stores the JAR package that loads animation when BI starts.
logs
It includes project operation logs and GC logs. Note: Clearing it usually has no impact on operation.
server
It is the root directory of Tomcat, including the configuration folder of Tomcat and its own dependent folder.
temp
l It stores temporary files generated during the running of Tomcat.
l It is also the cache path for exporting the Excel file. You can change the location of the cache by modifying the parameter Djava.io.tmpdir=.\temp in the file finebi.vmoptions of the directory %fineBI%/bin.
l Folders can be deleted after the project is down to free memory.
Note: It is not recommended to clean the temp temporary directory when the project is running. You can clean it when the project is shut down. If an error is displayed after cleaning, you need to restart the project.
webapps
It stores apps and loads the apps in the webapps directory when the server starts.
LICENSE
It records some terms of Tomcat and other contents.
NOTICE
It records new notifications and announcements in Tomcat.
RELEASE-NOTES
It records the description of released versions, some bundled APIs, new features, and so on.
RUNNING.txt
It records the running environment of Tomcat and how to configure parameters, variables, startup, and so on.
uninstall.exe
It originally has an uninstaller exe. You can enable the uninstallation function by double click.
Demo_files
It stores the DEMO that comes with the project and display needed documents.
It stores log files and records system login information, template visit information, error reporting information, and so on.
WEB-INF
It is the main directory of BI project.
Web Component. html
It is a web component; which just needs to enter the hyperlink address. Supposing it is a customized HTML file, it will be placed into the directory %/webroot/ within the project.
assets
It is a resource folder, storing resource files and other files used in the project.
Among these files, the uploaded images and Excel data are stored in temp_attach.
assist
It is an auxiliary folder, storing some auxiliary files.
classes
It stores the directory of the class file.
embed
It includes the directory of database configurations.
It is the JAR package folder that the BI project depends on.
reportlets
It stores the cpt and frm files of the FineReport reports.
resources
It stores project-related resource configuration files.
treasures
It includes the function points of reports and the buried point information of BI. Usually, it will be automatically generated once a month.
direct
It stores the configuration information related to real-time data.
cpu.xml
It is the switch of the CPU, which can be used when you face the problem that dealing with sigard causes the JVM virtual machine to crash.
FanRuan.lic
It includes project certificate files.
There is an error.log file in the directory %FineBI_HOME%\\bin of some users' projects. The file will not be split according to the date. It records all logs in the error level and some information related to info.
If you feel that the file occupies too much disk space, you can delete it manually, set a script to delete it regularly, or set a script to monitor the size of it.
Note:
1. It is recommended to confirm whether the log fanruan.log is sufficient or not, then to consider whether to delete the error.log file or not.
2. If the project is deployed in the container of the Tomcat, there will be no error.log file in the bin directory.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy