Introduction

The content service type kgsstore is used to access a historical ArchiveLink dataset via the tia Content Server Core.

The storage configuration is the same as in tia Classic environment:

Just specify in repository.cfg file the parameter kgsstore.configfile with the location of the storage configuration (storage.cfg) of the tia classic environment.

For more information on the available parameters within the storage.cfg, refer to the following tia Classic documentation: tia® Store (EN)

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

This content service type supports

read access to existing ArchiveLink documents.
update and delete access to existing ArchiveLink documents for adding and removing components,
delete documents.

It does not support the creation of new ArchiveLink documents.

To store new documents a tia Proxy configuration is required, for more information see the following link: tia Proxy. So, if a document id already exists in kgsstore, it can be updated with new components. This avoids storing the same document twice in tia Proxy’s primary as also secondary storage.

Configuration example

A configuration example for tia Proxy with kgsstore as proxy.secondary content service can be found here: tia Proxy.