Upgrades from V4.0/V4.1 to V4.2

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.

V4.0-to-V4.2 Upgrade

For upgrades from versions between V4.0.20 and V4.0.30 to V4.2.x, follow the steps in the "Upgrading FineDataLink from a Version Between V4.0.20 and V4.0.30 to V4.2.x" section of this document. 

Note:

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

V4.1-to-V4.2 Upgrade

Upgrading FineDataLink from V4.1.7.3

You are advised to upgrade FineDataLink to V4.2.2.3 or later versions.

If the target version is between V4.1.8.1 (exclusive) and V4.2.0.2 (inclusive), you must first upgrade FineDataLink to V4.1.8.1 as an intermediate step.

Upgrading FineDataLink from V4.1.x to V4.2.x

The steps are mostly the same as those in the "Upgrading FineDataLink from a Version Between V4.0.20 and V4.0.30 to V4.2.x" section of this document. Differences are explained in the following table.

Step Sequence	Step Description	V4.1.x-to-V4.2.x Upgrade
1	Obtain the JAR package.	See the "Obtaining the Latest JAR Package" section.
2	Pause pipeline tasks.	If your project version is V4.1.6.2 or later before the upgrade, you do not need to pause pipeline tasks.
		If your project version is earlier than V4.1.6.2, you must pause pipeline tasks by following the "Pausing Pipeline Tasks" section of this document.
3	Prepare the backups.	For details, see the "Backing up the Project", "Closing Tomcat", and "Backing up the Server" sections of this document.
4	Replace existing JAR files with the latest JAR files.	Navigate to Tomcat installation directory/webapps/webroot/WEB-INF/lib. 1. Delete all files suffixed with 4.1.jar. 2. Delete the fine-bi-engine-third-*.jar file if it exists. 3. Delete the fdl-bi-extension-4.1.jar file if it exists. 4. Upload the latest JAR files to this path. For specific steps, see the "Replacing Existing JAR Files with the Latest JAR Files" section of this document. Modify the provided Linux commands as needed for the specific environment. Note: To upgrade FineDataLink from V4.1.x to V4.2.x or later versions (the latest V4.2.x recommended): 1. First, upgrade FineDataLink to V4.2.2.3. After the upgrade, you are advised to start the project following the "Starting the Project" section of this document and verify whether the upgrade is successful. You will need to re-register the project and re-upload the license file. 2. Then, upgrade FineDataLink to V4.2.4.3. After the upgrade, you are advised to follow the "Starting the Project" section of this document to start the project and verify whether the upgrade is successful. Since the fdl-cron JAR file has been renamed fdl-offline, you must manually delete fdl-cron when replacing JAR files. 3. Finally, upgrade FineDataLink to the target version. If the target version is V4.2.6.2 or a later one, you must first delete all JAR files prefixed with fine- and fdl- in Tomcat installation directory/webapps/webroot/WEB-INF/lib, and then place the new JAR files.
5	Complete the post-upgrade steps.	1. Start the project following the "Starting the Project" section of this document. 2. Re-register the project and re-upload the license file since the previous license file becomes invalid after the upgrade to 4.2.x. 3. Rerun the previously paused pipeline tasks (if any).

Obtaining the Latest JAR Package

Note:

To obtain the JAR package for upgrade, contact your designated Customer Success representative in the service group.

Pausing Pipeline Tasks

Log in to FineDataLink as the admin, choose Data Pipeline, and pause running pipeline tasks, as shown in the following figure.

Backing up the Project

Performing Backup on the Platform

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.

Backing up FineDB

Since data pipelines cannot be backed up through the Backup and Restoration function on the platform, you need to manually back up FineDB  (the configured external database).

You can check the external database configuration by referring to the steps in the following figure.

Closing Tomcat

In this example, the project is deployed in /home/wendy/FDL/tomcat-linux.

1. Execute the following command to check the project processes. You will find that the current server is running, with process IDs 14429 and 13878, as shown in the following figure.

ps -ef|grep tomcat-linux

2. Kill the project process, and check whether there are unclosed project processes. All processes related to this project need to be killed.

kill 14429
kill 13878

After using the command above, you can wait for half a minute, and then use the command ps -ef|grep tomcat-linux again to check if the process has been closed.

Note:

1. You are not advised to use the kill -9 pid command, as it may cause abnormalities in pipeline tasks.

2. If the process remains unresponsive to the kill <pid> command for an extended period, contact technical support personnel for troubleshooting.

Backing up the Server

You are advised to back up the entire project for safety.

Execute the following command in Tomcat installation directory/ to back up the project.

tar -zcvf tomcat_Bak20240102.tar.gz tomcat

If the webroot directory is too large, you can delete some execution record files in FineDataLink installation directory/webroot/WEB-INF/dpworks/record before backup, as shown in the following figure.

