topic hubofficial - Microsoftreviewed - checked by Opus

Business Central web server

The Business Central web server section covers deploying and configuring the web server components on IIS for on-premises installations. It answers questions about web server instances, navsettings.json settings, IIS features, SSL/HTTPS, Kerberos delegation, multiple instances with PowerShell, and tenant host names.

Path: Business Central on-premises > Deployment > Business Central web server · tier official · system none · narrative reviewed (checked by Opus)

Overview

The Business Central web server runs as an ASP.NET Core application on IIS and serves the web client. This section explains how to deploy those components, prepare IIS, create one or more web server instances, and secure and tune them.

Start with “Deploy the Web Server Components” for the overview of network topology, instance creation methods and security. Then use “Configuring Internet Information Services for Business Central” for required IIS features and ARR headers, and “Configuring Business Central Web Server instances” for navsettings.json settings. The remaining pages cover specific tasks: SSL, multiple instances through PowerShell, tenant host names, and delegation when the web server and server instance are on separate computers.

Key points

  • Web server components run as ASP.NET Core on IIS; IIS needs specific features such as ASP.NET and .NET Extensibility.
  • Application Request Routing header configuration, including X-Forwarded-Proto, is described for the IIS setup.
  • Instance settings live in navsettings.json (credential types, SSL/HTTPS, session timeout, authentication, portal embedding) and can be edited directly or with PowerShell cmdlets.
  • SSL setup involves obtaining a certificate, adding an HTTPS binding, and optionally redirecting HTTP to HTTPS.
  • Multiple instances are managed with New-NAVWebServerInstance, Set-NAVWebServerInstanceConfiguration, Get-NAVWebServerInstance and Remove-NAVWebServerInstance, deployed as RootSite or SubSite.
  • Multitenant deployments need a URL rewrite rule in web.config so the web server accepts tenant host names.
  • Delegation across separate computers uses Kerberos, constrained delegation, service principal names and Active Directory configuration, with steps differing for version 20 and version 21 and later.

Learn pages

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.

What Learn documents here 7 Learn pages