Most platform configuration items are stored in the FINE_CONF_ENTITY table in FineDB.
Some configuration items cannot be configured on front-end pages or cannot be modified through FINE_CONF_ENTITY visualization configuration. In this case, you can modify these configuration items only by modifying the FINE_CONF_ENTITY table.
1. Do not modify FineDB files unless necessary, as modifying FineDB files may cause irreparable bugs.
2. Prioritize using the front-end configuration page or the FINE_CONF_ENTITY visualization configuration method to modify configuration items.
This document uses a simple example to introduce how to modify the table fields of FINE_CONF_ENTITY.
Steps:
1. Back up platform configurations.
2. Connect to the FineDB database to get the to-be-modified FINE_CONF_ENTITY table.
3. Query whether the configuration item exists in the FINE_CONF_ENTITY table, select different modification schemes based on the query results, and make corresponding modifications.
4. Restart the project.
Before you modify the table fields of FINE_CONF_ENTITY, it is recommended that you back up the platform configuration items manually or automatically. For details about backup methods, see Backup and Restoration.
For example, to take a manual backup, log in to the FineDataLink system as the admin, choose System Management > Intelligent O&M > Backup & Restoration > Platform Configuration, and select Manual Backup.
The default backup path is .../backup. The backup file is stored in the path FineDataLink installation directory/webapps/webroot/backup, as shown in the following figure.
Log in to FineDataLink as the admin and choose System Management > System Setting > General.
If the value of External Database is To Be Configured, you can view the FineDB database information by referring to the FineDB Database Introduction.
If the value of External Database is Configured, you can click it to view the information of the external FineDB database.
Create a data connection named FineDB. You can get the related configuration information in the "FineDB Database Information Obtaining" section, as shown in the following figure.
First, use a Data Synchronization node to query whether a field exists with ID = XX (select and modify the field as required; in this document, the example describes modifying the value of the field where ID = PluginFileValidateConfig.fileValidateOpen).
1. Create a scheduled task, as shown in the following figure.
2. Drag a Data Synchronization node to the design interface and click the node to configure it.
Select HSQL as the data source type, select FineDB as the data connection, and enter the following SQL statement:
1. Select ID and adjust SQL statements as required, as SQL statements may vary for different databases.
2. This section demonstrates the built-in HSQL-type FineDB database. If you have configured an external database, you can select the corresponding data source type and data connection as required.
select * from "PUBLIC"."FINE_CONF_ENTITY"where ID='PluginFileValidateConfig.fileValidateOpen'
Click Data Preview to check whether the required field exists, as shown in the following figure.
If the query result is empty:
1. This section applies to the scenario where the query result in the Query Field subsection is empty, that is, the required configuration item does not exist in the FINE_CONF_ENTITY table, as shown in the following figure.
2. By default, some configuration items do not have records in the FINE_CONF_ENTITY table of the project. It is necessary to manually add the relevant records and restart the project for these configurations to take effect.
Create a scheduled task, use a SQL Script node to add a field with ID set to PluginFileValidateConfig.fileValidateOpen and VALUE set to true, click Save, and click Run to execute the task, as shown in the following figure.
The SQL script is as follows:
INSERT INTO FINE_CONF_ENTITY (ID,VALUE)VALUES('PluginFileValidateConfig.fileValidateOpen','true')
If the query result is not empty:
Create a scheduled task, use a SQL Script node to modify the VALUE of the record to true, click Save, and click Run to execute the task, as shown in the following figure.
UPDATE FINE_CONF_ENTITY SET FINE_CONF_ENTITY.VALUE = 'true'WHERE ID='PluginFileValidateConfig.fileValidateOpen'
After the SQL script executes successfully, restart the project for the modifications to take effect.
If the system fails to achieve the expected results after you modify the field value, and you wish to restore the platform configuration, you can log in to the FineDataLink system to restore the backup file from the "Platform Configuration Backup" section of this document. For details, see Backup and Restoration.
If you are able to log in to the FineDataLink system normally before modifying the FINE_CONF_ENTITY table fields, but cannot log in after modification, you can follow the steps below to reset the platform configuration:
1. According to the backup path set in the "Platform Configuration Backup" section, locate the backup FineDB file, and replace the existing FineDB file with the backup file to restore the platform configuration.
Taking the manual backup as an example, in the path FineDataLink installation directory/webapps/webroot/backup/config/manual, locate the backup content with the folder name (backup time). Unzip the config.zip file to obtain the FineDB file and use it to replace the FineDB file in FineDataLink installation directory/webapps/webroot/WEB-INF/embed.
2. Restart the project.
滑鼠選中內容,快速回饋問題
滑鼠選中存在疑惑的內容,即可快速回饋問題,我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy