Multitenancy
- Armin Franke
- Fabian Nola
Multitenancy support (also known as mandant protection) enables a single instance of tia® Content Server core to support multiple, separated tenants. When working in multitenancy mode, each request 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.
Multitenancy support starts with version 2.5.0 of tia® Content Server 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® 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
Multitenancy support is activated in the application-wide settings by setting the parameter repositoryfactory.tenant-support to true. For general information about configuration topics see Application wide settings .
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:
<tentant>__<repository>Note: The separation characters between <tenant> and <repository> are two underscore characters.
After activating Multi-Tenant-Support, repository names not following this scheme are not accessible.