Skip to main content

NAV 2013 R2 - Multi-Tenancy Part 2

Hi all,

Previous Post in this series are -
  - MutiTenant Concept.
  - Implementing Multi -Tenancy Part 1.

In This post we will move to next steps to configure Service and Mounting Databases.

Till Now, We have separated the Application and Data Part.

STEPS -



3. Prepare NST for MutiTenancy.
   - Stop the NST.
   - Set MutiTenant to True.
   - Set the Database Name to Blank.
   - Start the NST.
   - Mount the App Data Created in Step 2.

Delete the content of Powershell and Paste Below Commands.
------------------------------------------------------------------------------------
#Prepare NST for Multilatency
Set-NAVServerInstance MultiTenent -Stop
Set-NAVServerConfiguration -ServerInstance MultiTenent -Keyname Multitenant -KeyValue "True"
Set-NAVServerConfiguration -ServerInstance MultiTenent -Keyname DatabaseName -KeyValue ""
Set-NAVServerInstance MultiTenent -Start
Mount-NAVApplication -DatabaseServer "localhost\NAVDEMO" -DatabaseName Customer_App_Data -ServerInstance MultiTenent
------------------------------------------------------------------------------------

Change the Service Instance and Application Database Name. Run the Command and output will be as shown below.



Let's see what changes have been done on the Service Tier.



Database name changed to application database and MultiTenant Set to True.

If you Try to Connect the Windows Client you will end up with the error message as below.


Why this Error?

Because we haven't Mounted Any Tenants.



so i think we can move to Next Step, Mounting Customer Data as Tenants.

4. Create Tenants.

Delete the content of Powershell and Paste Below Commands.
------------------------------------------------------------------------------------
#Mount Customer Database as Tenant
Mount-NAVTenant -ServerInstance MultiTenent -Id Default -DatabaseName "ABC Company Database NAV 2013 R2" -OverWriteTenantIDInDatabase
------------------------------------------------------------------------------------

Change the Customer Database Name & Tenant name if required (Default is default).
Run the Command and output will be as shown below.


Now if you try to connect to Navision Windows Client you can connect after changing the Server URL

From - ServerName:Port/InstanceName

TO - ServerName:Port/InstanceName/Tenant Name

In My Case it Changed from  localhost:8046/Multitenent

TO localhost:8046/Multitenent/Default



Now we can see all the companies in the Tenant. We have achieved "Partial MultiTenancy".

Commands used in this post can be found in My Sky Drive Folder.

File Name - Command 4 - Prepare NST & Mount Customer Database.ps1

In Next Post we will see how we can Break the Customer data Tenants into Further Tenants.


By Saurav Dhyani
saurav-nav.blogspot.in

Comments

Popular posts from this blog

BC 21 and Higher - PowerShell Cmdlet (Replacement of Business Central Administration).

Hi Readers, As discussed in last article about deprecating of Business Central Administration, there are few common actions that we use in administration till Business Central 20. For our on-prem customers, we will still require doing activities. As Microsoft suggest we need to start using PowerShell cmdlet.    Let's see how to do those via PowerShell, or Administration Shell. I will be keep adding commands as you comment to this article.

Send Mail with Attachment From Navision.

Hi all, We have seen how to save a report into PDF and how to send mail to a customer. Let's link these two post in one i.e. Mailing statement to a customer into PDF Format. This article is part of the Series. Please Refer  Table of Content here . If you have the old objects set let me brief you what I will be changing - 

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.