In this scenario, you install the Microsoft Dynamics NAV Web Server components, Microsoft Dynamics NAV Server, and the SQL Server database components on the same computer.
 Tip |
|---|
| For a step-by-step example that describes how to deploy this scenario, see Walkthrough: Installing the Microsoft Dynamics NAV Web Server Components on a Single Computer. |
Deployment Tasks
To deploy the Microsoft Dynamics NAV Web client and Microsoft Dynamics NAV Tablet client in this scenario, complete the following tasks.
Pre-Installation Tasks
The following table includes tasks to perform before you install the Microsoft Dynamics NAV Web Server components.
| Task | Description | For more information, see | ||
|---|---|---|---|---|
Make sure that system requirements are met. | Verify that the computer has the required hardware and software installed. | |||
Install Internet Information Services 7.0 or Internet Information Services 8.0. | When you install the Microsoft Dynamics NAV Web Server components, Microsoft Dynamics NAV Setup creates a website for the Microsoft Dynamics NAV Web client on IIS. If IIS is already installed, then make sure that the required features are enabled.
| How to: Install and Configure Internet Information Services for Microsoft Dynamics NAV Web Client | ||
Determine the TCP port for the Microsoft Dynamics NAV Web client and allow communication on the port through Windows Firewall. | Microsoft Dynamics NAV Setup creates a website on IIS for the Microsoft Dynamics NAV Web client. During Setup, you will have to choose the port to use for the site. The default port that is used in Microsoft Dynamics NAV Setup is port 8080. If you are not sure of which port to use, then use the default port. If the computer is running Windows 7 or Windows 8 with Windows Firewall enabled, then you have to create an inbound rule that allows communication on the port. | How to: Create an Inbound Rule in Windows Firewall for the Port of Microsoft Dynamics NAV Web Client | ||
Set up the service account for Microsoft Dynamics NAV Server and the SQL Server database. | Optional. When you install Microsoft Dynamics NAV Server, you can specify a user account that will be used to log on to the Microsoft Dynamics NAV Server instance and Microsoft Dynamics NAV database. The default service account is Network Service. If you want to use Network Service, then no action is required for this task. | |||
Obtain and install an SSL certificate. | Optional. If you want to configure SSL on the connection to Microsoft Dynamics NAV Web client, then complete the following procedures:
| The following sections in the Walkthrough: Configuring Web Services to Use SSL (SOAP and OData) topic: |
Note Installation Tasks
The following table includes tasks for installing the Microsoft Dynamics NAV Web Server components.
| Task | Description | For more information, see |
|---|---|---|
Install Microsoft Dynamics NAV Web Server components, Microsoft Dynamics NAV Server, and Microsoft Dynamics NAV database components. | Run the Microsoft Dynamics NAV 2017 setup.exe file, choose the Custom installation option, and then choose the SQL Server Database Components, Server, and NAV Web Server Components options. |
Post-installation Tasks
The following table includes tasks that configure the Microsoft Dynamics NAV Web Server components after installation. These tasks are optional depending on your organizational and network requirements.
| Task | Description | For more information, see |
|---|---|---|
Configure Report Viewer. | To display reports, Microsoft Report Viewer must be configured on a website of the Microsoft Dynamics NAV Web client. Report Viewer includes an option that lets users save a report as a Microsoft Excel, Microsoft Word, or PDF file. By default, this option is disabled. You configure Microsoft Report Viewer in the web.config file for the Microsoft Dynamics NAV Web client website. | How to: Configure Microsoft Report Viewer for the Microsoft Dynamics NAV Web Client |
Change the user authentication method. | The Microsoft Dynamics NAV Web client supports the same authentication methods as the Microsoft Dynamics NAV Windows client, which include Windows, UserName, NavUserPassword, and AccessControlService. By default, the Microsoft Dynamics NAV Web client uses Windows authentication. | How to: Configure User Authentication for the Microsoft Dynamics NAV Web Client |
Secure the connection to the Microsoft Dynamics NAV Web client with SSL. | You can help secure Microsoft Dynamics NAV data that is transmitted over the Internet by enabling Secure Sockets Layer (SSL) on the connection to the Microsoft Dynamics NAV Web client. | How to: Configure SSL to Secure the Connection to Microsoft Dynamics NAV Web Client |
Change Microsoft Dynamics NAV settings of the Microsoft Dynamics NAV Web client. | There are several parameters in the web.config file for the website that is running Microsoft Dynamics NAV Web Server components that you can modify to change the behavior of the Microsoft Dynamics NAV Web client. Some of the more common parameters include the Microsoft Dynamics NAV Server instance, company, language, time zone, regional settings, session time out, and online Help URL. | Configuring Microsoft Dynamics NAV Web Client by Modifying the Web.config File |
Set up multiple Microsoft Dynamics NAV Web client applications on a website. | You can set up multiple web server instances for the Microsoft Dynamics NAV Web client on the existing website. The web server instances will use the same address (URL) except with an alias that specifies the specific application. | How to: Set Up Multiple Web Server Instances for the Microsoft Dynamics NAV Web Client |
Configure web browsers on devices. | The Microsoft Dynamics NAV Web client supports several different web browsers. To access the Microsoft Dynamics NAV Web client, the web browser must be enabled on a device with cookies and JavaScript. | Configuring the Web Browser for the Microsoft Dynamics NAV Web Client |