Version-dependent patch steps

To upgrade to the desired version, you must perform all applicable patch steps from the following list whose patch level is higher than the current patch level and lower than or equal to the target version.

For example, if you want to upgrade to the target version 9.0.18 and your current version is 9.0.3, you must complete all steps from patch version 9.0.4 up to and including patch version 9.0.18.

In case a patch step occurs several times, you must execute it once only (e.g., Tomcat updates).

List structure

Patch level

Patch level requiring a manual patch action. Patching is necessary if you patch from a minor version to the indicated or to a higher version.
Prerequisites

Conditions that must be met for you to perform the patch step manually.
Action/Proceed as follows

Action(s) that must be performed.

9.0.0

Only standard patch steps are required.

9.0.1

Only standard patch steps are required.

9.0.2

Only standard patch steps are required.

9.0.3

Only standard patch steps are required.

9.0.4

Only standard patch steps are required.

9.0.5

Only standard patch steps are required.

9.0.6

Only standard patch steps are required.

9.0.7

New Leaky Bucket Settings

Usage

The fault tolerance setting in the Process Engine determines how quickly the Process Engine shuts down in the event of database connection problems.

Previous settings resulted in shutdown even after just a few connection interruptions. Therefore, the default settings have been revised to tolerate more connection interruptions.

Proceed as follows

Copy the setting from the ibis.xml_patch file placed by the patch installer into your ibis.xml file.

New values

Old values

Impacts:

Application - Process Engine

Prevent database dead locks

While this patch step is optional. We highly recommend performing it before you start the Process Engine.

Requirements

For regular database cleanup batch processing has been introduced with INUBIT-22257. The size of the batch is configurable by adding the configuration to the logsDBConfig.xml file in use.

Proceed as follows

Stop the Process Engine (if not already done)
Open the file <inubit-installdir>/inubit/server/ibis_root/conf/logsDBConfig.xml, maybe logsDBConfig.xml.bak

Add the following section inside the <dataEntriesLimit> element:

<dataEntriesLimit>
        ...
<!-- Chunk size for batch deletion to prevent lock contention on large DELETE operations.
        Rows are deleted in chunks with intermediate commits to release locks and allow
        concurrent INSERT operations to proceed.
        Default: 5000 rows per chunk
        Tuning: Increase for large tables with infrequent deletes; decrease if lock contention persists
        -->
       <batchDeleteChunkSize>5000</batchDeleteChunkSize>
</dataEntriesLimit>

Save the changes as logsDBConfig.xml file.
Start the Process Engine

Impacts:

Application - Process Engine

Use new feature by Keycloak

This patch step is optional.

Requirements

Keycloak has been updated to 26.6.1.

Proceed as follows

Open the file <inubit-installdir>/inubit/server/ibis_root/conf/keycloak_template.json

Add the following section inside the "documentation": element in between "admin-group-priority" and "client-ids" :

"group-description": "If added, fetches the Keycloak group descriptions alongside the group names. If not added, group descriptions are ignored.",

Save the changes as keycloak_template.json file.

Impacts:

Application - Installer
Application - Process Engine
Component - User Manager

Virtimo Cluster Manager Update

This INUBIT version updates the Cluster Manager to include the behavioral change described in Changelogs.

Prerequisites

You are using the Virtimo Cluster Manager. The patch installation has not yet been performed.

Action before running the patch installer

On all cluster nodes, open the configuration file located at <SUITE-INSTALL-DIR>/inubit/server/ibis_root/conf/clustermanager/virtimo_cluster_config.xml.
Ensure that there is only one node with the highest priority value:
```
<properties>
...
<priority>...</priority>
...
</properties>
```
Save the changes.
Update the node with the highest priority first.
Start this node so that it rejoins the cluster.
Now update the remaining cluster nodes (one by one).
You can then restore the previous priority configuration.

Impacts:

Application - Cluster Manager