Windows upgrade

This topic describes how to upgrade an existing installation on Windows.

Important note before upgrading to 25.2

Starting with version 25.2, Connect exclusively supports only PostgreSQL as the database. Derby is officially deprecated.

Database installation, upgrade, and management are the responsibility of the administrator.

Before upgrading, make sure you have a PostgreSQL database server installed on the machine. For details, see PostgreSQL database.

If you are currently using a version earlier than 25.1

You can only upgrade to version 25.2 from 25.1.

If you are running a version older than 25.1, download and install Connect 25.1, and then start it at least once to enable the necessary database upgrades.

After the above steps are done, run the following command to verify that the current Derby database is ready for upgrade:

Open cmd as administrator, and go to the Connect installation path (...\Micro Focus\Connect).
Execute the following command:
```
./jre/bin/java -jar ./Utilities/mfcMaintenance.jar -basePath . -dbValidate -dbValidateVersion
```
If validation passes, the result is Database validated successfully.

If validation fails, the result is Schema version is not updated or Data version is not updated.

Upgrade overview

This section guides you through the steps for upgrading to a later version of the product. We recommend using the latest version of Connect and its connectors, to benefit from the added capabilities and enhanced stability.

It is important to understand that upgrading to version 25.2 requires migrating from Derby to PostgreSQL. Follow the steps below carefully to ensure proper migration and upgrade.

Note: If you are upgrading from a prior version that uses a separate database deployment, contact support for upgrade guidance. The separate database deployment option has been deprecated until further notice.

Upgrade step 1: Before database migration

Download the latest version of Connect Core from AppDelivery Marketplace.
Download the latest version of the relevant connectors from AppDelivery Marketplace.
Download all connector dependencies as specified in the connector Readme files. The Readme files are included in the download packages.
Stop the Connect Web Server.
Zip and backup the entire Connect folder as a safety measure.
Launch and run the Connect installer of the new version.

In the wizard's Database Connection Options page, select one of following, depending on your PostgreSQL database configuration:
- Connect to an existing database. Select this option if you are using PostgreSQL database initialization. In this case you have to manually create the database. For details, see Create database manually.
- Create new database by admin user. In this case, provide the PostgreSQL admin user credentials and admin database, to establish the required admin session.
When complete, copy the relevant connectors with their dependencies into the AppData/Connectors folder.
If you have modified utility scripts (for example the .bat or .sh files), merge the modifications into the newly installed utilities. The utilities are installed together with Connect.

Caution: Do not copy over or merge older .jar files back into the new/upgraded install.
If you have installed security certificates, copy the certificates from the backup and replace cacerts in <install path>/Connect/jre/lib.
If you changed the running port or are using https/ssl, copy the server.xml file from the backup, and use it to replace server.xml in <install path>/Connect/WebServer/conf.

Upgrade step 2: Database migration

Prepare for migration:

During database migration, we recommend having available 24 GB of RAM, and 5 times the Derby database size as storage.

To check the Derby database size, verify the size of the AppData/data folder where the Derby database is located.
Perform the migration:
1. To perform the database migration, run the utility script mfcMigrateDataToPostgres. See Batch utility scripts for more information.
  
  Execute the script from a command prompt with administrator privileges to view the migration output.
2. If a previous migration attempt failed, or if you need to re-run the process, execute the mfcMigrateDataToPostgres script with the -force argument.
3. To troubleshoot a migration failure, check the DerbyToPostgresMigration.log file in AppData/logs folder.
Clean up migration files:

Once you see that Connect runs successfully after migration, you can clean up the migration-related log and metadata files. These are located in the derby_to_postgres_migration directory in the <Connect Installation location>/AppData directory. This can be permanently deleted.
If migration fails, check the following:
- Disk space. If you don't have the required disk space available (5 times the Derby database size), migration will fail. To resolve this issue, make sure you have enough disk space available, as described in the migration logs.
- Insufficient RAM. In rare situations, 24 GB of RAM may not be enough to migrate. Make sure that you have more available RAM space on the system.
  
  To start the migration with more than 24 GB RAM, modify the mfcMigrateDataToPostgres utility script. For example, to set it to 32 GB RAM, search for -Xmx24G and replace it with -Xmx32G.

Upgrade step 3: After database migration

Open the Services console and start the Connect Web Server service.
We recommend running the Purge script on a regular basis. Use Windows Task Scheduler to set up a nightly run of the utility at a convenient time. For details, see Purge files on Windows as a nightly task.
Log in, click the Info button, and select About. Verify that all builds and connectors match the latest version that you installed.
Start up the connections, one connection at a time. Verify that each connection is running correctly before starting the next one.