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 gives you what you need for a successful POC evaluation:

• ✅ Fast-track setup - Clear prerequisites and a step-by-step installation checklist
• ✅ Modern architecture - PowerShell 7 automation, OAuth 2.0 support, optional HTTPS hardening
• ✅ Proven scenarios - Recommended use cases that demonstrate the value of Nodinite
• ✅ Post-installation - Agent configuration, alerting, and security best practices

Tip

New to Nodinite? This quick-start guide gives you the essential steps for a POC. For detailed explanations, field references, 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 the value of Nodinite through at least three scenarios:

1. Simple scenario - Managed file transfer or single-system integration
2. Moderate complexity - Request-response with multiple systems and message transformations
3. 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 you start, understand how the Nodinite v7 components work together. On Windows Server, every Core Service is its own IIS web site with its own port, set per environment in the Portal.

Integration platforms (purple) send Log Events to the Log API; the Logging Service processes them in the Log Databases. The Monitoring Service reaches the Monitoring Agents (teal), which watch your systems. Users work in the Web Client, which calls the Web API; the MCP Server gives AI clients the same data. Blue: request-driven web sites. Orange: background processing.

Key Components

POC Prerequisites Checklist

Complete these prerequisites before you register your environment in the Nodinite Portal. The Prerequisites page is the master checklist, with commands to verify each item in Detailed Prerequisite Verification.

Infrastructure Requirements

Service Account Requirements

SQL Server Configuration

Security and HTTPS (Optional for POC)

Note

HTTPS is optional for a POC, but required for OAuth 2.0 and recommended on any network-accessible server.

Installation Steps

Step 1: Register the Environment in the Portal

1. Log in to the Nodinite Portal and open your customer entry.
2. Open the Environment tab, click Add Environment, and select Install Fresh Nodinite 7 (Step 1: Basics).
3. Complete the wizard; each step has its own page:

Step 2: Deploy the Generated Package with the CLI

1. Extract the downloaded ZIP to a folder, for example C:\Temp\NodiniteInstall\, and keep its structure.

2. Open PowerShell 7 as Administrator in the extracted folder.

3. Validate, dry-run, and deploy, as described in Step 7: Run the CLI Workflow:

   .\Nodinite.Installer.Cli.exe validate --config .\<serverfolder>\config.cli.json
   .\Nodinite.Installer.Cli.exe deploy-environment --config .\<serverfolder>\config.cli.json --dry-run
   .\Nodinite.Installer.Cli.exe deploy-environment --config .\<serverfolder>\config.cli.json
   

4. Enter any required passwords when the CLI prompts for them.

Important

Use PowerShell 7, not Windows PowerShell 5.1. Verify the version with $PSVersionTable.PSVersion.

Tip

Installation typically takes 5-15 minutes. For troubleshooting and advanced options, see Step 7: Run the CLI Workflow.

What the CLI Does

• Creates or updates the Configuration Database (no Log Database; the Logging Service creates the first one on its first start)
• Creates one IIS web site and application pool per Core Service (Web Client, Web API, Log API, Logging Service, Monitoring Service, and MCP Server), each on the port from the Portal
• Binds the TLS certificate that matches the certificate subject, when HTTPS is configured
• Deploys the selected Log Agents and Monitoring Agents
• Configures the service accounts

Step 3: Verify the Installation

1. Check the IIS web sites: In IIS Manager, confirm that each Core Service has a started web site on its own port. A stopped MCP Server is by design when Keep the MCP Server stopped is selected.
2. Open the Web Client: Browse to the Web Client, for example https://nodinite.contoso.com:<port>/, with the host and port from the Portal (Core platform services). Log in with your Windows account, or with OAuth if configured.
3. Check the Web API: Open Scalar at https://nodinite.contoso.com:<port>/scalar with the Web API port.
4. Check the databases: The Configuration Database exists right after the installation; the first Log Database appears after the Logging Service has started.

Each Core Service's Install page has a full verification checklist, for example Verify the Web Client, Verify the Web API, and Verify the Log Databases.

Configure Your POC Scenarios

Log Agent Configuration

Add Log Agents in the Portal for your POC scenarios; Installing Log Agents explains the options.

Quick Start: Verify Logging

1. Complete the agent's configuration guide.
2. Send a test message through the integration.
3. Find the event in a Log View in the Web Client.
4. In Administration → Log Agents, rename the automatically created Not Set entry.

Monitoring Agent Configuration

Add Monitoring Agents in the Portal to track system health; Installing Monitor Agents explains the options.

Quick Start: Monitor a Windows Service

1. In the Web Client, open Administration → Monitoring Agents and open the agent's Remote Configuration.
2. Add the Windows service to monitor and save; the agent discovers it as a Resource.
3. Add the Resource to a Monitor View and verify its state.

Configure Alerting

Nodinite v7 has four built-in Alarm Plugins: E-mail, E-mail with options, Event Log, and HTTP Webhook. Select an Alarm Plugin entry on each Monitor View that should send alerts.

Email Alerts (SMTP)

1. Open Administration → Settings → Alarm Plugins and open E-mail with options.
2. Configure its default entry: the Recipients tab and the SMTP server, port, and authentication on the SMTP options tab.
3. Select the entry on your Monitor View.

E-mail with options Configuration

Webhook Alerts (Slack, Teams, PagerDuty)

1. Open Administration → Settings → Alarm Plugins and open HTTP Webhook.
2. Configure the webhook URL and payload format, and select the entry on your Monitor View.

HTTP Webhook Configuration

Test Alerting

1. Add a test Resource to a Monitor View that uses your Alarm Plugin entry.
2. Trigger an alert condition, for example stop a monitored Windows service.
3. Verify that the alert arrives through the configured channel.
4. Start the service again and verify the OK alert.

Run Your POC Scenarios

Execute the scenarios you defined in What Should Your POC Prove?:

Simple Scenario Example

Goal: Track a file-based integration end to end

1. Monitor the folders with the File Folder Monitoring Agent
2. Send a test file through the integration
3. View the Log Event in a Log View with its business data
4. Search for and download the original file in the Web Client
5. Success metric: Find and retrieve the file in less than 30 seconds

Moderate Complexity Example

Goal: Correlate request and response across systems

1. Configure logging for the requesting system (for example a BizTalk send port)
2. Configure logging for the responding system (for example an SAP receiver)
3. Extract a shared ID with a Search Field
4. Show the end-to-end flow in a BPM
5. Success metric: Visualize the complete transaction with less than 60 seconds latency

Advanced Scenario Example

Goal: Enable business user self-service

1. Document the order flow in the Repository Model, with Custom Metadata such as the owner
2. Extract Order ID and Customer with Search Fields
3. Give business users a Role with access to an order Log View
4. A business user searches by Order ID in the Web Client, as in Find an order by Order Id
5. Success metric: The business user finds the order status without IT help

Measure POC Success

Track these metrics during your POC:

Post-Installation Security (Optional)

For POC environments exposed to the network or evaluating production readiness:

Enable HTTPS/TLS

1. Install a certificate whose subject matches the host name in LocalMachine\My or LocalMachine\WebHosting (see the Hardening Guide).
2. Set the Certificate subject in the Portal, Core host Configuration.
3. Download the package again and rerun it with the CLI; the CLI finds and binds the certificate. After a renewal, rerun the update.

Apply Least Privilege

1. Reduce the sysadmin right after installation, see SQL Server Sysadmin Requirements.
2. Use separate accounts per service: clear Same account for all Services in Step 4: Servers, or use gMSA.
3. Review the remaining items in Post Installation Steps.

Configure OAuth 2.0 (Optional)

1. Register the Nodinite applications in your identity provider, see Register Nodinite Applications in Entra ID.
2. Select OAuth 2.0 / OIDC in Step 2: Auth, and rerun the package.
3. Protect the Log API with its own app registration, see Protect the Log API with OAuth 2.0.
4. Test sign-in with your identity provider's users.

Install Nodinite v7 - OpenID

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
• Prerequisites - The master prerequisite checklist
• Planning your Nodinite Installation - Infrastructure and architecture planning
• Hardening Guide - Security best practices for production
• SQL Server Configuration - Database options and sizing
• Post Installation Steps - Additional configuration and tuning