Successfully!

Error!

Embedded Deployment

  • Last update:  2020-12-14
  • You will learn

    • Description

    • Copy the directory

      • Copy all

      • Partial copy

      • Copy tools.jar

    • Check if the deployment is successful

    1.Description

    If you want to deploy the report project to an existing web project, you need to copy the report-related files to the destination directory:


    2. Copy the directory

    2.1 Copy all

    For simplicity, you can directly copy the seven folders: assets, assist, classes, embed, lib, plugins, and reportlets under %FineReport_HOME%\webapps\webroot\WEB-INF to %Tomcat_HOME% \webapps\examples\WEB-INF.


    2.2 Partial copy

    You can also decide to selectively copy necessary files to an existing project.

    1) Files that must be copied to WEB-INF

    • lib: JAR packages that start with fine, plus netty-all-xxx.Final.jar and visualvm-xxx.jar;

    • assets: All chart resources are stored here;

    • assist: Files in this folder store some auxiliary tools, such as phantom for new charts;

    • plugins: This folder contains JAR packages and configuration information for plugins;

    • reportlets: This folder is specified by the FineReport server. It cannot be modified and must be lowercase. Sub-directories can be created under this folder and all report templates (.cpt and .frm) must be saved here.

     2) Selectively copied files

    • embed: It stores HSQL and all configuration information. it is recommended to be copied to WEB-INF; otherwise, the deployed project will be viewed as a new project;

    • classes: This folder is specified by the application server. The main function is to store the .class files. If you do secondary development such as custom functions, program data sources, program network reports, etc., you also need to copy the compiled class files to this folder;

    • database driver packages: If the database is connected via JDBC, you need to copy the corresponding database driver package, such as Oracle database driver ojdbc14.jar, to WEB-INF\lib.


    2.3 Copy tools.jar

    Copy tools.jar under %JAVA_HOME%/jdk/lib to the server in case Tomcat Server 500 Error.


    3. Check if the deployment is successful

    You can use browsers to check if the deployment was successful.

    Restart Tomcat, launch the browser and enter http://ip:port/project name/decision. If you see the initialization page, the deployment is successful.


    Attachment List


    Theme: Deployment and Integration
    Already the First
    Already the Last
    • Helpful
    • Not helpful
    • Only read

    Doc Feedback