Skip to main content

NAV 2013 R2 - Multiple Web Clients.

Hi all,

As we have multiple RTC Clients, can't we have multiple Web Clients  Server?

*Thanks for the update +Mukesh Verma, sorry for misleading information.

We had already done it in NAV 2013, Let's try to do it on NAV 2013 R2.

The requirement was raised by Mr. +Ganesh S. All thanks to him for finding that there are changes in NAV 2013 R2 for multiple web clients.



1. To Achieve this we will be using the Powershell. If you are un-aware about Powershell read here.

2. I opened the Cmdlet created in earlier post, can be downloaded from here.
(File name - Command 1 - Import NAV Module.ps1)

3. Executed the script which will enable to Navision cmdlet in the powershell. Refresh the Command Addon.

4. If you don't see the Commands Addon on Right open it from view menu as shown below.



5. For Creating New Web Client Instance we will use Cmdlet New-NAVWebServerInstance.

6. Just Search for New-NAVWebServerInstance and select in Command Add-on and below are the steps.

a. Enter These Parameters.
  - Server Name. (Name of NAV Service Computer)
  - Server Instance. (Name of Instance you want to connect)
  - Web Server Instance. (Name you want to give to Web Site in IIS).
  - Client Service Credential Type.
  - Client Service Port.
  - Company. (If Required).






7. From the Bottom of Command Window Select Run.

HERE IS THE CmdLet THAT CAN BE USED TO DO ALL in ONE GO.
------------------------------------------------------------------------------------
#Prepare PowerShell
Set-ExecutionPolicy unrestricted -Force
Import-Module 'C:\Program Files\Microsoft Dynamics NAV\71\Service\NavAdminTool.ps1'

#Create Another Web Client
#Change these parameter as per your requirement.
  # - Server
  # - ServerInstance
  # - WebServerInstace
  # - ClientServicesCredentialType
  # - ClientServicesPort

New-NAVWebServerInstance -Server localhost -ServerInstance JetReport -WebServerInstance MyWebClient2 -ClientServicesCredentialType Windows -ClientServicesPort 1046
---------------------------------------------------------------------------------------

8. All Done and web site should be available in IIS. Let's Open ISS and check.



The two web clients are working as shown below.


Here is what Happened (What i Think).

1. The Command Copy the Existing Folder of Web Client and Paste with New Name as specified in the Command Parameter.

2. Added the New Folder in IIS.

Here are differences between two web.config Files.


So for me this was simpler than what we did in NAV 2013.

You can download the complete cmdlet from my skydrive folder.
(File name - Command 2 - Create Web Client Instance.ps1)

Let me know if you have any issues.

Regards,
Saurav Dhyani
saurav-nav.blogspot.in

Comments

Popular posts from this blog

VIEW SERVER STATE permission on SQL Server?

Hi all, Sometime While trying to Login into a database we face an error message as shown below. --------------------------- Microsoft Dynamics NAV Classic --------------------------- You cannot start Microsoft Dynamics NAV Classic because you do not have the VIEW SERVER STATE permission on SQL Server. Contact your system administrator. --------------------------- OK    ---------------------------

NAV 2013 R2 - Cumulative update 12 Released.

Hi all, Please find below the details of  Cumulative Update 12 released for Microsoft Dynamics NAV 2013 R2. Title - Cumulative Update 12 for Microsoft Dynamics NAV 2013 R2 Build No. - 38053 Release Date - October, 2014 Local Version Included - AU, AT, BE, CH, DE, DK, ES, FI, FR, IS, IT, NA, NL, NO, NZ, SE, UK, RU Download Link Note: Implementing this cumulative update will require a database conversion unless you have already implemented update rollup 5.

NAV 2013 Upgrade Part III - Data Upgrading.

Hi all, As per agenda we need to discuss the data upgrade in NAV 2013. The process is similar to what used to be till NAV 2009 R2 but with some changes. Let's start the process. Remember -  1) You can only upgrade a database to NAV 2013 from NAV 2009 SP1 / R2 SQL Only. 2) The Synchronization of users with SQL Server is no more required.