Windows

NiFi Version Upgrade on Bridge Client from 1.28.x to 2.6.x on Windows

This article provides a step-by-step procedure to upgrade Apache NiFi from versions 1.28.x or 1.25.0 to 2.6 for both:

• Apache NiFi Server

• OvalEdge Bridge Client on Windows

The document also includes the Java upgrade procedure from JDK 17 to JDK 21, along with:

• prerequisite validation

• backup requirements

• configuration updates

• rollback considerations

• validation procedures

• post-upgrade verification steps

This guide is intended for administrators, DevOps engineers, implementation teams, and support engineers responsible for maintaining the OvalEdge Bridge environment.

Upgrade Overview

Perform the upgrade in the following sequence:

1. Verify prerequisites and current environment status.

2. Validate Bridge connectivity from the OvalEdge UI.

3. Back up the existing NiFi configuration and Bridge artifacts.

4. Stop existing NiFi services.

5. Upgrade Java from JDK 17 to JDK 21.

6. Upgrade the Apache NiFi Server from 1.28.x to 2.6.

7. Upgrade the Apache NiFi Bridge Client from 1.28.x to 2.6.

8. Update NiFi configuration files.

9. Restart NiFi services.

10. Validate Bridge connectivity and connector execution.

11. Verify logs, metadata flow, and processor communication.

Supported Upgrade Paths

Component	Existing Version	Target Version
Apache NiFi Server	1.25.0 / 1.28.x	2.6
Apache NiFi Client	1.25.0 / 1.28.x	2.6
Java	JDK 17	JDK 21

Prerequisites

System Requirements

Ensure the following prerequisites are met before starting the upgrade.

Component	Supported Version
Windows Server	2019 / 2022
Windows Client	Windows 10 / 11
Java	JDK 21
Apache NiFi	2.6

Minimum Hardware Requirements

Resource	Minimum
CPU	4 vCPUs
Memory	8 GB RAM
Disk Space	20 GB Free
Network	Stable connectivity to OvalEdge Application

Recommended Hardware Requirements

Resource	Recommended
CPU	8 vCPUs
Memory	16 GB RAM
Disk Space	50 GB Free

Network Requirements

Ensure the following connectivity is available:

• Bridge Client → OvalEdge Application URL

• Bridge Client → Database Sources

• Bridge Client → Cloud Services (if applicable)

If a corporate proxy is used:

• Configure proxy settings before installation.

• Verify access to OvalEdge application endpoints.

• Validate outbound HTTPS communication.

Mandatory

• Administrator access on the server and the Bridge Client VM

• Access to the OvalEdge Application UI

• Access to ECS Task Definitions

• Access to EFS mount configurations

• Sufficient disk space for backups

• Existing Bridge installer ZIP package

• Internet access or offline installation binaries

• If internet access is unavailable, obtain the following installation packages before beginning the upgrade:

  • OpenLogic JDK 21 Installer

  • Bridge Client Installer JAR

  • Required Bridge Artifacts

  • SAP JCo Libraries (if applicable)

Recommended

• Perform the upgrade during a maintenance window.

• Notify users about temporary connector interruptions.

• Export screenshots of the existing NiFi flow configuration before the upgrade.

Pre-Upgrade Validation

Validate Bridge Status from the OvalEdge UI

1. Log in to the OvalEdge application.

2. Navigate to the Bridge monitoring section.

3. Verify the Bridge status displays:

   1. Connected

   2. Running

Expected Result

• The Bridge status appears healthy before the upgrade begins.

Failure Impact

• If the Bridge is disconnected before the upgrade, troubleshooting becomes difficult afterward.

Apache NiFi Server Upgrade (1.28.x → 2.6)

Stop the Existing NiFi ECS Service

1. Navigation Path:

   AWS Console
   → Amazon ECS
   → Clusters
   → <Cluster Name>
   → Services
   → <NiFi Service Name>

   Locate the active NiFi service before stopping the task.

2. Stop the currently running NiFi ECS service before updating the task definition.

   

Validation

Verify the ECS task status changes to:

• Stopped

Warning

• Do not proceed with the upgrade while the existing NiFi service is still running.

Update the ECS Task Definition

1. Open the ECS Task Definition used by the NiFi service.

2. Replace the existing NiFi Docker image with the NiFi 2.6 image.

3. Save the updated task definition revision. Example:

   Existing Image:
   apache/nifi:1.28.1
   Updated Image:
   apache/nifi:2.6

Validation

Verify that the new ECS task revision was created successfully.

Validate EFS Mount Paths

1. Open the ECS Task Definition.

2. Verify the EFS container mount paths are correctly mapped.

3. Confirm all required NiFi configuration directories are accessible.

Validate the Following Mounts

1. nificonf

2. nifilib

3. certificates directory

4. flow configuration directory

Failure Impact

Incorrect EFS mappings may cause:

1. missing flows

2. missing certificates

3. startup failures

Back Up the Existing nificonf Directory

Mandatory

• Take a complete backup of the existing nificonf directory before modifying any configuration files. Sample Reference Screenshot:

  

  Example Backup Command

  cp -r nificonf nificonf_backup_$(date +%Y%m%d)

Expected Result

A full backup of the existing NiFi configuration is available for rollback.

Retain Required Files in nificonf

1. Inside the existing nificonf directory, retain only the following files:

   keystore.jks
   nifi-cert.pem
   nifi.properties
   truststore.jks
   users.xml

   Do not remove certificate or truststore files required for secure communication.

Update the nifi.properties File

1. Open the following file:

   nificonf/nifi.properties

2. Locate the following property:

   nifi.flow.configuration.file=./conf/flow.xml.gz

3. Update the property to:

   nifi.flow.configuration.file=./conf/flow.json.gz

   Sample Reference Screenshot:

   
4. Save the file.

Purpose

• NiFi 2.6 uses flow.json.gz instead of flow.xml.gz.

Validation

• Verify the updated property is saved correctly before restarting the service.

Clean the nifilib Directory

1. Navigate to the nifilib directory.

2. Remove all .nar and .jar files except:

   sapjco.jar

Warning

• Do not delete the SAP JCo library required for SAP connectors.

Start the Updated NiFi ECS Service

1. Deploy the updated ECS task revision.

2. Start the NiFi ECS service.

Validate the Following

1. NiFi UI is accessible.

2. Existing flows are visible.

3. No certificate errors appear.

4. No startup failures appear in logs.

Validation Commands

docker logs <container_name>

or

aws ecs describe-services

Update the InvokeHTTP Processor

1. Log in to the NiFi UI.

2. Open the existing InvokeHTTP processor.

3. Update the following processor properties:

   1. Remote URL

   2. SSL Context Service (if configured)

   3. Authentication configuration

   4. HTTP Method

   5. Request timeout settings

      Ensure all values match the latest OvalEdge application configuration.

      Example:

      https://ovaledge.company.com/api

      Use the URL currently configured for the OvalEdge application environment.

Validate the Following

1. URL connectivity

2. processor execution status

3. successful HTTP communication

4. processor scheduling state

Expected Result

The processor status displays:

• Running

• No communication errors

Apache NiFi Bridge Client Upgrade (Windows)

Environment Information

Parameter	Text
Operating System	Windows
Existing Java Version	JDK 17
Target Java Version	JDK 21
Existing NiFi Version	1.25.0 / 1.28.1
Target NiFi Version	2.6

Verify Existing NiFi and Java Versions

1. Open Command Prompt as Administrator.

2. Navigate to the existing NiFi bin directory.

   cd C:\ovaledge\bridge_client\nifi-1.28.1\bin

3. Verify the NiFi service status.

   nifi.bat status

   Sample Reference Screenshot:

   
4. Verify the Java version.

   java -version

   Sample Reference Screenshot:

   

   Expected Result

   NiFi Version: 1.28.1 or 1.25.0
   Java Version: 17.x

   • NiFi Service Status: Running

   • Process Identifier (PID): <PID>

   • Application Status: Running

Stop the Existing NiFi Service

1. Open Windows Services.

2. Stop the existing NiFi service.

Validation

Verify the service status changes to:

• Stopped Sample Reference Screenshot:

  

Remove the Existing NiFi Windows Service

1. Open Command Prompt as Administrator.

2. Delete the existing NiFi service.

   sc delete <service_name>

   Sample Reference Screenshot:

   

   Example

   sc delete nifi

Validation

• Verify that the service has been successfully removed from Windows Services.

The sc delete command removes only the Windows service registration.

Important

1. It does not remove:

   1. NiFi installation files

   2. Configuration files

   3. Bridge artifacts

   4. Logs

2. The NiFi installation directory remains unchanged.

Back Up Existing Bridge Files

Mandatory Backup Activities

Back up the following:

1. Existing NiFi installation directory

2. BridgeRegistration.properties

3. Existing Bridge ZIP artifacts

4. Java cacerts file.

• The Java cacerts file may contain organization-specific SSL certificates used for secure communication with:

  • OvalEdge Application

  • Databases

  • Cloud Services

  • Internal APIs

• Retaining a backup prevents certificate trust issues after the Java upgrade.

Important Files

C:\ovaledge\bridge_client\nifi-1.28.1
C:\ovaledge\bridge_client\nifi-1.28.1\conf\BridgeRegistration.properties

Sample Reference Screenshot:

If the original Bridge ZIP artifact is unavailable, retrieve it from the client Bridge server temporary directory.

Install OpenLogic JDK 21

1. Download and install OpenLogic JDK 21.

2. Java Download: OpenLogic JDK 21 Download

Installation Procedure

1. Double-click the .msi installer.

2. Click Next.

   
3. Complete the installation wizard.

4. Click Finish.

   

Update Java Environment Variables

1. Open: Edit the system environment variables

   
2. Update the Variable name and Variable value as shown below.

   
3. Update the Java environment variables.

