General Information (Store)

Owned by Former user (Deleted)
Last updated: Apr 30, 2021
3 min read

System Requirements

For the system requirements and prerequisites regarding tia® Store please refer to Prerequisites for tia® and kgs Software Components

Storage types

The SAP ArchiveLink-model is based on a "Document / Component"-structure. A document is a container that may contain one or more components. A document may in theory also contain zero components. Depending on your configuration and the flavour/-s of storage systems you provide KGS Store will create a directory tree for each document. The tree may follow this structure:

/<Archpath>/<ContentRepositoryID>/<DocumentID (splitt into multiple sub-sections)>/<Last digits of DocumentID

All documentIDs may have a minimal length of 12 characters (leading zeros may be added to it). All document and component files may start with the last three digits of the document ID.

For every SAP document a *_Info-file may be created which contains properties related to the SAP document. For every SAP component a *_comp-ID.Data-file as well as a *_comp-ID.Info-file may be created.

The *_comp-ID.Data-file may contain the data of the archived component. The *_comp-ID.Info-file may contain additional properties and information related to the archived component.

Sample (STORAGEFS)

ContentRepositoryID: T1

DocumentID:             0F24D05D46A6CC478CB48EA4734AFE8 

Components:            1 Component


Unsupported characters in DocumentID

If a provided DocumentID contains characters which may lead to a sub directory structure which isn't allowed (for example names like: COM1, LPT1 or contains characters which aren't supported by the storage system like "<>:?") the pathname may be encoded by Base32 algorithm and you may find a subfolder called "codedIds". The path may have the same structure as described above.

Unsupported characters in ComponentID

If a ComponentID contains characters which aren't supported (like \</>:?) the separator between the last characters of the DocumentID will be "-codedid_" instead of "_".

The ComponentID may be encoded by Base32 algorithm as well.

Filenames exceeding the allowed filename length

If a ComponentID leads to a filename which may exceed the allowed filename length of your filesystem (or the length defined by the parameter MaxFileNameLength) the separator between the last characters of the DocumentID "_" may be replaced by "-codedFP_".

The ComponentID may be used to create a hash value (Fingerprint) which will be encoded using Base32 algorithm for having the shortest possible filename that is associated to the ComponentID.

The original ComponentID may be stored in the Component-Info-file in this case.


→ Installation (Store) | tia® Store (EN)