Services (tC)
- Stefan Franz
- Simone Conrad
- Armin Franke
- Benjamin Schröder
tia® core services provide many different functionalities for a repository. All services implement the Spring service concept.
Services are configured for each repository separately in the repository.cfg file. For more information about this configuration file see https://kgs-software.atlassian.net/wiki/spaces/DOCUEN/pages/2741796866
The services available are:
Service | Optional | Description |
|---|---|---|
Config Data Service | required | Handles the storage of persistent configuration options such as metatype definitions. |
Content Service | required | Stores resources and collections in storage systems. |
Encryption Service | optional | Only required when data encryption is relevant. |
Keystore Service | optional | Only required when access data encryption is relevant. |
Meta Service | required for CMIS optional for ArchiveLink | Managing meta data. |
Protocol Service Protocol Reader | optional | Writes, updates and deletes protocols into supported databases, respective provides a REST API to read these protocols. |
Retention Service | optional | LegalHold and ClientManaged retention are features of tia® core and do not need configuration |
Meta Definition Service | required | From a technical point of view, this is an internal service that processes internal metadata. It is mentioned for the sake of completeness. From a user perspective, there is no configuration required. |
There are also other services for system-internal purpose.