Multi-Tenancy Creating Default Tenant Configurations using Prototype Instance
- Updated on 05 Mar 2019
- 2 minutes to read
Creating Default Tenant Configurations using a Prototype Instance is the process of enabling customers to add new tenants that are already setup or configured in Decisions.
After a customer is registered, navigate to the login and select the InstanceDefaultSetupPrototype to log in. The instance default setup is where the Decisionsenvironment is set up for every new instance (Tenant) that is added to the Multi-Tenant environment.
Locate My Apps or a Folder andCreate a Flow.
Log out of the InstanceDefualtPrototype.
Navigate to the File Local Disk (C) > Program Files > Microsoft SQL Server > MSSQLExpress > MSSQL > Backup right click and delete the DecionsInstancePrototype.bak file.
Next continue the update by locating SQL Manager> Databases>DecisionsInstancePrototype to back it up. Right click on DecisionsInstancePrototype select tasks and then select Back up to back up the Database.
Note: Navigate using this pathway: C:\Program Files\Microsoft SQL Server\MSSQL14.SQLEXPRESS\MSSQL\Backup, .
Select Ok to begin the backup. After the database has been successfully backed up a notification displays stating that it has successfully back up, select OK.
After Decisions Instance Prototype has been successfully backed up in SQL server, Log into the account and then choose the Primary Instance in Decisions.
First, log into the account.
Next, select the Primary Instance from the drop down.
In the Primary Instance locate the customer's folder and select a registered customer (Test Company VM) to add anInstance (Tenant) for the registered customer to host. Begin by locating the registered customer, select the customer in the folder view, right-click and choose Add Instance.
Note: Adding an Instance to a registered customer can only be added after a customer is registered and a Registered Configuration (Hosting definition) is assigned to the customer.
Create a new Instance, make sure that the Instance name and theDatabase Name match. Select the correct Accounts and make sure toSelect administrators for theInstance.
Add theInstance name: TestCo Tenant
Under Hosting, Assign To Server: DECLAPTOP16
Under Accounts, Assign Accounts: email@example.com
Under Select Administrators, select Add New and pick the desiredAccounts to add asAdministrators for the newly created Instance.
Add New: firstname.lastname@example.org
Under Databas e give the Database a Name: TestCo Tenant
The New Instance (TestCoTenant) will now be visible under Test Company VM,.
Now Log out of the Primary Hosting environment to view and log into the registered customerTest Company's newInstance, called: (TestCo Tenant) . Locate Customer Test Company VM, right click select Add User Account and choose Link Account.
Pick the desiredAccount andAssign To Instances by checking the checkbox next to eachInstance.
Check: TestCo Tenant
Check: Is Administrator
Now Create an Incognito page to sign in with the administrator account and choose the new Instance TestCo.Tenant , (Figure 15).
The new Instance should now show the new Flow that was created in the InstanceDefaultSetupPrototype (Figure 16).