...
removed tab Database
Changes in Behavior
Performance improvement and multi
...
line index file handling
The main objective for this major change was performance optimization. Until DocumentRouter3, index file processing is single-threaded.
This means that the index files are treated in parallel, now. In order to fullfil fulfill stiff the max-fetch-file-feature we needed to redesign multiline multi-line index file handling.
In version 4, if an a multi line index file is found, it will be first splited split into single line index files. Therefore the error handling for such files has changed. THe multiline The multi line index file is splitted and after successful split it will be moved to Success folder (or deleted). If it fails, created index files are gone deleted and the multi line index file is moved to Failure (or deleted). After the split, the single line index files are handled normal.
Another change is about the schema file reading. In version 3 on every index file read the schema was read and parsed again. In Version 4 the schema file reading and parsing is done once at the start of the instance. The parsing result is cached. This cache is deleted if schema file change takes place. This mean as well, that if the schema file is changed for another instance, all instances will reread its schema. So In this manner we could maintain the old behavior that the schema file change is effective on every file handling.
SID mapping
While in DR3 SID mapping was realized by a SID mapping definition file it can be done by referencing to an existing SAP connection (defined in SAP connector plugin) via index file, now. Further details can be found here: https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/2311028919/DR4+-+Defining+DataInterfaces+SIDMappings+and+Archive+Link+Mappings#SIDMapping-definition.
Archive Link Connection mapping
In DR3 connection mapping for KGS Access API was reusing SID mapping
...
TODO, which was primarily foreseen for linking.
In DR4 the same, former named SID definition file, can be used for Archive Link connection mapping. The reference to this file can be found in instance configuration tab Archiving. Further information can be found here: https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/2311028919/DR4+-+Defining+DataInterfaces+SIDMappings+and+Archive+Link+Mappings#Archiv-Link-Connection-mapping . Reusing DR3 config files in DR4 will overtake the SID-Definition-file valueas value for Archive Link Connection mapping.