Downgrade Guide

If you need to switch back to an older BPC version, there is the General Downgrade, which should work in most cases. If this is not possible due to an error with the model versions of the internal configuration, then Downgrading when internal configuration versions differ will certainly help.

General Downgrade

The following is the procedure to follow if no migration of the internal configuration was performed by the BPC version being replaced. The " Affected Versions " section lists the BPC versions for which a migration was performed.

Procedure

The necessary steps are outlined here.

Karaf must be running
Copy the jar/war files from the previous/older BPC version to the karaf/deploy directory.

That should be all.

Downgrading when internal configuration versions differ

As described at Versioning of the Internal BPC Configuration, the internal model of the BPC configuration changes from time to time. This is located in the OpenSearch index with the alias bpc-configuration.

When a new version of the BPC Core module is launched, the settings from the bpc-configuration index are migrated to the next version of the internal model, if necessary. Once this has been done, it is no longer possible to restore or roll back to an older BPC version.

In that case, a snapshot/backup of the bpc-configuration index that matches the version of the “older” BPC must be restored.

Procedure

The steps required for this are outlined here.

Karaf must be running
Copy the jar/war files from the previous/older BPC version to the karaf/deploy directory. This must be done first; otherwise, the currently installed/newer BPC Core will run and migrate the index again.
Open the Karaf console
List the snapshots/backups of the bpc-configuration index with the BPC configuration:
```
bpc:backup-list bpc-configuration
```
The snapshots that can be used with this version are marked, and only these can be restored.
Restore the appropriate snapshot
```
bpc:backup-restore <snapshot-name-vom-schritt-davor>
```
Snapshots with newer model versions cannot be restored.

If the commands bpc:backup-list and bpc:backup-restore are not available in the Karaf console, investigate why the bpc-be-core bundle is not in the 'Active' status.

If the bpc-be-core bundle cannot be started due to a faulty BPC configuration in the bpc-configuration index, stop Karaf, delete the bpc-configuration index, and repeat the process.

This assumes that snapshots of the bpc-configurtation index are also available.

Keywords: