By the Multi-Tenant-Support feature a single instance of tia Core is able to support multiple, separated tenants. When working in multi-tenant mode, each request must be sent naming the tenant. Each tenant then gives the abstraction of working on 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 starts with version 2.5.0 of tia Core.
tia 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 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-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 .
Is also is mandatory, when activating Multi-Tenant-Support that EVERY repository is 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 underline characters.
After activating Multi-Tenant-Support, repository names not following this scheme are not accessible.