/
Changelog (MIG)

Changelog (MIG)

4.1.4

24.02.2025
  • fix an hash issue during reprocessing

  • add configuration to add repository in serverInfo

4.1.3

02.09.2024
  • fix an issue with oracle connections

  • fix an rare issue with wrong sorting during reprocessing of non kgs sources for documents with multiple components

4.1.2

12.06.2024

 

  • add support for additional creation date format: yyyyMMdd and time HHmmss

4.1.1

19.04.2024

 

  • removed a bug with Repositories starting with a space

  • fixed a bug with skipExisting when orgin-datesource was null

  • fixed a bug where a cleanup was triggered in the destination before a migration

  • updated versions

  • smaller fixes (typos etc.)

4.1.0

29.11.2023

 

  • datatype is now a mandatatory field

  • setOriginalDateTime is now default set to truee, existing configurations remain unchanged

  • datesource in migration reports is now the creation date of the components from source archive

  • fix an issue that prevents using tia classic ContentServer Version 6.x as target

4.0.0

08.11.2023

Major Release

  • Change to Jarkata Servlet >= 6.0 - Breaking Change: is only running on modern Java-Webserver that supports JakartaEE (e.g. Tomcat 10 …) and Java 17+

  • Security-Fixes

 

3.2.17

28.06.2023
  • fixed that the migration sends only characters in compIds in create that are not ASCII UTF-8 encoded to support SAP ContentServer

3.2.16

23.06.2023
  • fixed that the migration sends the compIds with spaces encoded as + symbols to the destination

3.2.15

14.04.2023
  • support for new tia core saphttp (>= 2.1)

3.2.14

28.03.2023
  • update commons-text from 1.9.0 to 1.10.0

 

Improvement / Fix

  • DOMP-PROPERTY-RETENTION and DOC-PROPERTY-RETENTION removed from create URL while deliver if config flag Property retention on create disabled (Tab "Migration" (MIG) )

Improvements

  • update security toolkit to 1.5.0 with tia certificate

  • added opportunity to select tia certificate

  • updated proxy to 1.2.1

Improvement

  • Fix: removed feature from release 3.2.9 (Migration now also works when the H5 Viewer is enabled at the source content server)

 

Improvement

  • Change handling of SkipExisting

 

WARNING: Breaking changes! If you are not using a custom database, changes have to be made to the existing H2 database, or existing data will be lost. Please see Update H2 Database from 1.4.199 to 2.2.220 for documentation of the required changes.

Improvements

  • When the configuration options ‘SkipExisting’, ‘CheckSrcHashValues’ and ‘CheckDstHashValues’ are enabled and the source Document ID exists in the destination archive, then the checksums of both documents are compared and different checksums lead to Errors

  • Migration of documents with many components lead to SQL errors

  • Migration now also works when the H5 Viewer is enabled at the source content server

 

Improvements

  • add Feature: “Prevent trim() in CompIDs” (default: active). With this feature enabled(Configuration Tab “Migration”) it is possible to migrate components that starts or ends with a blank. This also allowes the migration of components that consists only of blanks. * (See note at the bottom)

  • add Feature: support for IXOS overlay fomat “<</IXOSFormId“

  • Another Fallback scenario: In case error-retry is enabled and the documentinfo is always detected something other than UTF-8, the third try enforce UTF-8 as reading Charset for the DocumentInfo-Request (inclusive header). This is needed as the CharsetGuesser + Hint sometimes still detect something not correct which is most likely UTF-8.

  • Headers with invalid format (violating the ArchiveLink-Specification) are tried to convert in the valid format (only date/time headers while receiving documentInfo from source are validated).

  • Note: Be aware: you need a destination storage that allow that scenario. The KGS Store (with FS,Azure,S3 and DB) supports that feature since version 3.8.5.

 

 

Improvements

  • add Feature: Encoding Hints for componet-Ids charset detection. Support Fallback to UTF-8 when the encoding is not supported by installed Java Virtual Machine

  • add Feature: add support for OT overlay merging in PDF

  • add Feature: add searchable text layer to PDF

  • add Feature: migration summary export from MSSQL and Oracle databases

  • Enhancement: improve internal lock handling

  • Fix: serverinfo version in ascii mode

  • Fix: conversion were working only with documentens which does have 2 components

  • Fix: CSV export - escaping

  • Fix: NPE if SAPALink and destination hash validation enabled

 

Improvements

  • removed old functionalities (legacy): online

  • added feature “Download all Reports” in summary view

  • added config “remove empty content-type” for cases where source cs delivers empty content-type

  • Added Checksum-Support again for Non-KGS target CS

  • Added Support for MSSQL

  • Feature: Performance Monitor Scrolls with the window

  • Fix: Permanent License Key was displayed falsly

  • Fix: Display Error in German with Temp-Keys (e.g. März)

 

Version wasn't released - modifications can be used since 3.2.6

 

Version wasn't released - modifications can be used since 3.2.6

 

Improvements

  • fix memory leak

 

 

Improvements

  • fix not written msdoc tables

 

 

Improvements

  • fix not visible stop and start button in migration ui

 

 

Improvements

  • Performance Optimizations:

    • in RAM Processing for HTTP Migrations

    • CheckDstHash is handled on CS (target) side (reduced HTTP Requests)

    • transferring document as mCreate (multipart) (reduced HTTP Requests)

    • HTTP-Lock Request is handled on CS (target) side (reduced HTTP Requests)

  • Automatic Tika Charset-Detection for Headerfields (like DocID and CompID) (addressing special character issues)

  • Support for AutoDigit Protocol-Field StatusCode

New Feature

  • Configurable treshhold for InMemory-processing and filebased processing

Important:

  • The KGS Migration 3.2.0 works only with the new KGS Contentserver 5.3.0 as TARGET-System regarding CheckDstHash. It does not work with older Version of the KGS Contentserver (5.2.11 or below). For Non-KGS Target-Systems (like SAP Contentserver, OpenText Contentserver etc.), the Migration will work as expected (“CheckDstHash” and “keepOriginalDateTime” is then not supported).

 

Fix

  • Optimizations regarding RFC download

Improvement

New Feature

  • Added JPG to Multiplage-PDF capabilities

  • Added PDF/A-Searchable option (Windows Plattform only)

Security

 

Fix

  • Improved mimetype override for app/oct-st to tiff

  • Improved SAPALink-Migration

Improvement

  • Updated documentadapter bundle which adds convert to pdf and jpg to pdf capabilities

  • Rework of user interface

  • Extended configuration with OCR

New Feature

  • Integration of MultiConfig

  • Migration over http

  • Decoding of ComponentID added

Security

 

Fix

  • Improved support for encoded and unencoded components.

Improvement

New Feature

Security

 

Fix

  • Fixed issue regardind multiple start and stop operations

  • Fixed issue regarding multipage tiff conversion

Improvement

  • Optimized detail display

  • Improved stability on webserver startup

  • Change of behavior from file locking to socket locking

New Feature

  • Added capability to send certificates

  • Added capability to test connections

  • Added RFC capabilities

Security

 

Related content