The following illustration shows the components of the Microsoft Dynamics NAV Web client environment.

You can deploy the components on one computer or on separate computers. For example, you can install the Microsoft Dynamics NAV Web Server components on one computer and the Microsoft Dynamics NAV Server and SQL Server database on another computer. The topology that you choose depends on the network resources and the infrastructure of the Microsoft Dynamics NAV components. The installation and configuration process is different for each scenario.

For information about the common deployment scenarios, see Deployment Scenarios for the Microsoft Dynamics NAV Web Client.

To deploy the Microsoft Dynamics NAV Web client, you install Microsoft Dynamics NAV Web Server components on a computer that is running Internet Information Services (IIS). When you install Microsoft Dynamics NAV Web Server components, a web server instance is added on IIS for the Microsoft Dynamics NAV Web client. The web server instance consists of a virtual directory and application. The following illustration shows the structure in Internet Information Services Manager.

The following table includes the default settings for each element of the website structure.

Website

Virtual directory

Web application

Setting	Value
Application pool	Microsoft Dynamics NAV 2013 R2 Web Client Application Pool
Application pool identity	ApplicationPoolIdentity
Physical path	%systemroot%\inetpub\wwwroot\DynamicsNAV71\WebClient Note This folder is a symbolic link that targets the %systemroot%\Program Files\Microsoft Dynamics NAV\71\Web Client folder.
Virtual path/Alias	/DynamicsNAV71/WebClient
Protocol	http
Authentication	Windows Authentication

For more information about how to install the Microsoft Dynamics NAV Web Server components and IIS, see How to: Install the Web Server Components for the Microsoft Dynamics NAV Web Client and How to: Install and Configure Internet Information Services for Microsoft Dynamics NAV Web Client.

Typically, you will deploy the Microsoft Dynamics NAV Web client in phases, which can influence the network topology and security settings that you deploy. For example, in the development phase, you develop, test, and fine-tune the application. In this phase, you might consider deploying the Microsoft Dynamics NAV Web client in a single-computer scenario. When you move to the production phase, you deploy the Microsoft Dynamics NAV Web client in the full network infrastructure.

User Authentication

Service Account for Microsoft Dynamics NAV Server and Microsoft Dynamics NAV Database Access

When you install Microsoft Dynamics NAV Server and Microsoft Dynamics NAV database components, you must identify an Active Directory account to provide credentials for the servers. By default, Microsoft Dynamics NAV 2013 R2 Setup runs Microsoft Dynamics NAV Server and the Microsoft Dynamics NAV database under the Network Service account, a predefined local account that is used by the service control manager.

Tip
We recommend that you create and use a domain user account for running Microsoft Dynamics NAV Server and accessing the Microsoft Dynamics NAV database. The Network Service account is considered less secure because it is a shared account that can be used by other unrelated network services.

For more information, see Provisioning the Microsoft Dynamics NAV Server Account.

Securing the Connection to Microsoft Dynamics NAV Web Client With SSL

Tasks

Concepts