Introduction

the content service type kgsstore is used to access a historical ArchiveLink dataset via the tia content server core edition.

If no metadata is needed for this data area, this setup does not require any migration.

Note: This content service type is only supported as read-only for the historical ArchiveLink dataset.

to store new documents e.g. via the cmis interface a tia core proxy configuration is required, for more information see the following link: https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/2630975491

Availability

Please make sure you are using at least tia core version 2.7.0.

Architecture overview

The following architecture sketch shows the relationship between the implementation of kgsstore classic edition and kgsstore tia core edition.

[the best is yet to come ]

Configuration example

with this configuration we point the contentservice type = kgsstore to the "tia content server classic edition" storage.cfg configuration file.

#===== T1 repository configuration 
T1.contentservice.type     = kgsstore
T1.accessmode              = r
T1.configdata.filesystem.root=/temp/meta
T1.saphttp.security=2

#===== T1 content service configuration (filesystem|azureblobstore|s3blobstore|kgsstore)
T1.contentservice.kgsstore.configfile = /opt/tia/conf/storage.cfg
T1.contentservice.kgsstore.context    = default

#===== T1 keystore service configuration (none|pkcs12)
T1.keystoreservice.type = pkcs12
T1.keystoreservice.pkcs12.name = tiacore
T1.keystoreservice.pkcs12.path = /opt/tia/keystore

#===== T1 meta service configuration
T1.metaservice.type = none

for more information on the available parameters that can be configured within the storage.cfg, please refer to the following documentation https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/153911480