- 5 minutes to read

Update Integration Manager from v4 to Nodinite v5

Upgrade your Integration Manager v4 to Nodinite v5 with confidence. This guide walks you through every step, ensuring a smooth, secure, and efficient transition to the latest version.

✅ Comprehensive checklist for a successful upgrade
✅ Key prerequisites and app pool configuration tips
✅ Step-by-step agent and database migration
✅ Troubleshooting and support resources for your team

On this page you will learn how to update Integration Manager v4 to Nodinite v5.

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

This guide assumes you have Integration Manager version 4 installed, which means all Prerequisites are already in place.

Nodinite 6.0 and later require .NET Framework 4.8 or later.
Nodinite 5.1 and later require .NET Framework 4.6.2 or later.
Nodinite 5.0 requires .NET Framework 4.5.2 or later.

Important

  • You must have access to old accounts and their passwords since you will need to re-enter them during the install and update process.
  • You must be allowed to manage instances—see Install and Update Tool - Access Rights.
  • Review IIS Authentication settings—you MUST use multiple app pools, one for each Web application. The installer stops and restarts the different App Pools automatically during the update.

IIS App Pools that must exists prior to update
Ensure you have at least the highlighted 4 App Pools on your Nodinite IIS Windows Server (rename as appropriate for your environment).

If you change the App Pool configuration, update the settings.json file for the Update client accordingly.

Estimated time

The update process typically takes about 1 hour for a test environment, depending on the number and size of Log Databases to be updated. This estimate includes replacing all Monitoring Agents and Log Agents.

Step 1: Download binaries

Download and install the following components in order:

  1. New installer (Install and Update tool)
  2. New Core Services Package
  3. New Agents

Step 2: Install the Nodinite Install and Update tool

  1. Make a copy of the app.im.json file and store it in a safe place, renaming it to settings.json
  2. Install the new Nodinite Install and Update Tool
  3. Replace the settings.json file in the new folder structure with the file from step 1.

    Note

    The file is now located in the APP_DATA folder

  4. Reload the browser and ensure all old environments are now listed in the Update/Configure menu pane:
    List of Environments
    Sample list of environments.

Step 3: Download the version of Nodinite to install

Follow the steps in the Packages user guide.

Step 4: Update Nodinite to latest package

  1. Follow the steps in the Update an existing instance of Nodinite user guide.

Remember to update ALL Log Databases before clicking the Update all button. This is the most time-consuming step.

Tip

The update process may consume significant disk space (all transactions are logged in SQL to the Log file). Shrink all database files after each database update.

Step 5: Update Monitoring and Logging agents

  1. Download the latest MSI
  2. Verify the agent to update is installed on the target server.
  3. Note the Service Account used before installing the new agent version. The old service name will be replaced.
  4. Install the latest agent version to the new folder structure and re-use the account from the previous step.
  5. From the old location, copy the *agent*.json file to the new location as Settings.json

    Some agents provide Metrics—copy the Metrics.json file if it exists.

  6. Restart the agent
  7. Change the Service URL from IM to Nodinite
    ChangeMonitoringAgentServiceURL
    Update the Service URL for each Monitoring Agent to use Nodinite.
  8. Verify configuration (ensure all settings still apply)

    Some agents have a new Culture property in the Settings tab—set a value appropriate for your time zone.

  9. Remove the old agent folder (it should now only contain a few files)

Repeat step 5 for each agent to update

Important

If the agent account is not a local admin, you may need to allow the agent to communicate on the new Endpoint (previous installations used /IM, now /Nodinite). See the Port 8000 user guide for more information.

netsh http add urlacl url=http://+:8000/Nodinite user=DOMAIN\user

The command above grants the service account DOMAIN\USER access to the url access control list.

Useful TSQL scripts

The following TSQL scripts help you change the names of existing Log Databases.

Change database names

This script creates another TSQL Script to rename all existing databases in your SQL Instance with a name like the @prefix variable.

Change the @prefix parameter as appropriate and run from the Master database

DECLARE @sql NVARCHAR(max) =''
DECLARE @prefix NVARCHAR(255) =  'IMLog_DEMO_'
DECLARE @length INT
SET @length = LEN(@prefix) 

;WITH imlogdatabases (Name) as
(SELECT name From sys.databases Where name Like (@prefix + '%'))--'IM_Log_PROD_%')
Select @sql += 'ALTER DATABASE [' + l.Name + '] Modify Name = [NodiniteLog_PROD_' + Substring(l.name, @length +1, 255) +']'  + CHAR(13)+CHAR(10) 
--SELECT *
FROM imlogdatabases l
ORDER BY name
Print @@Rowcount
Print @sql

Creates a script to change the names of existing Log Databases.

Change name of existing Log databases

This script creates another TSQL Script to update the names of the Log Databases in the LogTables table in the Configuration Database (name like the @prefix variable).

Change the @prefix parameter as appropriate and run from the Configuration Database

DECLARE @sql NVARCHAR(max) =''
DECLARE @prefix NVARCHAR(255) =  'IMLog_PROD_'
DECLARE @length INT
SET @length = LEN(@prefix) 

;WITH imlogdatabases ([Database]) as
(SELECT [Database] From LogTables Where [Database] Like (@prefix + '%'))--'IM_Log_PROD_%')
Select @sql += 'UPDATE LogTables SET [Database] = ''NodiniteLog_PROD_' + Substring(l.[Database], @length +1, 255) +''''  + ' WHERE [Database] = ''' + l.[Database] + '''' + CHAR(13)+CHAR(10) 
FROM imlogdatabases l
ORDER BY [Database]
Print @@Rowcount
Print @sql

Creates a script to update the LogTables table in Configuration Database.

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