Driver Management

Version 

Application Scenario 

You may fail to connect to FineDataLink or the database due to the lack of the built-in database driver of the corresponding version.

Function Description 

You can use the Driver Management function to upload the corresponding driver JAR package. Driver Management supports hot swapping, which allows you to use the driver after uploading it without restarting the project.

Before using the Driver Management function, set the SystemConfig.driverUpload field in the fine_conf_entity table of the FineDB database that stores FDL information to true.

• If the parameter value is set to true, drivers can be uploaded through Driver Management.

• If the parameter value is set to false (default value), drivers cannot be uploaded through Driver Management. An error message will appear when you upload a driver, saying "The driver JAR package is not allowed to be uploaded. You can modify the value of SystemConfig. driverUpload to enable this function."

V 4.0.14 and Earlier Releases

Manual configuration is required for V4.0.14 and earlier releases.

1. Log in to FDL as the admin and choose System Management > Permission Management > General.

2. If FDL is configured with an external database, connect it to the external database. For details, see Data Source Creation and Management.

If FDL is not configured with an external database, connect it to the built-in database. For details, see HSQLDB Configuration.

Use the Data Synchronization node to query whether there is a SystemConfig.driverUpload field.

The SQL statement is as follows: 

select * from fine_conf_entitywhere id='SystemConfig.driverUpload'

Note: The statement may vary with the database. Adjust it as needed.

Use the SQL Script node to add a SystemConfig. driverUpload field with a value of true if the result is null and run the task.

Note: The statement may vary with the database. Adjust it as needed.

The SQL script is as follows:

INSERT INTO FINE_CONF_ENTITY (ID,VALUE) VALUES('SystemConfig.driverUpload','true')

• If the value of this field is false, modify it to true and run the task.

The SQL script is as follows:

UPDATE FINE_CONF_ENTITY SET FINE_CONF_ENTITY.VALUE = 'true' WHERE ID='SystemConfig.driverUpload'

• If the value of this field is true, no operation is needed.

3. Restart the project after a successful write operation. Log in to the system, and now you can upload the driver JAR package through Driver Management.

V 4.0.14 and Later Releases 

No operation is required for V4.0.14 and later releases as the function is enabled by default.

Log in to FDL and choose System Management > Data Connection > Driver Management, as shown in the following figure.

Uploading the Database Driver

1. Click New Driver and enter a name for differentiation from other drivers. For example, to upload a DM driver, name the driver DM Driver.

2. Click Upload File to upload the database driver package.

Note: You can download the database driver in the help document of corresponding databases or get it from the database administrator.

3. Select the uploaded driver from the drop-down list of Driver, and click Save, as shown in the following figure.

Note: 

1. If there are multiple JAR packages for a driver, and you are unsure which one to upload, ask the corresponding database administrator for help. 

2. The uploaded driver package is located at %FineDataLink_home%\webapps\webroot\WEB-INF\drivers.

If a driver is problematic, you can quickly modify the driver-loading method to ensure a fast connection. By default, Load and Upload Driver Preferentially via Current Method is selected.

• Load and Upload Driver Preferentially via Current Method refers to loading the JAR file in WEB-INF/drivers/hive first. If no such file exists, it will load the JAR file in WEB-INF/lib.

• Load and Upload Driver Only via Current Method refers to only loading the JAR file in WEB-INF/drivers/hive.

Using Uploaded Database Driver 

Click New Data Connection on the Data Connection Management page to create a new data connection. For example, to create a DM data connection, see DM Data Source Configuration.

Deleting a Driver

To delete an existing database driver, go to the driver management page and click the  icon, as shown in the following figure.