When updating Fabasoft Folio from a version below 2012 Summer Release to a version equal or higher 2012 Summer Release following migration steps have to be considered.
From version 2012 Summer Release numerical values larger than 2^32-1 (or 2^31-1 for negative numbers) are supported. In previous versions numbers are stored as 32 bit values. Since 1 bit is used for the sign (+ or -), for the number range only 31 bits remain. In Fabasoft Folio it can be defined for number properties, whether they use a sign or not. If no sign is used, the negative value range is used for storing large numbers.
In the course of the conversion from 32 bit to 64 bit, those large values that are stored as negative numbers must be migrated. The identification of affected properties is done via the tool upgr122. As part of an update by the Fabasoft Folio Setup this tool will run automatically.
Attention: In the following chapter two scenarios are described that need further manual steps.
Scenario 1: Affected values exist only in versions or in the archive
The automated identification only considers integer properties that contain values of the affected number range in the current version. For integer properties that potentially contain values of the affected number range only in versions or in the archive, a migration CSV file has to be created manually.
The CSV file must have the following format:
1223;9;<object address 1>;<object address 1>;1;1
1223;9;<object address 2>;<object address 2>;1;1
and so on
The object address of the integer property can be set as 64 bit ID or as COO address.
The CSV file has to be stored in the migration folder (<server directory>/CooSrv/files/migration or /var/opt/fabasoft/instances/files/migration) on all backend servers before running the setup, such that the migration is carried out as part of the COO service start-up.
Scenario 2: Fabasoft Folio Backend Services are distributed on several clusters
If Fabasoft Folio Backend Services are distributed across multiple clusters, a manual execution of the tool Setup\ComponentsBase\Services\<Plattform>\upgr\upgr122 is necessary on each cluster. After each run, the output file (phase=1: attridfile; phase=2: csvfile) has to be used as input file for the following execution:
The result file (UINT322INT64.csv) has to be stored in the migration folder (/var/opt/fabasoft/instances/files/migration) on all backend servers before running the setup, such that the migration is carried out as part of the COO service start-up.
This chapter describes a complete update of a Fabasoft Folio Domain and its services.
Note: It is necessary to stick to the given order.
To update a Fabasoft Folio Domain, perform the following steps: