- 5 minutes to read

Release Notes

Welcome to Nodinite Installation & Configuration

Successfully deploy Nodinite, the monitoring and logging platform for integration solutions. Whether you set up a new instance, update an existing v7 installation, migrate from v6, or explore a proof of concept, this hub sends you to the right guide.

Begin by planning your installation, review the prerequisites, and then follow the Installation Guide.

Understanding the Installation Journey

Nodinite v7 is installed in two phases. First, you register the Environment in the Nodinite Portal wizard, where you describe authentication, SQL Server, servers, ports, TLS, and agents. Then you download the generated package and run it with the CLI (Nodinite.Installer.Cli.exe) from an elevated PowerShell 7 prompt. Updates and the v6 to v7 migration reuse the same Portal and CLI pair.

flowchart TD Start(["fa:fa-flag Where do you start?"]) Start -->|"New installation"| Plan["fa:fa-clipboard-list Plan the solution"] Plan --> Prereq["fa:fa-clipboard-check Check the prerequisites"] Prereq --> Portal["fa:fa-person-to-portal Portal wizard
Steps 1 to 6"] Portal --> CLI["fa:fa-terminal Step 7: run the CLI
in elevated PowerShell 7"] CLI --> Agents["fa:fa-monitor-waveform Log Agents and
Monitoring Agents"] Agents --> Post["fa:fa-shield-halved Working with Nodinite
and post-installation"] Start -->|"Running v7"| Update["fa:fa-arrow-turn-up Update Nodinite v7"] Update -->|"Download the new package"| CLI Start -->|"Running v6"| Migrate["fa:fa-arrow-right-arrow-left Migrate from v6 to v7"] Migrate -->|"Register the Environment"| Portal Start -->|"Running v5"| V5["fa:fa-box-archive Plan the move with
Support or a Partner"] style Start fill:#2678BD style Portal fill:#9E59BB style CLI fill:#E47528 style Update fill:#E47528 style Migrate fill:#FFD525 style V5 fill:#FFD525 style Post fill:#93d16d

Diagram: the Nodinite v7 journey. Blue is the starting point, purple the Portal wizard steps, orange the CLI run that both new installations and updates use, yellow the legacy paths (v6 to v7 migration and v5), and green the finished installation after Log Agents, Monitoring Agents, and post-installation steps.

Choose Your Version

On Windows Server, every Nodinite Core Service (Web Client, Web API, Log API, Logging Service, Monitoring Service, and MCP Server) is its own IIS web site with its own port, set per Environment in the Portal Servers step. This makes HTTPS/TLS the standard transport for production. Container runtimes (Docker, Kubernetes, OpenShift, and Azure Container Apps) are coming; see Runtime Environments.

Key Features

  • Automated installation with Nodinite.Installer.Cli.exe, generated per Environment by the Portal
  • Modern technology stack - .NET 10 and ASP.NET Core
  • OAuth 2.0/OpenID Connect support for enterprise authentication, next to Windows Authentication
  • IIS-hosted Core Services and agents on Windows Server with TLS bound by certificate subject (hardening)
  • Multi-environment management from the Portal
  • Ongoing support and updates

Nodinite v6 (Legacy – No Longer Supported)

Important

Nodinite v6 and its Install and Update Tool are no longer supported. Existing v6 customers should upgrade to v7 for continued support, security updates, and new features.

Nodinite v5 and v4 (Historical Archive)

Important

Nodinite v5 has been out of support for many years. A move from v5 to v7 is technically possible, but plan it with Support or a certified Partner.

Main Resources

Installation & Configuration

Troubleshooting & Support

Runtime Environments and Docker (Experimental)

Windows Server with IIS is the production runtime today. The Portal also offers container runtimes for evaluation; the Docker Compose path suits POC scenarios where a team wants to try the Web Client experience and explore the Repository Model quickly.

Professional Services

About Nodinite Installation

Nodinite is installed as a dedicated instance for each customer or environment, ensuring:

  • Strict access control - Each instance has isolated user permissions
  • Data isolation - Complete separation between environments
  • Scalability - Deploy from single-server POCs to distributed enterprise installations
  • Flexibility - On-premise, cloud, or hybrid deployments

Architecture Options

Icon Deployment Type Description Best For
Single Server Core Services, agents, and SQL Server on one server POC, small environments, monitoring-only
Distributed Core Services on one server, SQL Server and agents on others Production, high availability, large scale
Cloud Azure, AWS, or other cloud platforms Hybrid scenarios, geographic distribution

Tip

Planning your architecture? See Planning Your Installation for topology, sizing, and SQL Server high availability.

Next Steps