How to Install Nodinite v7 for a Proof of Concept (POC)
Get your Nodinite v7 Proof of Concept up and running quickly with this streamlined checklist. This guide provides everything you need for a successful POC evaluation:
- ✅ Fast-track setup - Clear prerequisites and step-by-step installation checklist
- ✅ Modern architecture - PowerShell 7 automation, OAuth 2.0 support, optional HTTPS hardening
- ✅ Proven scenarios - Recommended use cases to demonstrate Nodinite value
- ✅ Post-installation - Agent configuration, alerting setup, and security best practices
Tip
New to Nodinite? This quick-start guide gives you the essential steps for a POC. For detailed explanations, architecture diagrams, and troubleshooting, see Install Nodinite v7.
Free e-learning: Sign up at nodinite.com/learn to accelerate your Nodinite expertise.
What Should Your POC Prove?
Define clear success criteria for your POC. We recommend proving Nodinite value through at least three scenarios:
- Simple scenario - Managed file transfer or single-system integration
- Moderate complexity - Request-response with multiple systems and message transformations
- Advanced scenario - Correlated events, message splits, multiple receivers, business user self-service
Example POC goals:
- Reduce troubleshooting time by 70% with centralized logging
- Enable business users to track order status without IT involvement
- Detect and alert on integration failures within 60 seconds
Understanding Nodinite v7 Architecture
Before starting your POC, understand how Nodinite v7 components work together:
(User Interface)"] WebAPI[" Web API
(Business Logic)"] LogAPI[" Log API
(Event Ingestion)"] LogSvc[" Logging Service
(Data Processing)"] MonSvc[" Monitoring Service
(Health Checks)"] end subgraph "SQL Server" ConfigDB[" Configuration DB
(Metadata)"] LogDB[" Log Databases
(Transactional Data)"] end subgraph "Monitoring Targets" Services[" Services"] Queues[" Queues"] APIs[" APIs"] end BizTalk -->|Log Events| LogAPI Boomi -->|Log Events| LogAPI MuleSoft -->|Log Events| LogAPI Custom -->|Log Events| LogAPI LogAPI --> LogSvc LogSvc --> LogDB LogSvc --> ConfigDB WebClient --> WebAPI WebAPI --> ConfigDB WebAPI --> LogDB MonSvc -->|Monitor| Services MonSvc -->|Monitor| Queues MonSvc -->|Monitor| APIs MonSvc --> ConfigDB style WebClient fill:#e1f5ff style LogAPI fill:#ffe1e1 style ConfigDB fill:#f0e1ff style LogDB fill:#f0e1ff
Nodinite v7 collects logs from integration platforms, monitors system health, and provides a unified web interface for operations and business users.
Key Components
| Component | Purpose | POC Relevance |
|---|---|---|
| Web Client | Browser-based UI for log search, monitoring, and administration | Your users' primary interface |
| Web API | REST API for business logic and data access | Backend for Web Client |
| Log API | Receives log events from agents and custom integrations | Ingestion endpoint for all logging |
| Logging Service | Processes and stores log events in databases | Runs as Windows service |
| Monitoring Service | Executes health checks on monitored resources | Runs as Windows service |
| Configuration Database | Stores metadata, users, monitors, alert rules | Single SQL database |
| Log Databases | Stores transactional log events (high volume) | One or more SQL databases |
POC Prerequisites Checklist
Complete these prerequisites before registering your environment in the Nodinite Portal:
Infrastructure Requirements
| # | Requirement | Specification | Documentation |
|---|---|---|---|
| 1 | Windows Server | Windows Server 2019+ (2022 recommended) 100GB system disk, 16GB RAM minimum Domain-joined (recommended for OAuth) |
Planning your Nodinite Installation |
| 2 | SQL Server | SQL Server 2017+ (2019/2022 recommended) Standard, Enterprise, or Express edition (Express sufficient for POC) Note: Express has 10GB database size limit |
SQL Server Options |
| 3 | PowerShell 7 | Latest version installed on application server Execution policy set to Unrestricted or ByPass (temporarily) |
PowerShell 7 Download |
| 4 | .NET Runtimes | .NET 9.0 Runtime + ASP.NET Core 9.0 Hosting Bundle .NET Framework 4.8 (Windows Server 2019 and earlier) |
.NET 9.0 Download |
| 5 | IIS | Windows Features installed (see below) | IIS Windows Features |
| 6 | DacFx | SQL Server Data-Tier Application Framework (latest) | DacFx Download |
| 7 | SSMS | SQL Server Management Studio (optional but recommended) | SSMS Download |
Service Account Requirements
| # | Requirement | Details | Documentation |
|---|---|---|---|
| 8 | Service Account(s) | Windows account(s) for Nodinite services Option A: Single account (simpler POC) Option B: Separate accounts per service (least privilege) Option C: Group Managed Service Account (gMSA) - recommended for production |
Planning your Nodinite Installation Secret Management |
| 9 | Local Administrator | Service account must be local admin on application server Note: gMSA accounts automatically granted necessary permissions |
Local Accounts |
| 10 | SQL Sysadmin | Service account must be sysadmin on SQL Server (Required for installation; can be reduced post-install) Tip: Use Secret Management to securely store SQL credentials |
DatabaseMaintenance |
| 11 | Password Policy | Set password never expires for service accounts Note: Not required for gMSA accounts (password managed automatically) |
How to set Logon as a Service right |
| 12 | Logon as Service | Grant Log on as a service right to service account Note: gMSA accounts automatically granted this right |
How to set Logon as a Service right |
SQL Server Configuration
| # | Task | Details | Documentation |
|---|---|---|---|
| 13 | Linked Server | Create linked server pointing to localhost or named instance Test with: SELECT * FROM [LinkedServerName].master.sys.databases |
Linked Servers |
| 14 | MSDTC | Configure Distributed Transaction Coordinator Enable Network DTC Access, Allow Inbound/Outbound |
MSDTC Configuration |
| 15 | Firewall | Open SQL Server port (default 1433) if using remote SQL | SQL Server Firewall |
IIS Configuration
| # | Task | Details | Documentation |
|---|---|---|---|
| 16 | IIS Windows Features | Install required features: • Windows Authentication • ASP.NET Core Module V2 (.NET 9) • ASP.NET 4.x (.NET Framework 4.8) • URL Rewrite Module (for HTTPS redirect) |
IIS Windows Features IIS Prerequisites |
| 17 | Application Pools | Default App Pool settings sufficient for POC Nodinite installer creates app pools automatically |
Install Nodinite v7 |
Security & HTTPS (Optional for POC)
Note
HTTPS is optional for POC but recommended if evaluating OAuth 2.0 or deploying on a network-accessible server.
| # | Task | Details | Documentation |
|---|---|---|---|
| 18 | SSL/TLS Certificate | Obtain certificate matching DNS name • Production: Commercial CA or Let's Encrypt • POC: Self-signed certificate acceptable |
Hardening Guide |
| 19 | DNS Record | Create A record: nodinite-poc.yourdomain.com → Server IP |
Hardening Guide |
| 20 | OAuth 2.0 / OIDC | Optional: Configure Azure AD / Entra ID for modern auth Requires HTTPS |
Install Nodinite v7 - OpenID |
Installation Steps
Step 1: Register Environment in Portal
- Log in to Nodinite Portal
- Navigate to your Customer → Environments tab
- Click Add Environment → Install Fresh Nodinite 7
- Configure environment settings (see Install Nodinite v7 for detailed field explanations):
Required Configuration Tabs:
| Tab | Key Settings | Notes |
|---|---|---|
| General | Environment name, server hostname | Use descriptive name like "POC-Production" |
| Database | SQL Server instance, database names, service account | Use same account for POC simplicity |
| Authentication | Windows Authentication (default) or OAuth 2.0 | OAuth requires HTTPS |
| TLS | Optional: HTTPS configuration | Configure if using OAuth or testing security |
| Agents | Select Log Agents and Monitor Agents to deploy | Choose based on POC scenarios |
Save and Download:
- Save environment configuration
- Download installation package (ZIP file)
Step 2: Run Installation Script
- Extract downloaded ZIP to temporary location (e.g.,
C:\Temp\NodiniteInstall\) - Unblock files:
dir -r | unblock-file - Open PowerShell 7 as Administrator
- Navigate to extracted folder
- Run:
.\Nodinite7-<ENVIRONMENTNAME>-Installation.ps1 - Enter passwords when prompted (script runs interactively)
Important
Use PowerShell 7, not Windows PowerShell 5.1. Verify version:
$PSVersionTable.PSVersion
Tip
Installation typically takes 5-15 minutes. For detailed troubleshooting and advanced options, see Install Nodinite v7.
What the script does:
- Creates SQL databases (Configuration Database + Log Databases)
- Deploys IIS applications (Web Client, Web API, Log API)
- Installs Windows services (Logging Service, Monitoring Service)
- Deploys selected Log Agents and Monitor Agents
- Configures service accounts and application pools
- Applies database migrations
Step 3: Verify Installation
Check Windows Services:
Get-Service | Where-Object { $_.DisplayName -like "*Nodinite*" }Expected services (should be Running):
- Nodinite Logging Service
- Nodinite Monitoring Service
Check IIS Sites:
Open IIS Manager → Verify applications under Default Web Site:
- NodiniteWebClient
- NodiniteWebAPI
- NodiniteLogAPI
Access Web Client:
Open browser → Navigate to:
http://localhost/NodiniteWebClient/- Login with Windows credentials (if Windows Auth)
- Or OAuth credentials (if configured)
Verify Database Creation:
-- In SQL Server Management Studio SELECT name FROM sys.databases WHERE name LIKE 'Nodinite%'Expected databases:
- NodiniteConfig (or your custom name)
- NodiniteLog (or your custom name)
Configure Your POC Scenarios
Log Agent Configuration
Deploy and configure Log Agents based on your POC scenarios:
| Integration Platform | Log Agent | Configuration Guide |
|---|---|---|
| Microsoft BizTalk Server | BizTalk Logging Agent | BizTalk Server Logging |
| Boomi | Boomi Logging Agent | Boomi Logging |
| MuleSoft | MuleSoft Logging Agent | MuleSoft Logging |
| Azure Logic Apps | Logic Apps Logging Agent | Azure Logic Apps Logging |
| Custom APIs/Services | Custom Logging API | Custom Logging |
Quick start steps (example: BizTalk):
- Navigate to Administration → Log Agents in Web Client
- Click Add Log Agent → Select BizTalk Server
- Configure connection (server name, database)
- Enable agent and test connection
- Send test message through BizTalk → Verify in Nodinite Log Search
Monitor Agent Configuration
Configure Monitor Agents to track system health:
| Resource Type | Monitor Agent | Configuration Guide |
|---|---|---|
| Windows Services | Windows Service Monitor | Windows Service Monitoring |
| Message Queues | MSMQ/IBM MQ Monitor | Message Queue Monitoring |
| HTTP Endpoints | HTTP Monitor | HTTP Endpoint Monitoring |
| Database | SQL Server Monitor | SQL Server Monitoring |
Quick start steps (example: Windows Service):
- Navigate to Monitor → Resources in Web Client
- Click Add Resource → Select Windows Service
- Configure service details (server, service name)
- Set monitoring interval and alert thresholds
- Save and verify status
Configure Alerting
Set up alert notifications for your POC evaluation:
Email Alerts (SMTP)
- Navigate to Administration → Settings → Alarm Plugins
- Click Add Alarm Plugin → Select Email with Options
- Configure SMTP settings:
- SMTP Server: your-smtp-server.com
- Port: 587 (or 25/465)
- From Address: nodinite-alerts@yourdomain.com
- Recipients: poc-team@yourdomain.com
Email with Options Configuration
Webhook Alerts (Slack/Teams/PagerDuty)
- Navigate to Administration → Settings → Alarm Plugins
- Click Add Alarm Plugin → Select HTTP Webhook
- Configure webhook URL and payload format
Test Alerting
- Create a test monitor with low threshold
- Trigger alert condition (stop service, simulate failure)
- Verify alert received via configured channel
- Acknowledge alert in Web Client
Run Your POC Scenarios
Execute the scenarios defined in What Should Your POC Prove?:
Simple Scenario Example
Goal: Track file-based integration end-to-end
- Configure file folder monitor
- Send test file through integration
- View log event in Nodinite with business metadata
- Search and download original file from Web Client
- Success metric: Find and retrieve file in <30 seconds
Moderate Complexity Example
Goal: Correlate request-response across systems
- Configure logging for request system (e.g., BizTalk send port)
- Configure logging for response system (e.g., SAP receiver)
- Use Nodinite Correlation to link request → response
- View end-to-end transaction flow in Web Client
- Success metric: Visualize complete transaction with <60 seconds latency
Advanced Scenario Example
Goal: Enable business user self-service
- Create custom Repository Model for order tracking
- Configure Custom Metadata extraction (Order ID, Customer)
- Grant business users Reader role access
- Business user searches by Order ID in Web Client
- Success metric: Business user finds order status without IT help
Measure POC Success
Track these metrics during your POC:
| Metric | Target | How to Measure |
|---|---|---|
| Log search performance | <2 seconds for 1M events | Use Web Client search with date range |
| Troubleshooting time reduction | 50-70% improvement | Compare time to find errors before/after Nodinite |
| Alert notification latency | <60 seconds from failure | Simulate failure and measure alert delivery time |
| Business user adoption | 3+ business users successfully self-serve | Track unique users accessing Web Client |
| Integration coverage | 80%+ of critical flows logged | Count monitored integrations vs. total integrations |
Post-Installation Security (Optional)
For POC environments exposed to network or evaluating production-readiness:
Enable HTTPS/TLS
- Obtain SSL certificate (see Hardening Guide)
- Install certificate in IIS
- Configure HTTPS bindings for Web Client, Web API, Log API
- Update Portal environment TLS settings
- Redeploy with updated configuration
Complete HTTPS Hardening Guide
Apply Least Privilege
- Post-install: Remove sysadmin from service account
- Grant specific SQL permissions (see DatabaseMaintenance)
- Create separate accounts for each service
- Configure folder permissions for log files
Configure OAuth 2.0 (Optional)
For modern authentication with Azure AD / Entra ID:
- Register Nodinite application in Azure AD
- Configure OAuth settings in Portal environment
- Update Web Client and Web API configurations
- Test authentication with Azure AD users
Next Steps
After completing your POC:
- Working with Nodinite - Learn advanced features and workflows
- Free E-Learning - Comprehensive training courses
- Partner Network - Find certified implementation partners
- Planning Production Deployment - Scale from POC to production
Related Topics
- Install Nodinite v7 - Complete installation guide with troubleshooting
- Planning your Nodinite Installation - Infrastructure and architecture planning
- Hardening Guide - Security best practices for production
- SQL Server Configuration - Database optimization and sizing
- Post Installation Steps - Additional configuration and tuning