- 10 minutes to read

Install Nodinite v7

Install Nodinite v7 confidently and efficiently. This guide empowers you to set up a robust integration platform, ensuring a secure, future-proof, and hassle-free deployment.

What you’ll achieve by following this guide:

  • ✅ Rapid, reliable installation with minimal downtime
  • ✅ Clear prerequisites and configuration steps for success
  • ✅ Flexible agent and database setup for any environment
  • ✅ Access to expert support and resources throughout the process

Update Nodinite v7

Tip

If you have a non-prod environment, we recommend testing the install process there first. This ensures you can validate all steps and configurations before applying them to your production environment.

Looking for a partner to help you install? Please contact any of our certified Partners.

Important

You must have knowledge of account names and their passwords and you must have administrative rights on the Nodinite Application Server to perform the installation.

Prerequisites

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

  • Administrator access to the Nodinite Application Server where the installation will be performed.
  • PowerShell 7 installed on the Nodinite Application Server. This is required to run the installation scripts.
    • You must temporarily allow importing/loading script blocks in PowerShell 7. Review this guide; Either use Unrestricted or ByPass. When you are done, you may revert the execution policy to its original setting.
  • Powershell 7 script user must be a member of the sysadmin role on the SQL Server instance where the Nodinite databases are hosted. This is required for the script to perform database migrations and updates.
  • Nodinite 7 product key available in the Nodinite Portal. If you don't have one, contact your partner or Nodinite Support.
  • Latest version of .NET 9.0 Install .NET Runtime 9.0.x AND ASP.NET Core Runtime 9.0.x (Hosting bundle) installed on the Nodinite Application Server. This is required for the new features and improvements in Nodinite v7.
  • Latest version of DacFX installed on the Nodinite Application Server. This is required for database migrations and updates.
  • IIS Management Scripts and Tools installed on the Nodinite Application Server. This is required for managing IIS and web applications during the installation process.

Estimated time

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

The installation process typically takes only a few minutes. This estimate includes installing all Monitoring Agents and Log Agents.

graph LR A["Register Environment"] --> AA["Configure Agents"] AA --> B["Download/Extract ZIP (Core and Agents)"] B --> C["Run PowerShell Script"]

Visual overview of the installation process.

Step 1: Register Environment

In the Nodinite Portal, register 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 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 Nodinite Support.

  3. Click the Environment tab, then click the Add Environment button.
    Add Environment
    Example of the Add Environment button in the Nodinite Portal.

  4. A modal appears, click 'Install Fresh Nodinite 7' button.
    Install Fresh Nodinite 7
    Example of the 'Install Fresh Nodinite 7' button.

  5. The modal changes and you must now enter variables (ultimately parameters in the PowerShell 7 scripts).
    Add Environment Variables
    Example of the Add Environment Variables modal.

Configure Nodinite 7 variables

💡Configure the necessary variables for the Nodinite 7 environment.

In this step, you will set the required variables for your Nodinite 7 environment. These variables are essential for the proper functioning of Nodinite and must be configured correctly.

Please ensure that you set the configuration values correctly, as some of them are difficult to change later. Your runtime platform is configured with these values, and they are utilized in the PowerShell script that will run later in the process. If you need to modify these values, you might have to remove everything except for the databases and start over.

If you are unsure about some values, enter placeholder information to continue. You can override these parameters later when you run the PowerShell 7 installation script. This flexibility allows you to update settings before finalizing the installation, ensuring you have full control over your environment configuration.

Mandatory Variable Default Description
Environment Name* The name of the target environment
NOTE: Once set, this should not be changed as databases, app pools, folders and more are poisoned with this name.
Description Description to clarify purpose or usage.
Destination Root Path C:\Program Files\Nodinite Leave it empty to select default value.
Default Domain Name* <DomainName> Name of the Windows Active Directory Domain; Default prefix for accounts;
Admin Account <NodiniteAdminUsrAccountName> Enter Nodinite Administrator Account Name.
Admin Account Email Enter Nodinite Administrator Account Email.
Default Services Account Name <DefaultServiceAccountName> Enter Default Services Account Name. You can override these in the 'Advanced' tab
Web Client Port 40000 IIS Port for Web Client
Web API Port 40001 IIS Port for Web API
Log API Port 40002 IIS Port for Log API
Logging Service Port 40003 IIS Port for Logging Service
Monitoring Service Port 40004 IIS Port for Monitoring Service

Configure Database Settings

💡Configure the database settings for Nodinite 7.

There are different settings depending on the type of database you want to use.

  1. Standalone - Use a single SQL Server instance for all databases. Use this option if you are using SQL Server Standard, Enterprise, or Express edition. Tihs also works for failover clusters.
  2. Always on - Use a SQL Server Always On Availability Group for high availability and disaster recovery.
  3. Azure - Managed Instance - Use an Azure SQL Managed Instance for a fully managed database service in the cloud. This option is suitable for cloud-based deployments. If you select this option, you must provide the connection string to the Azure SQL Managed Instance. As this option is NOT using integrated security, you must eventually provide the username and password for the database. This should be done by replacing this value directly in the PowerShell script that is run later in the process.
  4. You can also choose to Edit Connection String Manually if you prefer to configure the connection string yourself.
