Upgrading from 2.8 to 2.9

Overview

The upgrade to IBM Financial Services Workbench 2.9 is supported from the earlier versions 2.8, 2.7, 2.6, 2.5, 2.4, 2.3 and 2.2.

To upgrade IBM Financial Services Workbench from the previous version 2.8 to 2.9, just follow the steps in the Upgrade steps section below.

If upgrading from a version prior to 2.8, please first follow the instructions of one of the corresponding subsections 2.2, 2.3, 2.4, 2. 5, 2.6, or 2.7 to upgrade to the previous version 2.8, and then continue with the steps in the Upgrade steps section.

In any case you have to upgrade the Solution CLI only once to the latest version (4.2.64).

Upgrade steps

Event topics migration

In the past, event topics were created automatically in Kafka with a given naming pattern that included the k5-project, project name, domain name and the event name. From 2.9 on, Kafka topics can be referenced with Event Topic Bindings that can be created in the Solution Hub. To help with this change, a migration script is executed in the init container of the configuration-management the first time it is deployed.

Note: This script takes all event topics that match the given pattern and creates an Event Topic Binding for each topic. You can edit or delete the migrated event topic bindings or create new ones in the Environment section of the Solution Hub but no mandatory steps are needed.

Migrate Java low-code projects

All existing low-code projects with implementation language Java need to be updated in the Git repository due to a known issue. There is only the root level pom.xml file that has to be changed.

Search for the parent attribute and change it according to the following snippet:

<parent>
    <groupId>de.knowis.cp.sdk</groupId>
    <artifactId>cp-framework-managed-sdk-parent</artifactId>
    <version>2.1.18</version>
    <relativePath>./.framework/repo/de/knowis/cp/sdk/cp-framework-managed-sdk-parent/2.1.18/cp-framework-managed-sdk-parent-2.1.18.pom</relativePath>
</parent>

Migrate Java low-code and pro-code projects

By default, JUnit 5 is now set as the test library in Spring Boot. If you want to use JUnit 4, you have to add the following dependency in pom.xml.

<dependency>
  <groupId>org.junit.vintage</groupId>
  <artifactId>junit-vintage-engine</artifactId>
  <scope>test</scope>
  <exclusions>
    <exclusion>
      <groupId>org.hamcrest</groupId>
      <artifactId>hamcrest-core</artifactId>
    </exclusion>
  </exclusions>
</dependency>

Upgrade Solution CLI

Upgrade the Solution CLI to the latest version (4.2.64).

fss upgrade-cli