Multi-Tenancy: Creating Default Tenant Configurations using Prototype Instance

Last Updated: 01/16/2019 Introduced in Version:

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 Decisions environment is set up for every new instance (Tenant) that is added to the Multi-Tenant environment (Figure 1).

Step 1. 


Figure 1


Step 2. 

Locate My Apps or a Folder and Create a Flow (Figure 2). 

Figure 2



Step 3. 

Log out of the InstanceDefualtPrototype (Figure 3).

Figure 3


Step 4. 

Navigate to the File Local Disk (C) > Program Files >  Microsoft SQL Server > MSSQLExpress > MSSQL > Backup  right click and delete the DecionsInstancePrototype.bak file (Figure 4).


Figure 4

Step 5.

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, (Figure 5).

Figure 5



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 (Figure 6).  

Figure 6



After DecisionsInstancePrototype has been successfully backed up in SQL server, Log into the account and then choose the Primary Instance in Decisions (Figure 7).

First, log into the account.

Figure 7


Next, select the Primary Instance from the drop down (Figure 8).


Figure 8


In the Primary Instance locate the customer’s folder and select a registered customer (Test Company VM) to add an Instance (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 (Figure 9).

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 (Figure 9). 

Figure 9



Create a new Instance, make sure that the Instance name and the Database Name match. Select the correct Accounts and make sure to Select administrators for the Instance (Figure 10).

Add the Instance name: TestCo Tenant

Under Hosting, Assign To Server: DECLAPTOP16

Under Accounts, Assign Accounts:

Figure 10


Under Select Administrators, select Add New and pick the desired Accounts to add as Administrators for the newly created Instance (Figure 11). 

Add New:

Under Database give the Database a Name: TestCo Tenant

Figure 11



 The New Instance (TestCoTenant) will now be visible under Test Company VM, (Figure 12 ).

Figure 12


Now Log out of the Primary Hosting environment to view and log into the registered customer Test Company’s new Instance, called: (TestCo Tenant). Locate Customer Test Company VM, right click select Add User Account and choose Link Account (Figure 13). 

Figure 13


Pick the desired Account and Assign To Instances by checking the checkbox next to each Instance (Figure 14).

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).

Figure 15


The new Instance should now show the new Flow that was created in the InstanceDefaultSetupPrototype (Figure 16).

Figure 16


Multi-Tenant: Setup

Additional Resources