FineDataLink Transitional Upgrade Instruction

Version

Application Scenario

There are two types of FineDataLink application images in FineOps.

• fdl: It applies to FineDataLink of V4.2.4.2 and earlier versions.

• fdl42: It applies to FineDataLink of V4.2.10.3 and later versions, where an fdl42 image of V4.2.4.3 is additionally provided, because the FineDataLink upgrade must pass through this version.)

Standard component upgrades for a project only require higher versions of the same images.

However, for a FineOps-deployed FineDataLink project, you must use the Upgrade to Transitional FineDataLink Version function to switch from the fdl image to the fdl42 image to facilitate upgrades.

This document describes how to upgrade FineDataLink from V4.2.4.2 or earlier versions to V4.2.10.3 or later versions. (The version here refers to the fdl image version.)

It does not provide guidance for any other upgrade paths, such as upgrading the image to an intermediate version or from an intermediate version to a higher one. For assistance with those scenarios, contact your designated customer success representative in the FineDataLink service group.

1. Log in to FineOps as the admin, click a FineDataLink project, and choose Maintenance > Component Management.

2. Locate the FineDataLink component.

• Ensure the current version is V4.2.4.2 or earlier.

• Ensure the container name is fdl.

• Ensure the target version is V4.2.10.3 or later.

Overview: Upgrade the fdl image of V4.2.4.2 or earlier versions to a transitional fdl42 image of V4.2.4.3, and then upgrade the image to V4.2.10.3 or later versions in Component Management.

Upgrading FineOps

Upgrade FineOps to V2.26.0 or later versions.

Intranet users must upgrade FineOps using the full FineKey deployment package to obtain the latest fdl42 image in the local image repository.

For details, see Extranet-Based FineOps Upgrade or Intranet-Based FineOps Upgrade.

Manually Uploading the fdl42 Image of V4.2.4.3

External network users: No manual upload is required because the image can be pulled automatically.

Intranet users: Contact the designated customer success representative in the FineDataLink service group to obtain the fdl42 image of V4.2.4.3. Then, push it to the FineOps image repository. For details, see Pushing a Single Image to the Repository.

Baking up the Project

You are advised to back up the whole project before updating components to prevent uncontrollable accidents during the update.

If no backup from the past 24 hours is detected, the update cannot proceed.

Log in to FineOps as the admin, click the required O&M project, and choose Maintenance > Backup Management.

You are advised to tick Image Backup and click Start Backup to back up the whole project.

Note:

Some files are not backed up (such as files in /assets/temp_attach). Back up these files manually.

For details about the backup content, see Project Backup.

Upgrading FineDataLink to Transitional V4.2.4.3

1. Log in to FineOps as the admin and choose Maintenance Center > Upgrade to Key FineDataLink Version > Upgrade to Transitional FineDataLink Version.

2. Select the target FineDataLink project that is currently of V4.2.4.2 or earlier versions.

3. Check the current version, which is displayed automatically.

• The current version of the FineDataLink project must be V4.2.4.2 or earlier.

4. Select the update version.

• Intranet users: Choose the fdl42 image of V4.2.4.3 from the local image repository.

• External network users: Choose the fdl42 image of V4.2.4.3 from the FanRuan cloud image repository.

5. Click Start Upgrade.

FineOps will automatically upgrade the image of the selected project from fdl of V4.2.4.2 or earlier versions to fdl42 of V4.2.4.3 in the repository.

Upgrading the Project to V4.2.10.3 or Later Versions in Component Management

After successfully upgrading the image to V4.2.4.3, you can continue the normal upgrade of the FineDataLink project to V4.2.10.3 or later versions in Component Management.

For details, see Extranet-Based O&M Project Upgrade or Intranet-Based O&M Project Upgrade.

The project mounting path includes the container name. Since the upgrade changes the container name from fdl to fdl42, the project mounting path will change accordingly from Mounting path/fanruanxxx/fdl/xxx to Mounting path/fanruanxxx/fdl42/xxx.

Therefore, if any data transformation or processing operators are configured with the project mounting path, you must update these paths manually after the successful upgrade.