4. Remove the existing Java 17 path and add the Java 21 installation path

   

   Example:

   C:\Program Files\OpenLogic\jdk-21

5. Open a new Command Prompt window.

6. Verify the Java version.

   java -version

   Sample Reference Screenshot:

   

Expected Result

openjdk version "21"

Uninstall JDK 17 (Optional)

Recommended

• Uninstall JDK 17 after validating that the NiFi 2.6 upgrade successfully completes.

  

Important

• Back up the Java cacerts file before uninstalling JDK 17.

Create a New NiFi Client Directory

1. Create a new directory for the upgraded Bridge Client. Sample Reference Screenshot:

   

   Example

   C:\ovaledge\bridge_client\nifi_2.6_client

Download and Run the Bridge Installer

1. Download the latest Bridge Client installer JAR file.

   • Place the Bridge Client installer JAR in the bridge_artifacts folder on the bridge client VM.

   • Before running the installer jar file, take the values from BridgeRegistration.properties on the Bridge client VM and the existing bridge client conf folder.

2. Copy the installer JAR into the following directory:

   bridge_artifacts

3. Run the installer.

   java -jar <bridge_installer>.jar

   Sample Reference Screenshot:

   

Configure the Bridge Installation

1. During installation, provide the existing values from:

2. Reuse the following values from the existing BridgeRegistration.properties file:

   • Bridge Server URL

   • Bridge ID

   • Registration Key or Token

   • Environment Name

   • Client Identifier

   • Scheduler Configuration (if applicable)

     Ensure all values match the existing Bridge configuration to avoid registration failures after the upgrade.

3. Use the newly created installation directory:

   C:\ovaledge\bridge_client\nifi_2.6_client

Expected Result

The installer displays:

Bridge software installed successfully

Update Bridge Configuration Files

1. The bridge-oe-<version>.nar file is available in one of the following locations:

   1. Existing NiFi installation lib directory

   2. Bridge artifact package provided by OvalEdge

   3. Backup of the previous Bridge installation Example:

      C:\ovaledge\bridge_client\nifi-1.28.1\lib

2. Copy the file into the new NiFi 2.6 lib directory.

Copy Required Files

1. Copy the following files into the new NiFi 2.6 lib directory:

   1. bridge-oe-<version>.nar

   2. sapjco.jar

Validate bootstrap.conf Configuration

1. Open the following file:

   conf/bootstrap.conf

2. Verify:

   1. BridgeRegistration.properties values

   2. JVM arguments

   3. Java heap size settings

Example

java.arg.2=-Xms4g
java.arg.3=-Xmx4g

Update nifi.properties

1. Open:

   conf/nifi.properties

2. Locate the following properties:

   nifi.flow.configuration.file=./conf/flow.xml.gz
   nifi.flow.configuration.json.file=./conf/flow.json.gz

3. Update the configuration:

   nifi.flow.configuration.file=./conf/flow.json.gz
   #nifi.flow.configuration.json.file=./conf/flow.json.gz

   Sample Reference Screenshot:

   
4. Save the file.

Restart NiFi

1. Navigate to the NiFi bin directory.

2. Start NiFi.

   nifi.bat start

Validation

Verify:

• NiFi starts successfully

• No startup exceptions appear

• The NiFi UI opens successfully

Validate Bridge Status in the OvalEdge UI

1. Log in to the OvalEdge application.

2. Verify the Bridge status.

Expected Result

The Bridge status displays:

• Connected

• Running

Validate Connector Connectivity

1. Perform connector validation checks from the OvalEdge application.

   

Validate the Following

• Connector connection status

• metadata crawling

• lineage extraction

• scheduler execution

• profiling execution

• SAP connector communication

• Bridge response time

Expected Result

All connectors execute successfully without Bridge communication failures.

Rollback Procedure

Perform rollback if:

1. NiFi fails to start

2. connectors fail consistently

3. Bridge communication fails

4. If the upgraded ECS task fails:

   1. Open the ECS Service.

   2. Select the previous task definition revision.

   3. Deploy the previous revision.

   4. Verify container startup.

   5. Confirm NiFi accessibility.

5. processor validation fails

6. Metadata crawling stops unexpectedly

Rollback Steps

1. Stop the upgraded NiFi service.

2. Restore the backed-up nificonf directory.

3. Restore the previous ECS task definition or Bridge installation.

4. Restore previous Java configuration if required.

5. Restart the original NiFi version.

Validation

Verify:

• original flows are visible

• Bridge status is healthy

• connectors execute successfully

Post-Upgrade Verification Checklist

Verify the following after completing the upgrade.

Validation Item	Expected Result
NiFi UI accessibility	Accessible
Bridge status	Connected
InvokeHTTP processor	Running
Connector validation	Successful
Metadata crawling	Successful
Lineage generation	Successful
Scheduler execution	Successful
SAP communication	Successful
Application logs	No critical errors

Known Limitations

• Existing custom processors must be validated for NiFi 2.6 compatibility before deployment.

---

Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA, USA.