Mandatory Option/Setting Default Description
Database Type
  • Standalone
  • Always on
  • Azure - Managed Instance
 Type of database to use for Nodinite 7. The default is Standalone. If you select Clustered, you must provide a connection string to the SQL Server instance.
Database Server Name localhost Name of the SQL Server instance. The default is localhost. If you are using a named instance, use the format ServerName\InstanceName.
Edit Connection String Manually No Whether to edit the connection string manually.
Connect without encrypt No Whether to connect without encryption.
Encrypt Connection Checked Whether to encrypt the connection, or not. Should be checked on most environments
Trust server certificate Checked Whether to trust the server certificate, or not. Should be checked on most environments
Trust Server Certificate Checked Whether to trust the server certificate, or not. Should be checked on most environments
Sql Package Path C:\Program Files\Microsoft SQL Server\170\DAC\bin\SqlPackage.exe Path to the SqlPackage.exe tool.

Step 2: Save

💡Persist your settings.

You should save your settings before proceeding to the next step. Review all settings carefully to ensure they are correct.

Click the Save button to save your settings.
Save Button
Example Screenshot of the Save Button.

If the save is successful, you will see a confirmation message and another tab will appear in the modal. You can click the Review button to review your settings before proceeding. Your settings display with a visual graph. See Step 4: Review for more details.

Step 3: Select and Configure Agents

💡Select and configure Agents to include in the installation.

In this step, you will select the Agents you want to include in the installation. The Agents are responsible for Monitoring and Logging.

Click the Agents tab to view the available Agents.
Agents Tab
Example of the Agents tab in the Nodinite Portal. Click on the accordion on any of the agents to expand the configuration options.

Check the checkboxes for the Agents you want to include in the installation.

You must enter a port number for use within the IIS for each Agent you select. The port numbers must be unique and not conflict with other services running on the same server. The default port numbers are provided, but you can change them if needed.

Some agents like BizTalk, Azure Logic Apps, Dynamics CRM and IBM DataPower require additional configuration, such as the database connection string. Ensure you provide the correct values for these settings.
Logic Apps Agent Configuration
Example of the Logic Apps Agent configuration entry with additional configuration properties.

Step 4: Review

💡Review settings using a visual graph before you continue with the installation operation.

In this step, you have the opportunity to review your settings before you download the necessary binaries for Nodinite v7.

We recommend reviewing all settings carefully to ensure they are correct before proceeding. Click on the 'Overview' tab to open a Mermaid diagram displaying the current configuration in a user-friendly graph.
Review Settings Graph
Example of how the Environment will look with the current settings after the installation operation has completed.

Step 5: Download Binaries

In this step, you will download the necessary binaries for Nodinite 7.

  1. Close the modal if it is still open, or navigate to the Environments tab.
  2. Click the Actions button, and the click the Download menu item to start the download process.
    Download Binaries
    Example of 'Download' menu item in the Actions button.

While generating your ZIP package with the necessary binaries the following screen will be displayed:
Downloading Nodinite Binaries
Example of the Downloading Nodinite Binaries screen.

Once the download is complete, you can proceed to the next step.

Step 6: Run PowerShell 7 Script

💡Run the PowerShell 7 script to install your environment.

In this step, you will run the PowerShell 7 script to install your environment.

  1. Open a PowerShell 7 terminal with administrative privileges.
  2. Navigate to the folder where you extracted the downloaded ZIP file.
  3. Run the script by executing the following command (If you run the script like this, you will be prompted to enter the mandatory values interactively):
dir -r | unblock-file
.\Nodinite7-%ENVIRONMENTNAME%-Installation.ps1

Interactive Installation Script Example
Example Screenshot of the Interactive Installation Script.

After applying passwords the script starts the installation process:
Installation Overview Example
Example of the Installation in progress.

Important

If you provided bogus values in the previous steps, you must NOT edit the script to provide the correct values for the parameters. This includes the database connection string, service account names, and other settings you specified in the Nodinite Portal. You must run the script providing the new values, for example (you can use tab to switch between the available parameters):

For each unique password, repeat the following command to acquire a secure string:

dir -r | unblock-file
$serviceAccountPassword = ConvertTo-SecureString "P@ssw0rd" -AsPlainText -Force
.\Nodinite7-DEMO-Installation.ps1 -WebClientServiceAccount "Domain\n-svc" -WebClientServiceAccountPassword $serviceAccountPassword

Important

The password is SecureString. You must create a separate variable and use it accordingly for each unique password.

Override variables
Example of overriding variables in the PowerShell script.

    1. Open the Web Client and perform some basic checks to ensure the installation was successful.

Contact our support

If you have questions or encounter issues during the upgrade, contact your partner for 1st line support or email us at support@nodinite.com.

Next Step

Updating Nodinite v7

Uninstall Nodinite v7