Minor Version Upgrade Instruction for V4.2.x​

FineDataLink has been continuously updated and iterated to meet customers' new needs and enhance the functionality of earlier versions.

To access new functions and fixes for issues in previous versions, you need to upgrade FineDataLink to the latest version.

Notes

Note:

You are advised to upgrade FineDataLink to the latest minor version of V4.2.

Obtaining JAR Packages

You can send an email to international@fanruan.com or click at https://help.fanruan.com/finedatalink-en/.

For more contact methods, see Technical Support Channel Introduction.

Baking up the Project

Before a project upgrade, you must back up the original project and then proceed with subsequent operations. This can avoid rollback inability caused by project file loss if the upgrade fails.

Log in to FineDataLink as the admin, choose System Management > Intelligent O&M > Backup and Restoration, and click Manual Backup on the Platform Configuration, FDL Task, JAR Package, and Plugin tab pages in sequence, as shown in the following figure.

If pipeline tasks are running and an external database is configured, manually back up the migrated FineDB database.

Uploading the Update Package

Note:

Review the "Notes" section of this document. In some scenarios, you need to upgrade FineDataLink to a transitional version before upgrading it to the target version.

1. Refer to the "Notes" section of this document. For projects of certain versions, you need to delete some JAR files before upgrading the project.

2. Refer to the steps in the "Uploading the Update Package" section to upload the latest JAR packages and update the project.

Note:

The procedure applies to projects in all environments.

1. Refer to the "Notes" section of this document. For projects of certain versions, you need to delete some JAR files before upgrading the project.

2. Extract the JAR packages obtained in the "Obtaining JAR Packages" section and place them in Tomcat installation directory/webapps/webroot/WEB-INF/lib . (Overwrite existing files if files with duplicate names exist.)

Confirming Normal Kafka Operation

If the project contains running pipeline tasks, you are advised to confirm Kafka is running properly before starting the project.

For details about Kafka operation check and startup operations, see Kafka Deployment - ZooKeeper Mode.

Restarting Tomcat

For details, see Stopping/Restarting/Starting a FineDataLink Project.

Verifying a Successful Upgrade

Log in to FineDataLink as the admin after upgrading and restarting the project, and choose System Management > Registration Management > Version Information.

You can check whether the current JAR version is the desired project version, as shown in the following figure.

Compatibility Instruction

If you upgrade a project with activated data service APIs to V4.2.6.2 or later versions, note that:

• After upgrades, calls of activated APIs remain unaffected, but modifications to APIs may alter the request JSON format. Remind API callers to make corresponding changes.

• The Content-Type header of the data service is changed from text/json to application/json. Before upgrades, confirm whether the previous calls were done through code and whether the code specifically parsed text/json. If targeted parsing was implemented, the request type must be adjusted. Otherwise, the call will fail.

If you have upgraded FineDataLink to V4.2.1.1 and created pipeline tasks, and need to roll back the upgrades, you must delete the TO_SYNC_TRAFFIC field from the FINE_DP_PIPELINE_EXECUTE table in the FineDB database after rollback, and then restart the FineDataLink project.

Assume that you have upgraded FineDataLink to V4.2.11.3 or later versions and need to roll back the upgrades. Since the PAUSE status of real-time pipeline tasks cannot be recognized by FineDataLink of older versions, you need to execute the following SQL statement in the FineDB database before rollback: 

UPDATE FDL_PIPE_TABLE_RECORD set STATUS = 'PRE_INIT' WHERE STATUS = 'PAUSE'