- 0 minutes to read

Release Notes

Plan your Nodinite installation

Start your Nodinite journey for success! This page guides you to 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:

✅ Review all prerequisites for a successful Nodinite installation
✅ Plan infrastructure, licensing, and backup for scalability and compliance
✅ Align your team and business processes for maximum value

Ready to get started?
Nodinite v7 - Begin with the Install Nodinite v7 guide.
Nodinite v6 - Begin with the Install Nodinite v6 guide.

This page provides valuable information to help you get the best experience with our support and maintenance tool for system integration solutions, Nodinite.

Where do I find the latest information?

Access the latest information for Nodinite, including system requirements and product support information, from our Documentation page and our Portal. These links are easy to access and are available for all users from within the self-service web-based interface we call Nodinite Web Client.

Nodinite Release Notes

Review the prerequisites

Nodinite is a platform from the ground up designed for enterprise scalability with many different services and dependencies. You will find each of these prerequisite pages in the Getting started sections. Depending on your needs and demands (and wallet), there are different prerequisites for different target environments.

graph LR subgraph "SQL Server" roConfigDatabase(fal:fa-database Configuration database) --- |Linked Server| roLogDatabase(fal:fa-database fal:fa-database fal:fa-database Log databases) end subgraph "Application Server" roLogAPI(fal:fa-cloud-arrow-down Log API) --- roConfigDatabase roWebClient(fal:fa-globe Web Client) ---roWebAPI(fal:fa-cloud-sun Web API) roWebAPI --- roConfigDatabase roLoggingService(fal:fa-hard-drive Logging Service) --- roWebAPI roLoggingService --- roConfigDatabase roMonitoringService(fal:fa-watch-fitness Monitoring Service) --- roConfigDatabase roMonitoringService --- roWebAPI end

Architectural overview of the Core Services of Nodinite, customers with Logging, typically have large amounts of data and run SQL Server on dedicated servers.

Understanding your data and message processing requirements

It is essential to be clear about your processing requirements and understand what you want Nodinite to do for you and your business. With Nodinite, your business gets a self-service tool where they can manage Logging and Monitoring from specific business-critical workflows to technical nitty-gritty 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/cloud), data volumes, access control, and lifecycle management. Use these tables as checklists to ensure comprehensive planning.

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 retention period (e.g., 14-90 days). Log Databases
Important GDPR compliance Identify PII data in messages. Use Repository Model for data classification and retention policies. Repository Model
Important Historical data strategy Plan multiple Log Databases for historical data. Keep active DB < 50 GB for optimal performance. Log Databases
Good to Know Growth projections Estimate 6-12 month growth. Business expansion may increase message volumes significantly. Planning your Nodinite Installation

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

Security and Access Control

Priority Planning Item Details & Guidance Further Reading
Vital Domain integration Determine if servers must be domain-joined for Windows Authentication and user access. Access Management
Vital Service accounts Create dedicated service accounts for Nodinite services with appropriate SQL and IIS permissions. Prerequisites
Vital User roles Define who needs Administrator vs Contributor vs 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 Alert recipients Identify who receives alerts (email, Teams, SMS). Map alert types to responsible teams. Web API
Good to Know HTTPS/TLS setup Plan certificate deployment for encrypted communication. Recommended for production. Hardening

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. Core Services
Vital Server provisioning Order VMs/hardware: Application server (IIS, Nodinite), SQL Server, dedicated disk volumes. Prerequisites
Vital Network planning Configure firewall rules for Web Client, Web API, Log API ports. Plan DMZ if internet-facing. Hardening
Important SQL Server topology Standalone, AlwaysOn Availability Groups, or mirroring? Nodinite supports AlwaysOn. AlwaysOn
Important Agent deployment Identify which servers need Log Agents and Monitor Agents installed. Logging, Monitoring
Good to Know Load distribution Nodinite does not support NLB. Use SQL HA for reliability instead of app server clustering. Prerequisites

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 (Config + Log databases). Retention >= 4 days for long weekends. Test restores! InstallUpdate
Vital System owner Designate responsible person/team for production environment. Manages license renewals (twice/year). Partners
Important Update procedures Define maintenance windows. Who applies updates? How often? Nodinite releases regularly. UpdateNodinite
Important Knowledgebase Build internal documentation using Nodinite Articles for troubleshooting common issues. Articles
Important Training plan Allocate budget/time for webinars, self-study, POC testing. Stay current with new features. POC, Partners
Good to Know Newsletter subscription Subscribe via 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 a subscription-based software, and you can buy it directly from one of our Partners or us. However, depending on your need, different options may be better suitable, 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

graph LR subgraph "Database Server" roConfigDatabase(fal:fa-database SQL Server) end subgraph "Application Server" roWebClient(fal:fa-code-commit Nodinite) --- roConfigDatabase end

Nodinite should be installed on dedicated virtual machines with databases on separate SQL Server instances. Use these hardware and configuration recommendations as a starting point—adjust based on your specific workload.

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 same VM. Depends on workload.
RAM (App Server) 8 GB 16 GB Vital For servers running Nodinite Core Services.
RAM (SQL + App) 16 GB 32+ GB Vital If SQL Server and Nodinite are co-hosted on 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.
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 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. Do not use NLB or failover clustering for app tier.
SQL Server Clustered/AlwaysOn Vital Use SQL HA (AlwaysOn, Mirroring, Clustering) per your policy. AlwaysOn 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 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 overwrite setting to all servers running Nodinite components.

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

Tip

SQL Server Always On Availability Groups is supported by Nodinite.
If you intend to use SQL Server Always On Availability Groups, read the AlwaysOn user guide for configuration details.

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 Step

2. Prerequisites - Review all system requirements before installation

Install Nodinite Overview
Update Nodinite
POC Guide
Nodinite Partners
Download packages - Access v6 installation packages