Overview
Version
FineBI Version | Functional Change |
6.0 | / |
Functions
The admin logs into FineBI, clicks Manage > System, and can see General Parameters, WebSocket Setting, BI Parameter, and Spider Parameter on the General tab.
This article mainly introduces General Parameter and WebSocket Setting.
For details about BI Parameter and Spider Parameter, see BI/Spider Parameter.
General Parameters
Note: Some general parameters can only be used in FineReport. You need to set them as needed.
Function | Project Corresponding to Parameters | Explanation |
Servlet Path Name | FineReport | It is not recommended to modify it, because modification will affect the way the URL is written when you access FineReport templates. Default to decision. |
Week Start from | FineBI | You can select Monday/Sunday in Week Start from. Save and restart the system to take effect. When you set the week to start from Monday, the system will consider the week to range from Monday to Sunday. When you set the week to start from Sunday, the system will consider the week to range from Sunday to Saturday. This setting affects date formulas: Supported formulas: WEEK() and WEEKDATE() Unaffected formulas: WEEKDAY(), which returns the day of the week. DATEINWEEK(), which defaults the start day of a week to Monday. |
URL Management Center | FineBI | The switch of cloud center connection Various links in FineBI are managed by the cloud center, so it is recommended to turn on for later use of related cloud-based operation and maintenance functions.
|
Gzip Compression | FineReport | Enabling Gzip Compression can reduce storage space. When the system transfers files through the network, the transfer time can be reduced, which can speed up FineBI access speed. It is recommended to turn it on. |
Cryptographic Algorithm | FineBI | Admins can switch between default encryption and SM encryption. After you switch encryption methods, transmission, storage, user passwords, and so on are all encrypted by SM algorithm. |
External Database | FineBI | After you configure the external database for the report system, the stability of the report system can be ensured in cluster environments or situations with large amounts of data. |
Note:
1. After you disable URL Management Center, the server will no longer actively request the URL management center and will not output relevant logs for the failure to connect to the URL management center.
2. After you disable URL Management Center, some functions will not be available. The functions that cannot be used are shown in the table below:
Module | Function | Description |
Cloud center | Get the address of website center. | Website management center itself |
Plugin engine | Get update information. | Information of plugin mall version |
Download plugin. | Online plugin installation and online plugin update | |
Platform and plugin store information | Get plugin store information. | |
Local printing | Get the address of website center. | Download online for local printing. |
BBS authentication | FineReport passport login | Designer login |
Platform plugin store | ||
SMS login | ||
Cloud operations login | ||
FineReport market | Open SMS platform | / |
Send a text message. | / | |
Decision platform | Get current client-end IP and city. | The function Last login information prompt setting Note: The Last login information prompt setting function cannot display the latest information. |
WebSocket Setting
To reduce the difficulty of WebSocket configuration, FineBI 6.0 supports container WebSocket solution.
This solution uses the WebSocket of Web container for connection, with the http port. You do not need to open ports, nor do you need any manual configuration.
When FineBI supports the container WebSocket solution, the front-end access will first use the new solution. If it fails, it will use the Socket.IO solution for retry.
Therefore, WebSocket settings are not displayed in General by default. It will only be displayed when the container Websocket solution fails to be called.
WebSocket Request Port
After ticking, you can configure the WebSocket request port. It is not ticked by default. However, it will be automatically enabled under the cluster.
After you tick, the port setting text box will be displayed. You can fill in the requested port of WebSocket, which is 48889 by default.
Note: FineBI WebSocket port defaults to 48888 and 48889, with port number 48888 taking priority over 48889.
Note: There is a format restriction on the port filling. If the port format is filled incorrectly, an error message will be prompted when you click Save: Incorrect Port Format.
WebSocket Request Path
When the default value is /socket.io, the default request path is http://ip:port/socket.io.
You can specify a middle path such as /webroot/decision/socket.io. Then the request path is http://ip:port/webroot/decision/socket.io.
HTTPS Settings
Note: If HTTPS is already configured at Nginx, there is no need to configure HTTPS information on the platform.
Server protocol: Select the protocol type, with plain for http and ssl for https.
The default value is plain.
SSL key path: the absolute path storing the key and public key, corresponding to field values of keystoreFile in the file server.xml under the path %TOMCAT_HOME%\conf.
SSL key password: the key used when you apply, corresponding to field values of keystorePass in the file server.xml under the path %TOMCAT_HOME%\conf.
SSL type: Select the format. If it is a PFX certificate, change it to PKCS12. The default is JKS.
Note: After you have configured the WebSocket request port, a message will be prompted to restart the server when you save the configuration.
Other Settings
Check Font, Report Inspection, Parameter Setting, Dashboard calculation, Template Assistant, and Fine Report Parameters are all special functions of FineReport templates. They do not take effect on FineBI templates.
