Services provide many different functionalities for a repository.
The services available are:
Service |
|
|
|---|---|---|
Meta Service | required for CMIS not available for ArchiveLink | Managing meta data. |
Retention Service | optional | LegalHold and ClientManaged retention are features of Core of tia and need do not need configuration |
Data Encryption Service | optional | Only required when data encryption is relevant |
Keystore Service | optional | Only required when access data encryption is relevant |
Config Service | required | Service is required for saving config files in filesystem |
Content Service | required | Stores resources and collections in storage systems |
Protocol Service | optional | can store read, write, update and delete protocols in supported databases |
Meta Definition Service | 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 parameters for services therefore follow this format:
<repository>.<service>.[etc]
For example:
ZQ.contentservice.proxy.primary.type = splitfilesystemv2