Setting up a Control Instance
- 22 May 2024
- 1 Minute to read
- Print
- DarkLight
Setting up a Control Instance
- Updated on 22 May 2024
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
In a multi-tenant environment, the host server is called the Control Instance. It is the primary host for additional Tenant Instances.
The Control Instance can direct users to the desired instance throughout the environment. The following document demonstrates how to install a Control Instance.
Important!
- If the Tenant and Control Instances are hosted on the same server, it is strictly recommended that both applications be hosted on Information Internet Services (IIS).
- If the Tenant Instances are hosted on separate servers, it is essential to align the hosting configuration of the Tenant Instances with that of the Control Instance. The Tenant Instances should also be self-hosted if the Control Instance is self-hosted, similarly for Internet Information Services (IIS). Ensuring consistency in the hosting environment is essential in such scenarios.
Installing Control Instance
- Download and then run the Decisions Installer as an Administrator.
- Continue with the installation until the Select Installation Type window. Select Multi-Tenancy Server (Control), then click Next.
- Proceed with the installation as outlined in the Installation Guide.
- Complete the installation process, then open the Studio and verify that the environment contains the System > Hosting Folder with the created Instance Name visible in the Folder's respective Report.
Accounts assigned to Control Instance
By default, when a new account is created in a Control Instance, it is automatically assigned to the Control Instance unless otherwise unchecked from the settings. Additionally, administrators have the ability to assign accounts to specific tenants available on the Control Instance. To create a new account, refer to Creating Accounts.
Was this article helpful?
