- 5 minutes to read

Update Nodinite v7

Upgrade your Nodinite v7 with confidence and ease. This guide empowers you to perform a secure, efficient, and hassle-free update to the latest version, ensuring your integration environment remains robust and future-proof.

What you’ll achieve by following this guide:

  • ✅ Minimize downtime and disruption for end-users
  • ✅ Protect your data with clear backup and validation steps
  • ✅ Benefit from the latest features and improvements in Nodinite v7
  • ✅ Access expert support and resources throughout the process
graph LR subgraph "Nodinite v7" roPortal(fal:fa-person-to-portal Nodinite Portal) roEnvironment(fal:fa-leaf Environments) roZIP(fal:fa-file-zip Download ZIP) roCLI(fal:fa-terminal CLI Installer) roPortal --> roEnvironment roEnvironment --> roZIP roZIP --> roCLI end subgraph "Nodinite Instances" roCustomerSouth(fal:fa-code-commit Development) roCLI -.- roCustomerSouth roCustomerContoso(fal:fa-code-commit PreProd) roCLI -.-> roCustomerContoso roCustomerNorth(fal:fa-code-commit Prod) roCLI --> roCustomerNorth end style roPortal fill:#90EE90 style roEnvironment fill:#90EE90 style roZIP fill:#90EE90 style roCLI fill:#90EE90 style roCustomerSouth fill:#87CEEB style roCustomerContoso fill:#87CEEB style roCustomerNorth fill:#87CEEB

Visual overview of the update process for multiple environments.

Install Nodinite v7

Tip

If you have a non-prod environment, test the upgrade process there first. This lets you validate all steps and configurations before applying them to production.

Looking for a partner to help you update? Contact any of our certified Partners.

This guide assumes you already have Nodinite version 7 installed, potentially with Monitoring Agents and Log Agents.

Important

After the Core Services update is complete, always review the Log Databases page in the Web Client and use the Update Log Database wizard if the page reports that a database schema update is available. This is a separate step from the Core Services installation and is often required after major v7 upgrades.

Important

You must know the account names and their passwords and have administrative rights on the Nodinite Application Server to perform the update.

Prerequisites

Before you begin the update process, ensure you have the following prerequisites in place:

  • Inform end-users about the update and potential downtime.
  • Backup your Nodinite databases and configuration files. This is crucial to prevent data loss in case of any issues during the update.
  • Existing Nodinite v7 installation with Monitoring Agents and Log Agents configured. Everything will be updated to the latest version.
  • Valid Nodinite 7 product key available in the Nodinite Portal. If it has expired or is nearing expiry, create a new one. If you cannot do this, contact your partner or Support page.
  • The Prerequisites for Installing Nodinite v7 must be met.
  • Network access: Ensure the Nodinite Application Server can reach the outbound hosts listed in Prerequisites for Installing Nodinite v7. The same allowlist applies to portal downloads, version metadata, and optional direct MSI downloads for remote server installation.

Estimated time

On a high level, there are a few distinct steps in the update process:

Running the CLI commands typically takes a few minutes. This estimate includes updating all Monitoring Agents and Log Agents.

After the CLI deployment finishes, review the Log Databases overview in the Web Client and run the Update Log Database wizard if there are schema updates pending for any existing database.

graph LR A["Select Environment"] --> B["Download/Extract ZIP (Core and Agents)"] B --> C["Run CLI Workflow"] style A fill:#90EE90 style B fill:#90EE90 style C fill:#90EE90

Example of the main steps in the update process.

Step 1: Select Environment

Tip

Find the environment for the Licensee

In the Nodinite Portal, select your environment by following these steps:

  1. Navigate to the existing Customer entry.
    Customer Overview
    Find and Click on the Customer entry.

  2. Ensure you have a valid Nodinite 7 product key available. If not, create it by clicking on Create Product Key button.
    Product Key Entry
    Example of a Nodinite 7 product key entry.

    Important

    You must have a valid Nodinite 7 product key to proceed with the upgrade. If you can't create one, please contact your partner or Support page.

  3. Click the Environment tab and find the entry to update.
    Environment
    Example of Environment to update for a selected Licensee in the Nodinite Portal.

Step 2: Download/Extract ZIP (Core and Agents)

Tip

Download the CLI bundle ZIP for the selected environment.

  1. Click the Download all packages button in the Review and Download step of the environment entry.:
    Download
    Example of the Download all packages button in the Review and Download step of the environment entry.

    Alternatively, from the Environments Overview for selected Customer, you can click the Actions button and select Download all packaages from the Actions menu.
    Action Download
    Example of the Actions button and Download all packages menu item in the Environments Overview for selected Customer.

  2. The download will begin immediately. Save the ZIP file to your preferred location.
    Downloading
    Example of the downloading process in the browser.

Step 3: Run the CLI workflow

In the extracted ZIP bundle, navigate to the folder with the host name of the Nodinite Application Server. This folder contains the generated config.cli.json file for your environment. Inside, you will find a readme.txt file with instructions for running the CLI commands.
Execute the commands from an elevated PowerShell 7 prompt in the extracted ZIP bundle root.

Tip

Run commands from an elevated PowerShell 7 prompt in the extracted ZIP bundle root.

Use this recommended workflow (localhost is just an example, replace it with your actual host name as mentioned in the readme.txt file):

  1. Validate the package without changing the machine:
.\Nodinite.Installer.Cli.exe validate --config .\localhost\config.cli.json
  1. Run a dry-run to check install/update actions:
.\Nodinite.Installer.Cli.exe deploy-environment --config ".\localhost\config.cli.json" --dry-run
  1. Deploy after validation and dry-run are clean:
.\Nodinite.Installer.Cli.exe deploy-environment --config ".\localhost\config.cli.json"

If you need runtime overrides, pass arguments instead of editing generated files. Common examples include --database-connection-string, --agent-connection-string, and --service-password.

After deployment, browse the Web Client and perform basic verification checks.

File Locks Detected

If you encounter file locks during the update, the CLI will report them. On Windows, issue a iisreset command to release the locks, then rerun the CLI command. A reboot of the Nodinite Application Server may also be required to release locks. Some .NET 10 updates occassionally also require a reboot to complete the update.
CLI File Lock Error
Example of a file lock error reported by the CLI. Use iisreset to release locks and rerun the command.

Contact our support

If you have questions or encounter issues during the upgrade, contact your Partner for 1st line support or read more at the Support page.

Next Step

Nodinite Portal

Install Nodinite v7
Log API
Logging Service
Monitoring Service
Web API
Web Client