- 10 minutes to read

Release Notes

Plan your Nodinite installation

Start your Nodinite journey for success! This page helps you align your team and infrastructure for a smooth, scalable, and secure installation. Discover what you need to know before deployment and ensure your business maximizes the value of Nodinite.

On this page, you will learn to

✅ Understand the v7 architecture and choose a topology
✅ Plan infrastructure, licensing, and backup for scalability and compliance
✅ Align your team and business processes for maximum value

Note

This page covers planning. Detailed system requirements are on the next page: 2. Prerequisites. Ready to get started? Begin with the Install Nodinite v7 guide.

Where do I find the latest information?

Find the latest information for Nodinite, including system requirements and product support information, on our Documentation page and in the Nodinite Portal. Both are linked from the Nodinite Web Client, the self-service web-based interface.

Nodinite Release Notes

Understanding the Nodinite Architecture

Nodinite is designed for enterprise scalability. Understanding the component topology helps you plan server roles, network access, and SQL Server sizing before installation. On Windows Server, each Core Service is its own IIS web site with its own port, and the Core Services run on exactly one server per environment (Step 4: Servers). Agents can run on that server or on others.

flowchart LR subgraph Agents["Nodinite Agent Servers"] roMA["fa:fa-monitor-waveform Monitoring Agents"] roLA["fa:fa-box-archive Log Agents"] end subgraph Core["Nodinite Core Services Server - IIS on Windows Server"] roWebClient["fa:fa-globe Web Client"] roWebAPI["fa:fa-cloud-sun Web API"] roLogAPI["fa:fa-cloud-arrow-down Log API"] roLS["fa:fa-hard-drive Logging Service"] roMS["fa:fa-watch-fitness Monitoring Service"] roMCP["fa:fa-plug MCP Server"] end subgraph SQL["SQL Server"] roConfig["fa:fa-database Configuration Database"] roLogDB["fa:fa-database Log Databases"] end roWebClient --- roWebAPI roWebClient --- roMCP roWebAPI --- roConfig roLogAPI --- roConfig roMCP --- roConfig roLS --- roConfig roLS -->|"Creates the first one on first start"| roLogDB roMS --- roConfig roMS -->|"Monitor checks"| roMA roLA -->|"Log Events"| roLogAPI roConfig ---|"Linked Server"| roLogDB style roMA fill:#E47528 style roLA fill:#E47528 style roWebClient fill:#93d16d style roWebAPI fill:#93d16d style roLogAPI fill:#93d16d style roLS fill:#93d16d style roMS fill:#93d16d style roMCP fill:#93d16d style roConfig fill:#2678BD style roLogDB fill:#2678BD

Diagram: green nodes are the Core Services (Web Client, Web API, Log API, Logging Service, Monitoring Service, and MCP Server); blue nodes are the Configuration Database and the Log Databases, joined by a Linked Server; orange nodes are the Monitoring Agents and Log Agents. The installer creates the Configuration Database; the Logging Service creates the first Log Database. Customers with heavy Logging typically run SQL Server on dedicated servers.

The Core Services Overview explains each component's role; the Prerequisites page maps the ports between them.

Understanding your data and message processing requirements

Be clear about your processing requirements and what you want Nodinite to do for you and your business. With Nodinite, your business gets a self-service tool to manage Logging and Monitoring, from specific business-critical workflows to technical details, all according to your well-defined policy. Nodinite has role-based security.

About your run-time environment

When planning your Nodinite environment, consider infrastructure design (on-premise or cloud), data volumes, access control, and lifecycle management. Use these tables as checklists.

Data Volume and Retention Planning

Priority Planning Item Details & Guidance Further Reading
Vital Daily message volumes Estimate messages/day to process and log. Affects SQL sizing and performance. Log Databases
Vital Retention requirements ~1 million transactions/day = 1 GB compressed. Calculate storage for the retention period (e.g., 14-90 days). Log Databases
Important GDPR compliance Identify PII data in messages. Use the Repository Model for data classification and retention policies. Repository Model
Important Historical data strategy Plan multiple Log Databases for historical data. Keep the active database < 50 GB for optimal performance. Log Databases
Good to Know Growth projections Estimate 6-12 month growth. Business expansion may increase message volumes significantly. SQL Server Options

Volume planning ensures adequate storage and performance for your logging needs.

Security and Access Control

Priority Planning Item Details & Guidance Further Reading
Vital Authentication model Windows Authentication (domain integration: servers and users in the domain) or OAuth 2.0 / OIDC with an identity provider such as Microsoft Entra ID. You choose it in the Portal. Step 2: Auth, OpenID/OAuth
Vital Service accounts Create dedicated service accounts with the Logon as a Service right, SQL rights, and, for the Monitoring Service, DCOM Local Activation. v7 supports gMSA for automatic password rotation. You set the identities per service in the Portal. Logon as a Service, gMSA accounts, Monitoring Service rights, Step 4: Servers
Vital User roles Define who needs Administrator, Contributor, or read-only access. Plan role-based security. Access Management, Roles
Important Self-service access Enable business users to view logs, resubmit messages, and acknowledge alerts independently. Access Management
Important Alarm recipients Identify who receives alarms and through which of the four built-in Alarm Plugins (E-mail, E-mail with options, Event Log, HTTP Webhook). Map alarm types to responsible teams. Alarm Plugins, Monitor Views
Important HTTPS/TLS setup Plan the certificate and the host name for encrypted communication. The installer finds the certificate by subject and binds it at every install and update. Core host Configuration, Hardening
Good to Know SQL Server encryption Plan encrypted SQL connections for production. Includes certificate trust and connection string options. SQL Server Options, Connection Strings
Good to Know SPNs If using custom domain service accounts, register Service Principal Names for Kerberos. SPN

Security planning protects your integration data and defines clear responsibilities.

Infrastructure and Architecture

Priority Planning Item Details & Guidance Further Reading
Vital Hosting strategy On-premise, Azure, AWS, or hybrid? Consider latency, costs, and compliance requirements. Windows Server with IIS is the production runtime; container runtimes are coming. Runtime Environments, Core Services
Vital Server provisioning Order VMs/hardware: one Core Services server (IIS, Nodinite), SQL Server, agent servers as needed, and dedicated disk volumes. Prerequisites, SQL Server Options
Vital Network planning Plan one port per Core Service and agent, and the firewall rule for every hop: browsers, agents, SQL Server, domain controllers, mail server. Plan a DMZ if internet-facing. Network and Firewall Overview, Hardening
Important SQL Server topology Standalone, AlwaysOn Availability Groups, or mirroring? Nodinite supports AlwaysOn. AlwaysOn, SQL Server Options
Important Agent deployment Identify which servers need Log Agents and Monitoring Agents installed. You select them in the Portal. Step 5: Agents, Logging, Monitoring
Good to Know Load distribution Nodinite does not support NLB. Use SQL HA for reliability instead of app server clustering. Cluster and High Availability

Infrastructure choices impact performance, reliability, and total cost of ownership.

Lifecycle Management and Governance

Priority Planning Item Details & Guidance Further Reading
Vital Backup strategy Daily SQL backups of the Configuration Database and the Log Databases. Retention >= 4 days for long weekends. Test restores! The CLI asks you to confirm a verified backup before it changes the Configuration Database. Configuration Database, Backup prompt
Vital System owner Designate a responsible person/team for the production environment. Manages license renewals (twice/year) and access to the Environment in the Portal. Nodinite Portal, Partners
Important Update procedures Define maintenance windows. Who applies updates? How often? Nodinite releases regularly. Updating Nodinite v7
Important Knowledgebase Build internal documentation using Nodinite Articles for troubleshooting common issues. Articles
Important Training plan Allocate budget/time for webinars, self-study, and POC testing. Stay current with new features. POC, Partners
Good to Know Newsletter subscription Subscribe via the Support Portal for release notes and best practices. Release Notes

Proper lifecycle management ensures long-term success and minimizes downtime.

Buying Licenses for Nodinite

Nodinite is subscription-based software, and you can buy it directly from one of our Partners or from us. Depending on your need, different options may suit you better, for example:

Managed Services

Most partners offer professional services:

  • Education
  • Hands-on help
  • Updates
  • Hosting - Some partners sell Nodinite as a service (SaaS)

Contact us at info@nodinite.com for guidance and recommendations.

How to become a Partner

If you want to become a partner, contact us at contact@nodinite.com or visit our Become a Partner page.

Recommendations

Install Nodinite on dedicated virtual machines, with the databases on separate SQL Server instances. Use these hardware and configuration recommendations as a starting point and adjust them to your workload.

