By the Multi-Tenant-Support feature Multitenancy support (also known as mandant protection) enables a single instance of tia Core is able tia® Content Server core to support multiple, separated tenants. When working in multi-tenant multitenancy mode, each request must be sent naming the tenant. Each tenant then gives the abstraction of working on sent to tia® Content Server core must name the tenant the request is addressed to. So each tenant provides the impression of working with a separate instance. Summarizing, each request must be targeted to exactly one tenant, and it is not possible to access the tenant data without referencing it explicitly. In other contexts, multi-tenant-support is also known as mandant-protection.Multi-Tenant-Support
Multitenancy support starts with version 2.5.0 of tia Coretia® Content Server core.
tia Core tia® Content Server core supports tenants for the protocols SAPHTTP (ArchiveLink), ILM, and CMIS.
When the feature is activated, the tentant is referenced in requests to tia Core tia® Content Server core by HTTP header X-TiaClientId. A typical configuration is exposing a service ip by a proxy that sets this header.
Configurating tia Core for Multi-Tenant-Support
Multi-tenant-Multitenancy support is activated in repository.cfg file the application-wide settings by setting the parameter repositoryfactory.tenant-support to true. For general information about configuration topics see Repository- Application wide settings .
Is also is mandatory, when activating Multi-Tenant-Support that EVERY repository is When multitenancy support is activated, every repository must be linked to a tenant. This is achieved by including the tenant name into the repository name by this scheme:
| Code Block |
|---|
<tentant>__<repository> |
| Info |
|---|
Note: The separation characters between After activating Multi-Tenant-Support, repository names not following this scheme are not accessible. |
...