- 3 minutes to read

Prerequisites for the Nodinite Web Client

This page describes the prerequisites for successfully installing and running the Web Client.

The Web Client is a Web Application hosted within IIS and is installed as part of the Core Services package.

graph LR subgraph "Consumers" roBrowser[fab:fa-chrome Chrome
fab:fa-firefox Firefox
fab:fa-internet-explorer Internet Explorer
fab:fa-edge edge
fab:fa-safari Safari] end subgraph "Web Server" roWebClient(fal:fa-globe Web Client) ---roWebAPI(fal:fa-cloud-sun Web API) roBrowser ---roWebClient end
Verified Topic
Supported Client Browser
Windows rights
Firewall

Use the checklist above to verify that you have performed all steps required to get Nodinite flying

Supported Client Browser

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
Chrome 48 Latest Recommended choice
Internet Explorer* 11 About Lifecycle We do not recommend the usage of IE
edge 12 Latest
Safari 5 Latest
Firefox 37 Latest

/* Internet Explorer 9 and 10 was supported with Nodinite version 1-4. Nodinite 5 and later, 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

What Windows rights does the Web Client require?

Nodinite is locked down by default and only members of a Role can logon.

Technically speaking, when you install Nodinite, the install and update tool configures the Web Client with a dedicated named IIS App Pool. This IIS App Pool is set to run with ASP.NET Impersonation, review the IIS Authentication settings user guide for additional information. This means that further calls to the Web API retain the information about the end-user.

What Firewall settings are required for the Web Client

The Web Client requires both inbound and outbound ports to be opened for communication. Since Nodinite is highly configurable, the actual ports in use may differ from what's being exampled here.

graph LR subgraph "PowerBI, Excel, QlikView" roReport[fal:fa-user-chart Custom Reports] end subgraph "Web Server" roWebAPI(fal:fa-cloud-sun Web API) roWebClient(fal:fa-globe Web Client) -->|80,443,...| roWebAPI roReport -.-|80,443,...| roWebAPI roReport -.-|80,443,...| roWebClient end
  1. Inbound communication
    • HTTP and/or
    • HTTPS
  2. Outbound communication with the Web API
    • HTTP and/or
    • HTTPS

1. Inbound communication

Port Name Inbound Outbound TCP UDP Comment
80 HTTP default for HTTP)
443 HTTPS default for HTTPS)
  • 1-65535 - It all depends on what port you have assigned using 'Edit Bindings' for the Web Site hosting the Web Client
    • If you're going to host Nodinite on non-default ports, Please contact our support for guidance at support@nodinite.com

2. Outbound communication with the Web API

All communication with the underlying databases etc. is made using the Web API.

Port Name Inbound Outbound TCP UDP Comment
80 HTTP default for HTTP)
443 HTTPS default for HTTPS)
  • 1-65535 - It all depends on what port you have assigned using 'Edit Bindings' for the Web Site hosting the Web Client
    • If you're going to host Nodinite on non-default ports, Please contact our support for guidance at support@nodinite.com

Frequently asked questions

Common problems and FAQ for the Web Client can be found in the troubleshooting page.

Can I secure the Web Client?

Yes, the Web Client supports the usage of SSL Certificates. Add your certificate to IIS and configure the Web Client to only allow calls using HTTPS.

Review the IIS Hardening user guide for more information

What SQL Rights does the Web Client require?

The Web Client does not access any of the databases directly and hence does not need any rights assigned within SQL Server.


Next Step

Install Nodinite