Independent Tomcat Server Deployment in Windows

Tomcat is a free and relatively stable web application server, which is very popular among many small and medium-sized enterprises. This article will introduce how to deploy FineBI 5.0 & 5.1 to the Tomcat server side.

1. Version 

Users need to download and install JDK   in advance Tomcat server. Please refer to the information for Tomcat & JDK installation and configuration steps.

The Tomcat version and the JDK version need to correspond to the operating system. The corresponding relationship between the Tomcat version, the JDK version and the BI version is as follows:

2. Notes

• Multiple BI projects cannot be deployed in the same Tomcat server. The JDK  version is: JDK 1.8 and the minor version needs to be above JDK8u102.

• 32-bit operating systems are not supported.

• Tomcat version 10.0 is not supported.

• When users install JDK  and configure environment variables, when configuring path , it is recommended to add %JAVA_HOME%\jre\bin 

• The installed JDK version must match the operating system. A 64-bit operating system can install a 32-bit JDK, but FineBI does not support such operations and must be unified.

Example deployment steps under Windows system.

1. Preparations

1)  Confirm JDK installation is successful

Call the terminal command, enter java -version and javac , if the following appears, the JDK installation is successful:

2) The Tomcat server has been installed successfully

Double-click startup.batin the %Tomcat_HOME%\bin directory to start the Tomcat server, and enter the command in the browser http://localhost:8080, the web page shown in the following figure appears, indicating that the installation is successful:

2. Copy BI project

Copy the webroot file under %FineBI%\webapps to %Tomcat_HOME%\webapps, as shown below:

Note: The BI project name webroot can be customized and modified, but it should be noted that the address when accessing the BI project laterhttp://ip:port/ The project name in project name/decision should also be changed accordingly.

3. Copy tools.jar

Copy tools.jar under %JAVA_HOME%\jdk\lib to any location in %Tomcat_home%\lib or %Tomcat_home%\webapps\webroot\WEB-INF\lib .

Note: If this operation is not performed, the page displays an error message: HTTP Status 404 when accessing the BI project.

4. Configuration parameters

1) Configure BI to use memory parameters

FineBI has certain configuration requirements for the server, so it is necessary to configure memory parameters to ensure the stability of the server. For details, see: Modify FineBI Configuration Parameters

Note:  If the headless  parameter of section 5.1 in Modify FineBI configuration parameters is not configured, the super-control export Excel  will report an error: No export permission.

2) Configuring dump JVM parameters

Here, you need to configure the JVM parameter for automatically generating dump logs when the project is down. Configuring this parameter has no impact on the performance of the project, and is only used to generate dump logs when the server is down.

Go to the %Tomcat%\bin directory, edit the configuration file catalina.bat and add the following JVM parameters:

set JAVA_OPTS=%JAVA_OPTS% -server -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=D:\heapdump

Note: The path D:\heapdump  represents the path for generating the downtime file, and the file path can be modified as needed. After the modification is saved, you need to restart Tomcat for the configuration to take effect.

As shown below:

5. Start the Tomcat server

Enter the %Tomcat_HOME%\bin directory and double-click startup.bat to start the Tomcat server, as shown in the following figure:

6. Access BI Project

Enter the access address http://IP:port/webroot/decision in the browser, the example is http://localhost:8080/webroot /decision, open the BI project login page, that is, the deployment is successful, as shown in the following figure:

Ⅲ. Precautions

1. 0day vulnerability warning

If customers encounter0day vulnerability warningNotice, see: 0day Vulnerability Description

2. Poor performance

Problem description

After the project is successfully deployed in the Windows system, there is a lag problem and poor performance.

Cause Analysis

In Windows Server 2016 and later versions, Windows has updated the function of the console to support more functions similar to the cmd window. These new functions cause serious performance problems to the logs output to the console when Tomcat deployed in Server2016 is started in windowed mode, which eventually leads to BI performance freezes.

Solution

Option 1: Keep the startup window

1) After double-clicking startup.bat, on the pop-up Tomcat window, right-click the top white bar, select "Properties", check "Use Legacy Console", and click " Sure". As shown below:

2) Restart the Tomcat project.

Option 2: Disable the startup window

1) Go to the %Tomcat_HOME%\bin directory, find the setclasspath.bat file, and change set _RUNJAVA="%JRE_HOME%\bin\java.exe" to set _RUNJAVA="%JRE_HOME%\bin\javaw.exe". As shown below:

2) After saving, restart the Tomcat project.

Note 1: Use startup.bat to start Tomcat, the command window will flash, but the service has already started. To access the project, you need to wait for Tomcat to start.

Note 2: In this way, if you want to stop Tomcat, you can only go to the task manager to kill the java process.