Table of Contents |
Everything within this section is only visible while editing. Use Page Properties ID "STUB", "REFACTURE", "PROGRESS", "rDEV", "rDOC", "rLANG" and "DONE". Everything contained within the table is displayed in the (INTERNAL) Reports page.
Resources & Remarks https://wiki.optimal-systems.de/display/EnaioServices/Archive+Service https://help.optimal-systems.com/enaio/v100/admin/administrator/en/archivieren/archivierung.htm Modification History Add a new line to this table and fill it whenever you edit the page.
|
This core service manages the storage of binary content files and their renditions. Find here characteristics and configuration options. |
|
| Service Name | repository |
|---|---|
| Port Range | 7500-7509 |
| Profiles | prod,storage,docker,kubernetes,redis,metrics |
| Helm Chart | yuuvis |
The REPOSITORY service is responsible for the storage management of binary content files. For this purpose, an S3 store is the standard archive solution. Alternatively or additionally, many external archive providers are supported to be connected via the ARCHIVE Service.
Furthermore, the SHA-256 digest for the binary content files is calculated during there saving processes and stored in the content stream properties section of the corresponding DMS objects.
As of 2021 Winter, a default rendition repository can be configured. Renditions of supported types (listed below) of binary content files assigned to objects can be stored in the default rendition repository. Thus, renditions can be retrieved from storage and are not regenerated for each retrieval request. Whenever a rendition of a supported type is requested for an object, it is retrieved from the default rendition repository. If available, the stored rendition will be returned. If not available, the requested rendition is generated from the binary content file that is assigned to the object, stored in the default rendition repository and finally returned.
The initial generation of a rendition is triggered by its first request.
If a default rendition repository is configured and accessible, the following rendition types are managed in this repository as of 2021 Winter:
| Type | Content-Type | Description |
|---|---|---|
pdf | application/pdf | The PDF representation of the binary content file. No distinction between PDF, PDF/A or PDF with embedded OCR. |
slide (as of 2023 Spring) | image/png | A thumbnail representation of the binary content file. |
If the default rendition repository is not available or not configured, any request for a rendition triggers the generation of a new rendition file. The result is returned but not stored in a repository. Thus, for subsequent requests of the same rendition, it has to be regenerated each time.
The yuuvis® Momentum configuration files for the operation in the Kubernetes cluster are stored on the Git Server configured in the system. In order to change the configuration of a service, you need to access the Git repository.
The following parameters are referenced from the corresponding profiles. Click a profile in order to display descriptions and default values of the corresponding parameters.
| Configuration File | Parameter |
|---|---|
application-storage.yml | storage.default-rendition-repository (as of 2021 Winter) |
storage.repositories | |
storage.profiles |
The values for the parameters can be modified as described here.
>> Configuring Services using Profiles.
Read on
|