FineBI Version
New Function
6.0
/
Application Scenarios
When you deploy the server, the deployment may fail due to multiple reasons. At this time, a guiding page will be provided to help you detect and fix the problem.
When the server deployment fails, the wizard will guide you to detect and fix problems in time for a successful deployment.
The deployment procedure is as follows:
Container
Instruction
Tomcat
JDK version: JDK 1.8, and the minor version must be newer than JDK 8u102. For details, see FineBI Deployment on Tomcat.
WebLogic
JDK version: JDK 1.8, and the minor version must be newer than JDK8u102. For details, see FineBI Deployment on Weblogic
WildFly
For details, see FineBI Deployment on WildFly 9 to WildFly 18, FineBI Deployment on WildFly 8.
WebSphere
For details, see FineBI Deployment on WebSphere on Linux.
Resin
For details, see FineBI Deployment on Resin
Docker
For details, see FineBI Deployment on Docker.
The error message is displayed as follows:
For details, see Deployment Environment Exception.
1. Built-In Database Connection Failture
WhenFineBI fails to be connected to the built-in database, the error message is shown like this:
2. External Database Connection Failture
WhenFineBI fails to be connected to the external database, the error message is shown like this:
After modifying the configuration of the external database, click Retest. If the connection is successful, you will directly access the new database. If the connected database has no data, it will prompt that the target database is an unusable new database.
When the WebSocket port conflicts with other ports, the error message is shown like this:
If an external database exception is detected, an error message will be prompted: Check whether the database user has the permission to create and modify tables. Or check the database logs to rectify the fault.
To address this issue, we need to check whether the user has the permission to create and modify tables in the database. If the user does not have the permission, grant the permission to the user. If the user has, check the database logs for other problems.
Note: External database user without database permissions will be prompted during the upgrade to terminate the upgrade.
Take Tomcat container as an example. Copy webroot folder under %BI_HOME%/webapps/webroot to %TOMCAT_HOME%/webapps and start Tomcat.
If the project fails to start, visit http://localhost:8080/webroot/decision, and you will automatically be directed to the server deployment wizard page http://localhost:8080/webroot/decision/v10/deployment/recommendation.
Following the Prompt
Copy the tools.jar file under %JAVA_HOME%\jdk\lib to %Tomcat_home%\webapps\webroot\WEB-INF\lib.
Restart Tomcat and visit http://localhost:8080/webroot/decision. If you can be directed to the login page, the deployment is successful.
滑鼠選中內容,快速回饋問題
滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy