General Settings

1. Version 

2. Function introduction

Enter the data decision system as an administrator, click "Manage> System", and under the "General" tab page, you can see general parameters, WebSocket settings, BI parameters, and Spider parameters. As shown below:

This article mainly introduces general parameters and WebSocket settings. For the introduction of BI parameters and Spider parameters, please refer to: [Extract data]BI/Spider parameters

Note: Among the following general parameters, only "Connect to URL Management Center", "External Database", "Start of Week" and FineBI is related, other general parameters are used in FineReport , please set according to your own needs.

Note 1: The FineBI project whose JAR package time is after 2019-01-15 supports the "Week Starts at" setting.

Note 2: For FineBI projects whose JAR package time is after 2020-08-04, after the user closes the "Connect URL Management Center" button, the server will no longer actively request the URL management center, and will not output the URL management center connection failure in the log related logs.

Note 3: After closing the "Connect URL Management Center" button, some functions will be unavailable. The unavailable functions are shown in the table below:

The WebSocket port provides interface configuration to improve ease of use. The setting items are as shown below:

Note: The FineBI project whose JAR package time is after 2019-12-20 supports setting WebSocket in the data decision system. Users can also configure WebSocket through other methods. For details, please refer to: Configuring WebSocket in HTTPS Environment under 10.0

1. WebSocket request port

After checking , you can configure the WebSocket request port, and it is not checked by default. But it will be automatically enabled under the cluster.

port setting text box will be displayed below , fill in the request port of WebSocket here, the default is 48889. As shown below:

Note 1: The WebSocket port of FineBI is [48888, 48889] by default, and the port number is 48888 first and 48889 second.

Note 2: If the Websocket port is occupied/unusable, please refer to the documentation for troubleshooting and solution: Websocket port is occupied/unusable

Note: There are format restrictions for filling in the port. If the port format is wrong, when you click Save, an error message will be prompted: The port format is incorrect.

2. WebSocket request path

default value is /socket.io , and the default request path is http://ip:port/socket.io .

An intermediate path such as /webroot/decision/socket.io can be specified , and the request path is http://ip:port/webroot/decision/socket.io .

3. HTTPS settings

Note: If you have configured HTTPS at Nginx, you do not need to configure the platform's HTTPS information.

·       Server Protocol: Select the protocol type, select plain for http, and select ssl for https . For details, see: Configuring SSL Certificates for HTTPS Access . The default is plain.

·       SSL key path: the storage path of the key and public key , using an absolute path, corresponding to the value of the keystoreFile field in %TOMCAT_HOME%\conf\server.xml .

·       SSL key password: the key used in the application , corresponding to the value of the keystorePass field in %TOMCAT_HOME%\conf\server.xml .

·       SSL certificate type: select the certificate format, if it is a pfx certificate, change it to PKCS12, the default is JKS.

Note: After configuring the WebSocket request port, you will be prompted to restart the server when saving the configuration