About Multi-Tenancy
- 19 Jul 2022
- 1 Minute to read
- Print
- DarkLight
This documentation version is deprecated, please click here for the latest version.
About Multi-Tenancy
- Updated on 19 Jul 2022
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
v.7x instances do NOT CURRENTLY SUPPORT Multi-Tenant (MT)
v8.x instances expect to support MT. Please plan upgrades accordingly or contact Support for assistance.
Overview
Multi-Tenancy is a Server Architecture that allows multiple independent installations of Decisions to run as instances on a single Server. The Server responsible for hosting the application and its database is called the Control Instance Server. This is where Tenant maintenance is handled and where relational data about the Tenant is stored. System Administrators can control Permissions, Account Assignments, and other parameters from the Control Instance.
Developing on a Control Instance
Although it is possible, it is NOT recommended as Control Instances are used for managing Tenants. Changes that negatively impact the Control Instance through testing may affect the Multi-Tenant Server it's build upon.
A Tenant is one of the independently running instances on a Multi-Tenant Server with the ability to customize parts of the application, such as the look and feel of the Portal. However, a Tenant cannot customize the underlying application code. Tenants will all run the same version of the application with a Multi-Tenancy architecture, the provider only has to make updates once. Each Tenant runs on its own database with its own secure install, so data is isolated and remains invisible to other Renants.
Additional Information
The diagram below illustrates the relationship between a Control Instance Server and its multiple Tenants in a Multi-Tenant environment.
.png)
Was this article helpful?
