- Updated on 22 Jan 2020
- 2 minutes to read
Though it is possible to develop a Control Instance on a Multi-Tenant server, it is not recommended to do so. Control Instances are used for managing tenants, so devoloping on one is not ideal. Changes that can negatively impact this Control Instance may affect the Multi-Tenant server it is built upon which could be costly and time consuming to try and remedy.
Multi-tenancy is an architecture in which a single instance of a software application serves multiple customers. In Decisions, the server responsible for hosting the application and its database is called the Control Instance server. The client machines connecting to the Control Instance server are called Multi-Tenant servers. Each instance is called a Tenant. Tenants in a multi-tenant configuration in Decisions have the ability to customize some parts of the application, such as the look and feel of the Decisions portal, however, the 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. The provider can run one instance of its application on one instance of a database and provide web access to multiple customers. In such a scenario, each tenant's data is isolated and remains invisible to other tenants.
Install Decisions on only one server; this serves as both the Control Instance server and the Multi-Tenant Server. Once Decisions is installed, locate the file where Decisions is installed. By default, Decisions installs to Local Disk C. drive.
- Locate Settings.xml
- RestartService Host Manager
- Open Decisions and confirm that the instance is now Hosting.
Multi-Tenant Environment Setup
Locate Local Disk C. > Program Files > Decisons > Decisions Services Manager > Settings.xml > Search for "standard" (select control F to search) > locate ServerType >Standard After the Server Type is located within Decisions the Server Type name is by default called Standard.
Change the name form Standard to Hosted to begin the Multi-tenant Set-up. Next, save and re-open to check that the changes were saved.
Now RESTART Service Host Manager for the changes to upload into Decisions.
To locate Service Host Manager, search for "Services" and then locate Service Host Manager to restart.
It is important to note that Decisions may take longer than usual to restart when initially setting up Multi-Tenant.
When a Multi-Tenant Environment has been Setup, the word [Primary] will display next to the current login user. Hosting now displays under the My Documents Folder.