- 8 minutes to read

Managing the Install and Update Tool

Always make sure to perform installations and updates using the latest version of the Install and Update tool, see the release notes for additional information

To reach the tool you can try the default address http://localhost/NodiniteUpdate/UpdateClient/ or check your IIS for the correct address if you can not reach it.


With the Nodinite Install and Update tool you can manage the following features:

Manage instance of Nodinite

Assigning Access rights

TheNodinite Install and Update tool can be configured to only allow named users or members of named Windows Active Directory Groups. Setting security restrictions secures your instance of the Nodinite Install and Update tool by configuring who is allowed entry. Currently, users who are granted access, still need to provide passwords for all accounts (usually just one) configured for the Nodinite Core Services.

If you have not yet assigned any access rights, the tool will then complain about it with a visible yellow warning bar, encouraging you to configure the access rights. Access to the tool is otherwise fully open for everyone.

How do I restrict access?

Make sure to add your self to the list of allowed users before accepting and persisting your changes

From the Settings tab/page you can Add and Remove users and groups. You must know the exact names from your Active Directory in the format (you can see your account name to the far right in the bottom of the tool):

  1. Domain\User Name
  2. Domain\Group Name
    Settings tab where an authenticated and assigned user can add and remove users and groups to allow/prevent access to this tool

Note: When you click on the Add/Remove buttons, the changes are immediately effective

After you have assigned the first-named user account or group, the settings are instantly applied and if you did not provide your own account, then you got locked out.

Configuration file

You should only edit this file manually if you lock yourself out of the tool or perform advanced updates/reconfigurations. Make sure to create a backup before you proceed

Users and groups may be edited in the underlying Settings.json file.

You need to be an administrator with access to the file system to read and change the content of this file. Remember to open Notepad elevated, or even better use Notepad++


ActiveDirectoryUsers": [
    "Name": "DOMAIN\\JohnDoe"
    "Name": "DOMAIN\\JaneDoe"
"ActiveDirectoryGroups": [
    "Name": "DOMAIN\\administrators"

Package Management

You can manage downloaded packages with Nodinite. First, click on the Package Management button from the Instances main menu. PackageManagement

The Packages already added are listed in the Packages tab:
List of Packages with version info

Download new package version from the Internet

Downloading the package with Nodinite Core Services requires only 1 zip file to be downloaded. There are two ways to get the latest version of Nodinite:

  1. Add package from the Internet - Available from within the Nodinite Install and Update tool

This option requires Internet access from the server hosting the Nodinite Install and Update tool, see bullet Download from Internet below

  1. Add package manually - Download to the local file system (including external media like USB...) See bullet

The currently installed version of Nodinite is printed in the Web Client, read more in the Nodinite Version user guide.

Step 1: Add Package You can add Nodinite package using any of the following options:

  1. Download from the Internet
  2. Add manually

1. Download from the Internet

The latest available version and accompanying Release Notes forNodinite is displayed in the Latest version Online frame.

  • Click Download package to get the latest officially released version (requires Internet connection)
    Direct download of Nodinite
    Download the new version from Internet Option from within the tool

Step 2: Continue with either Install or Update

2. Add manually

For Nodinite instances without access to the Internet, you must manually download a Nodinite release. This option is also the way to go when installing BETA releases (often the case during POC's).

Manual Download tab
Example of the manage packages manually dialogue

  • Click on the Browse button and select the Nodinite release to Upload

Select file to upload from the local file system

  • Click on the Upload button to start the upload, this may take a few seconds because the ZIP file will be validated and extracted

Upload started operation

DO NOT INTERRUPT THIS OPERATION!!! The operation should normally complete within 10-30 seconds depending on current load and other circumstances on the server

Step 2: Continue with either Install or Update

Installing a new instance of Nodinite

You can install new instances of Nodinite using the Nodinite Install and Update tool. Follow the steps in the Installing and Configuring - Nodinite user guide to get Nodinite installed and configured for first use.

If you have all your prerequisites set, then you should only be 15-30 minutes away from running your Nodinite instance

Updating an existing instance of Nodinite

Always use the latest version of the Nodinite Install and Update tool, see Release Notes for more information

Existing instances of Nodinite are updated using the Nodinite Install and Update tool. An Update operation always uses the highest version from the list of uploaded packages. It's only possible to Update, downgrades are not implemented.

Before continuing with the update, make sure you have the latest version of the Nodinite Install and Update tool and the latest version of Nodinite uploaded.

The Update all button is only enabled when and if there is a higher package version available (uploaded).

Step 1: Select environment

Begin with selecting the environment to Update.

There can be multiple instances to manage from the list of installed Nodinite instances. There is one table for each Customer

  1. Click on a row the environment name to update
  2. Or Click on the Action button and select the Update menu item
    Select environment
    List of available instances to update

Step 2: Review Update

Next, you will be presented with a summary of installed components and components which are due for an update. If there are updates to any of the Log Databases, the update tool does not allow you to perform the update until you have manually updated every one. Always begin with the oldest one and move forward. More about this in the steps to follow.

We strive hard to only release new versions of the Log Databases where you can also expect that there might be changes for major releases (features), never to minor builds (bugs).

Application Update Database and Application Update
  1. Configuration Database requires no update, compare with the image to the right where an update exists 1.1 If there is a problem updating the database or you want to update manually follow the How to manually update database user guide
  2. Log API will be updated
  3. Click on Update All to open the update modal.

Log databases must always be updated manually, copy the DACPAC command and follow the How to manually update database user guide before continuing

Step 3: Perform Update

Now that all your Log Databases are up to date, you can initialize the update process. For each unique named account configured for the Core Services, you must provide the password.

  1. Select the version to update to (by default the highest available version is selected)

NOTE: If you perform manual updates to any of the databases in the previous steps then make sure to select and verify the SAME version in this dialogue is selected

  1. Enter the password for the installation/service account(s) and click on the Validate Account button.
    Example: Enter the 'Password' for the service account

  2. When all accounts are validated, you can initialize the update process by clicking on the Update Nodinite button
    Example: All fields validated and ready to begin the update process

  3. A progress bar will be displayed, Wait for the update to finish (usually takes between 15 seconds and 3-5 minutes, depending on current workload, often the longest time for the update is to gently stop processes with work in progress)

  4. When completed successfully, click the Close button

Congratulations, Nodinite is now up to date

Manage BizTalk Server Logging

Add and Remove Microsoft BizTalk Server Logging Agents is detailed in the 'Configure Microsoft BizTalk Server Logging Agent' user guide.

Manage System Parameters

Each instance of Nodinite is managed individually and when working with one instance you have access to the System Parameters and changing run-time values are described in the 'How do I change the System Parameters' user guide.

Manage License

To manage the License, click on the Manage Licence button:
Manage License Button

From within this page, you can edit the following two properties:

  1. Customer Name
  2. Product Key

Manage License

When you click on the Save button, the information in the header is updated and the licence gets validated. This feature will help you detect visually when the product key is about to expire.

The ability to modify the license as documented in this section was introduced with the 5.2 release. If your list of Nodinite instances has the following icon displayed, simply open the licence modal and click on the Save button to validate the license.
Update License Icon
Example of license as displayed after update to 5.2

Next Step