Additionally, you can delete older files in FineDataLink/webapps/webroot/backup and FineDataLink/webapps/webroot/logs, as shown in the following figure.

Replacing Existing JAR Files with the Latest JAR Files

Note:

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

1. First, upgrade FineDataLink to V4.2.2.3. After the upgrade, you are advised to start the project following the "Starting the Project" section of this document and verify whether the upgrade is successful. You will need to re-register the project and re-upload the license file.

2. Then, upgrade FineDataLink to V4.2.4.3. After the upgrade, you are advised to follow the "Starting the Project" section of this document to start the project and verify whether the upgrade is successful. Since the fdl-cron JAR file has been renamed fdl-offline, you must manually delete fdl-cron when replacing JAR files.

3. Finally, upgrade FineDataLink to the target version. If the target version is V4.2.6.2 or a later one, you must first delete all JAR files starting with fine- and fdl- in Tomcat installation directory/webapps/webroot/WEB-INF/lib before placing the new JAR files.

Upgrading FineDataLink to V4.1.13.2

1. Delete all files suffixed with 4.0.jar in Tomcat installation directory/webapps/webroot/WEB-INF/lib. Delete fine-bi-engine-third-6.0.jar if it exists in this path.

2. Extract the JAR package corresponding to  V4.1.13.2 obtained in the "Obtaining the Latest JAR Package" section and place JAR files in Tomcat installation directory/webapps/webroot/WEB-INF/lib. (Overwrite existing files if files with duplicate names exist.)

3. Start the project following the "Starting the Project" section of this document to verify if the upgrade is successful. Note that the previous license will become invalid.

Upgrading FineDataLink to V4.2.2.3

Upgrade FineDataLink toV4.2.2.3.

Navigate to Tomcat installation directory/webapps/webroot/WEB-INF/lib, delete all files suffixed with 4.1.jar and the fine-bi-engine-third-*.jar file, and then upload the latest JAR files.

1. After receiving the latest JAR package, upload it to the FineDataLink server and extract it. In this example, the extracted folder is named FDL_jar_4.2.0.3. (Input the actual folder name in the command.) Upload the extracted files to FineDataLink installation directory/webapps/webroot/WEB-INF/lib.

The procedures are as follows:

Navigate to Tomcat installation directory/webapps/webroot/WEB-INF/lib and execute the command:

cp -r FDL_jar_4.2.0.3/*  Tomcat/webapps/webroot/WEB-INF/lib

Press y and then Enter when prompted.

2. Delete JAR files suffixed with 4.1.jar.

Navigate to Tomcat installation directory/webapps/webroot/WEB-INF/lib and execute the command:

rm *-4.1.jar

Press y and then Enter when prompted.

3. Delete fine-bi-engine-third-*.jar.

Navigate to Tomcat installation directory/webapps/webroot/WEB-INF/lib and execute the command:

rm fine-bi-engine-third-*.jar

Press y and then Enter when prompted.

4. Start the project following the "Starting the Project" section of this document and check if the upgrade is successful (recommended). Re-registration is required.

Upgrading FineDataLink to V4.2.4.3

• Extract the JAR package corresponding to  V4.2.4.3 obtained in the "Obtaining the Latest JAR Package" section and place JAR files in Tomcat installation directory/webapps/webroot/WEB-INF/lib. (Overwrite existing files if files with duplicate names exist.)

• Since the fdl-cron JAR file has been renamed fdl-offline, you must manually delete fdl-cron when replacing JAR files.

• You are advised to start the project following the "Starting the Project" section of this document and check if the upgrade is successful.

Upgrading FineDataLink to the Target Version

• To upgrade FineDataLink to a version earlier than V4.2.6.2:

Extract the JAR package corresponding to the target version and place JAR files in Tomcat installation directory/webapps/webroot/WEB-INF/lib. (Overwrite existing files if files with duplicate names exist.)

• To upgrade FineDataLink to V4.2.6.2 and a later version:

Delete all JAR files starting with fine- and fdl- in Tomcat installation directory/webapps/webroot/WEB-INF/libfirst, and then place the new JAR files.

Starting the Project

1. Check if Kafka is running properly.

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

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

2. Navigate to Tomcat installation directory/bin and execute ./startup.sh to start the project. For details, see Stopping/Restarting/Starting a FineDataLink Project.

3. Log in to the FineDataLink project, choose System Management > Registration Management, and check whether the data platform version is the specified version, as shown in the following figure.

Re-registration

1. Log in to the FineDataLink project, choose System Management > Registration Management, and re-upload the license file in Registration Information. For details about the license application procedure, see Local Machine Info Authentication.

2. Start the previously paused pipeline tasks.

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.

For details, see Instructions for Rollback from V4.2.x.