Extranet-Based O&M Project Upgrade

Version

Application Scenario

FanRuan products (FineReport/FineBI/FineDataLink) are continually updated to meet new customer requirements and improve on some features of previous releases.

After deploying projects via the O&M platform as the admin, you need to update and upgrade the projects regularly, but you may encounter some problems with the traditional upgrade approach.

1. The minor updates of FineReport (intranet)/FineBI require manually replacing JAR packages, which is challenging.

2. You may need to upgrade the project to a specified version rather than the latest version due to compatibility issues. It requires manually replacing JAR packages, which is challenging.

3. Upgrading FineReport (extranet) requires manually restarting the project or all cluster nodes, which is troublesome.

4. A failed upgrade cannot be reversed automatically, causing risks.

Function Description

FineOps provides a FanRuan products-oriented (FineReport/FineBI/FineDataLink) update function.

1. It allows for updating the component to the latest/specified version.

2. It maintains the security of intranet updates by pushing the image.

3. Any failed updates can be automatically rolled back.

Validity

• Extranet definition: If the FineOps image repository can access an extranet, you can upgrade projects using the extranet.

• Upgrade projects to those of the latest versions: FineOps obtains the version numbers of the latest images by default, allowing you to update specific components with the latest images it obtains online.

• Upgrade projects to those of specified versions: You can contact technical support personnel to obtain the specified version numbers of images and update specific components with images of specified versions FineOps obtains online.

Note:

For details about updating projects with intranet, see Intranet-Based O&M Project Upgrade.

Prerequisite

FineOps Deployment

Updating FanRuan projects via FineOps applies to projects deployed via FineOps only. Operations described in this document do not apply to projects not deployed via FineOps.

Ensuring Access of the Image Repository Address to FanRuan Cloud Repository

Updating the project components online via FineOps requires component image packages of new versions for replacement.

Therefore, you must ensure the server hosting the image repository has external network access to FanRuan cloud repository to enable image pulls from the cloud.

For details, see Ensuring Access to FanRuan Cloud Repository.

Project Version Confirmation

1. Log in to FineOps as the admin, select an O&M project, and choose Maintenance > Component Management. Locate the component to be updated and check if an update is available.

There is no available update if the message "Already the latest version." is displayed.

Notes

1. When updating the O&M project components, you can update multiple components in batches or update a component individually. But you cannot update partial containers of a component.

• This setting ensures version consistency of containers of the same component.

• You are advised to update all project components to those of the latest versions to improve project security. ·

2. Some components have an update dependency. For example, updating the FineBI - Application Node component (the master component) will trigger an update of the Engine - Calculation Node component (the slave component).

• For components with an update dependency, the Update button of the slave component is grayed out, and you can only update the master component.

• When you update a master component, a prompt will appear, saying "If an update is triggered, Component name will stop and be updated to the corresponding version."

Project Backup

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

You cannot perform updates if no backup from the past 24 hours is detected. A prompt will appear, saying "Failed to update the component. Ensure a backup in the past 24 hours before updates. Try again after backing it up."

Log in to FineOps as the admin, select a project, and choose Maintenance > Backup Management.

Tick Image Backup (recommended). Click Start Backup to back up the whole project.

Version Update

You can update multiple components in batches or update a specific component individually.

You are advised to update all project components to those of the latest versions to improve project security.

Single Component Update

1. Log in to FineOps as the admin and select the required O&M project. Choose Maintenance > Component Management.

2. Find the component to be updated and click Update.

Note:

For components with an update dependency, the Update button of the slave component is grayed out, and you can only update the master component.

When you update a master component, a prompt will appear, saying "If an update is triggered, Component name will stop and be updated to the corresponding version."

3. Choose Start Update. You do not need to enter the version number. The component will be updated to that of the latest version.

• Components will be restarted in an update, which may affect the normal operation of the project. Do not perform this operation during use.

• If there is no backup within 24 hours, the update will be terminated. You can update components after backing up the project.

The Component Management page is refreshed automatically after the update is completed, and a prompt is displayed, saying "Updated successfully." The message "Already the latest version." is displayed at Lastest Version of the component.

Batch Component Update

1. Log in to FineOps as the admin and select the required O&M project. Choose Maintenance > Component Management and click Batch Update.

2. Choose Start Update. You do not need to enter the version number. All components will be updated to those of the latest versions.

• When an update is triggered, all components will stop running and be updated to those of the latest versions, which may affect the normal operation of the project. Do not perform this operation during use.

• If there is no backup within 24 hours, the update will be terminated. You can update the project after backing up the project.

Note:

This solution does not apply to rollbacks to specified versions.

Image Version Number Acquisition

Paid users contact the technical support personnel and provide the required product and the minor version number or the approximate date of the JAR package.

Technical support personnel will inform you of the specific image version number.

For details about how to contact technical support personnel, see Technical Support Channel Introduction.

Prerequisites

FineOps Deployment

Updating FanRuan projects via FineOps applies to projects deployed via FineOps only. Operations described in this document do not apply to projects not deployed via FineOps.

Image Repository Configuration

Updating the project components via FineOps requires component image packages of new versions for replacement. Therefore, you need to pull images from the cloud.

For details, see Ensuring Access to FanRuan Cloud Repository.

Notes

1. When updating the O&M project components, you can update multiple components in batches or update a component individually. But you cannot update partial containers of a component.

• This setting ensures version consistency of containers of the same component.

• You are advised to update all project components to those of the latest versions to improve project security.

2. Some components have an update dependency. For example, updating the FineBI - Application Node component (the master component) will trigger an update of the Engine - Calculation Node component (the slave component).

• For components with an update dependency, the Update button of the slave component is grayed out, and you can only update the master component.

• When you update a master component, a prompt will appear, saying "If an update is triggered, Component name will stop and be updated to the corresponding version."

Project Backup

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

You cannot perform updates if no backup from the past 24 hours is detected. A prompt will appear, saying "Failed to update the component. Ensure a backup in the past 24 hours before updates. Try again after backing it up."

Log in to FineOps as the admin, select a project, and choose Maintenance > Backup Management.

Tick Image Backup (recommended). Click Start Backup to back up the whole project.

Version Update

1. Log in to FineOps as the admin, select the required project, and choose Maintenance > Component Management.

2. Find the component to be updated and click Update.

Note:

For components with an update dependency, the Update button of the slave component is grayed out, and you can only update the master component.

When you update a master component, a prompt will appear, saying "If an update is triggered, Component name will stop and be updated to the corresponding version."

3. Enter the specified image version number in Update Version manually and choose Start Update > OK to perform the update.

• Components will be restarted in an update, which may affect the normal operation of the project. Do not perform this operation during use.

• If there is no backup within 24 hours, the update will be terminated. You can update the project after the backup.

The Component Management page is refreshed automatically after the update is completed, and a prompt is displayed, saying "Updated successfully." The message "Already the latest version." is displayed at Lastest Version of the component.