flowchart TD Q{"fa:fa-scale-balanced Production or
high log volumes?"} Q -->|"No: POC, DEV, or TEST"| Single["fa:fa-server Single server
Core Services, agents, and SQL Server"] Q -->|"Yes"| Dist["fa:fa-network-wired Distributed"] Dist --> CoreHost["fa:fa-server One Core Services server
no NLB, no failover cluster"] Dist --> SQLHA["fa:fa-database Dedicated SQL Server
with SQL HA such as Always On"] Dist --> AgentHosts["fa:fa-monitor-waveform Agent servers near
the systems they watch"] style Q fill:#2678BD style Single fill:#FFD525 style Dist fill:#93d16d style CoreHost fill:#93d16d style SQLHA fill:#93d16d style AgentHosts fill:#93d16d

Diagram: choosing a topology. Yellow marks the single-server layout that fits only POC, DEV, and TEST; green marks the distributed production layout with one Core Services server, a dedicated SQL Server with AlwaysOn or another SQL HA option, and Monitoring Agents or Log Agents on the servers they watch.

Note

Excessive logging should never block business-critical solutions. Isolate Nodinite on dedicated resources.

CPU and Memory Requirements

Component Minimum Recommended Priority Notes
CPU (x64) 2 cores 4+ cores Vital Nodinite is multi-threaded. More cores improve performance. No licensing impact.
CPU (co-hosted) 4 cores 8+ cores Vital If SQL + IIS + Nodinite share the same VM. Depends on workload.
RAM (App Server) 8 GB 16 GB Vital For the server running the Nodinite Core Services.
RAM (SQL + App) 16 GB 32+ GB Vital If SQL Server and Nodinite are co-hosted on the same Windows Server.
Licensing check N/A Verify Important BizTalk, SQL may require additional licenses depending on setup.

CPU and memory allocations directly impact message processing throughput and UI responsiveness.

Disk Storage and Performance

Volume Type Minimum Recommended Priority Notes
Windows Page File 20 GB 2.5x RAM Vital Dedicated volume. Calculate: Physical RAM × 2.5 for swap space.
SQL Disk I/O 100 MB/s 300+ MB/s R/W Vital Use SSD. Azure: Premium P30+ for DATA/LOG, P20+ for OS.
System Volume 50 GB 100 GB SSD Important OS and Nodinite binaries. Separate from SQL data.
SQL Data Volume 50 GB 50+ GB per DB Vital Each NodiniteLog_* < 50 GB. Use multiple Log Databases for large volumes.
Backup Volume Variable Formula-based Vital Formula: (# of DBs) × (DB size) × (retention days). Example: 3 DBs × 60 GB × 3 days = 540 GB.
Volume separation Per environment Dedicated disks Important Isolate DEV/TEST/PROD to prevent one environment filling disk and affecting others.

Disk performance is critical—30 GB/month typical growth. Monitor usage actively to prevent outages.

SQL Server Configuration

Configuration Setting Priority Notes
Initial DB size 50 GB Vital Pre-allocate to avoid autogrowth pauses during peak loads. Monitor growth actively.
Typical growth 30 GB/month Vital Based on average workloads. Retention usually 14 days. Adjust for your volumes.
Recovery mode Simple (default) Important Default for Nodinite databases. Full recovery supported but increases log disk usage. New Log Databases follow the LogDatabaseRecovery System Parameter.
Max DB size < 50 GB per DB Important Large databases impact performance. Use multiple Log Databases for historical data.
AlwaysOn support Supported Good to Know Nodinite fully supports SQL Server AlwaysOn Availability Groups. See the AlwaysOn guide.
Fault tolerance Per policy Vital SQL Server must be highly available. Follow your organization's HA policy and budget.

SQL Server hosts all Nodinite data—proper sizing and monitoring prevent the #1 cause of outages (disk full).

Cluster and High Availability

Component Configuration Priority Notes
Application Server No NLB/Cluster Vital Nodinite has no distributed cache, and the Core Services install on one server per environment. Do not use NLB or failover clustering for the app tier.
SQL Server Clustered/AlwaysOn Vital Use SQL HA (AlwaysOn, Mirroring, Clustering) per your policy. AlwaysOn is fully supported.
Network load balancing Not supported Vital Rely on SQL Server reliability, not app server redundancy.

Nodinite depends on SQL Server for persistence—invest in SQL HA, not app server clustering.

Event Log Configuration

Component Setting Priority Notes
Windows Event Logs Overwrite mode Vital Nodinite Core Services, Log Agents, and Monitoring Agents log errors to the Event Log.
Log size limit Avoid fixed size Important Use automatic overwrite (oldest events). Fixed-size logs can fill and block logging.
Monitoring scope All Nodinite servers Important Apply the overwrite setting to all servers running Nodinite components.

Event logs are the last-resort diagnostic tool—prevent them from filling and blocking operations.

Training

You can buy training from one of our certified Partners or contact us at info@nodinite.com for guidance and recommendations. Review our POC guide for proof-of-concept planning.

Next Steps

Service Accounts

  • Logon as a Service - Minimum rights required for all Nodinite services
  • gMSA accounts - Automatic password rotation
  • SPN - Service Principal Names for Kerberos authentication
  • Hardening - TLS, SQL encryption, certificate management

SQL Server

  • SQL Server Options - Supported versions, editions, collation, performance, and security
  • Connection Strings - Encryption, certificate trust, and AlwaysOn configuration
  • AlwaysOn - High availability with SQL Server Always On Availability Groups