Services 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 Configuration
The services available are:
...
Service | Optional |
|---|
Description |
|---|
Config Data Service | required |
not available for ArchiveLink
Managing meta data.
RetentionService
optional
LegalHold and ClientManaged retention are features of Core of tia and need do not need configuration
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 |
Service is required for saving config files in filesystem
ContentService
required
Stores resources and collections in storage systems
ProtocolService
optional
can store read, write, update and delete protocols in supported databases
MetaDefinitionService
required
handles internal metadata. No further configuration required
Services are configured for each repository separately in the repository.cfg file, which resides in the configuration directory with path: <web server installation>/webapps/<context>/conf.
The parameter names in the repository.cfg file follow a hierarchical scheme. The format of each parameter therefore follows this format:
<repository>.<service>.[etc]
For example:
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.