Prerequisites for the Web Client
This page describes the prerequisites for successfully installing and running the Web Client.
fab:fa-internet-explorer Internet Explorer
fab:fa-safari Safari] end subgraph Web Server roWebClient(fal:fa-globe Web Client) ---roWebAPI(fal:fa-cloud-sun Web API) roBrowser ---roWebClient end
Use the checklist above to verify that you have performed all steps required to get Nodinite flying
Nodinite requires a modern HTML-5 enabled browser which most are to some extent. HTML is simply speaking just a collection of tags and attributes that are used to markup a document to be processed by the browser. Unfortunately the different browsers available on the market are not processing content equally and you will get a different look and feel using Nodinite depending on your choice.
|Browser||Minimum Supported Version||Recommended version||Note|
|Internet Explorer*||11||About Lifecycle|
/* Internet Explorer 9 and 10 was supported with Nodinite version 1-4. Nodinite 5 requires a modern HTML-5 browser.
We develop and test Nodinite using Chrome to give you the best and richest experience and we strongly recommend that you use this great browser too
The Web Client is involved in SQL Server related operations and Nodinite uses the Windows Service Microsoft Distributed Transaction Coordinator (DTC) that is responsible for coordinating transactions that span multiple resource managers. We have written a dedicated tutorial for Nodinite with our best practices for how to install and configure the DTC Windows Service.
You must configure the DTC as documented otherwise Nodinite will not be able to function
When you install Nodinite using the install and update tool the Web Client is assigned an IIS App Pool. This IIS App Pool is set to run with ASP.NET Impersonation and all consumers of the Web Client will be impersonated to a dedicated Windows Service account.
If the impersonated service account for IIS App Pool is not local administrator then the Windows Domain account must be added to the local 'IIS_IUSRS' group. The account used must also be assigned certain SQL Rights, see next paragraph.
The Web Client accesses the databases using the impersonated configured for the Web API and must have the following SQL rights assigned:
- Configuration Database
- Grant Execute rights on all existing and future stored procedures:
Replace [Domain\user] with the Windows account being used for the Web API
GRANT EXECUTE TO [Domain\user]
- IMLog* (can be multiple )
Note: db_ddladmin is required in order for the service account to have proper rights to read statistics. Without this permission performance may be degraded, especially true for remote servers (linked servers). Read more here. Contact our support if you have any questions about this.
The Web Client requires both inbound and outbound ports to be opened. Since Nodinite is highly configurable, the actual ports in use may differ from what's being exampled here.
The Web Client requires both inbound and outbound ports to be open. Depending on your environment different ports may be used. On a high level the following services must be allowed:
- REST - Inbound communication typically HTTP and HTTPS
- Configuration Database - ports used to communicate with SQL Server
- 80 - HTTP
- 443 - HTTPS
- 1-65535 - It all depends on what port you have assigned using 'Edit Bindings' for the Web Site hosting the Web Client
- If your going to host Nodinite on non default ports, Please contact our support for guidance at firstname.lastname@example.org
The Web Client does not access any databases and does not need any explicit rights. All communication with the underlying databases are performed using the Web API. You can read more about SQL rights for the Web API in the 'What SQL Rights does the Web API require?' section.