- 3 minutes to read

Release Notes

Installing the Nodinite Boomi Monitoring agent

This guide teaches how to manually install the Nodinite Boomi Monitoring agent. With Nodinite 7, the installation can be scripted.

Nodinite version 7

Preferred Method: Portal-Based Scripted Installation

In Nodinite v7, agent installation is automated through the Portal-based scripted installation. This modern approach:

✅ Automates agent installation and configuration via PowerShell scripts
✅ Configures multiple agents simultaneously with consistent settings
✅ Eliminates manual installations and reduces human error
✅ Centrally manages all environments from the Portal

Follow the Install Nodinite v7 guide to install agents using the Portal-based approach. The Portal generates PowerShell scripts that install and configure agents automatically across your infrastructure.

Nodinite version 6 (Manual Installation - Legacy)

Warning

The manual installation method for Nodinite v6 is deprecated and will be retired. Please upgrade to Nodinite v7 for the modern Portal-based scripted installation experience.

Before you begin

First, ensure sure you comply with the prerequisites.

Note

You must be a local administrator to have the right to install Web Applications and manage IIS

Step 1: Download

Make sure to download the latest binaries (zip package) from the Nodinite portal.

Step 2: Create IIS App Pool

Next, create a new IIS App Pool.

  1. Open the IIS Manamagement Console (inetmgr)
  2. Create a new IIS App Pool, name it, for example Nodinite-%ENVIRONMENTNAME%-BoomiMonitoring_ID-AppPool
    Add IIS App Pool
    1. No Managed Code
    2. Integrated
    3. Check the Start the application pool immediately
      Create IIS App Pool

Step 3: Unzip package

In this step, you will unpack and unblock the files.

  1. Unzip the package to folder: c:\Program Files\Nodinite\%ENVIRONMENTNAME%\Agents\BoomiMonitoring_ID\.

    • Replace the %ENVIRONMENTNAME% accordingly with your Environment. The _ID should be replaced to uniquely identify this instance given that you are installing multiple instances of the agent. You can omit it completely if this is the only instance.
    • New 7.x With Nodinite 7, the _ID should be set in the Nodinite Portal.

  2. Unblock the files,

    Get-ChildItem -Path '%FOLDERFROMSTEP3%' -Recurse | Unblock-File

Step 4: Create Web Site

In this step, you will create a new Web Site:

  1. Expand 'Sites'
    Create New Web Site
    Example of creating a new Web Site in IIS.
  2. Create a new Web Site and name it 'Nodinite-%ENVIRONMENTNAME%-BoomiMonitoring_ID'
    Add WebSite
    • Set the folder you chose in step 2.
    • Select the App pool created in step 2.
      Select IIS App Pool
  3. Edit Permissions on the Application
    Edit Permissions
    • IIS AppPool\%NAMEOFIISPOOLFROMSTEP2%
    • Click 'Check name' to validate account.
    • Select 'Full control'.

Step 5: Test

In this step, you are verifying that the agent is operational.

Click the Web Application and select Browse. This should then open the default browser with a new tab, and a page with the Swagger content like below.
Swagger
Here's an example of the Swagger feature in the Nodinite Boomi Monitoring agent.

If you would like to test the APIs, you must first Authorize requests with an x-api-key.
Authorize
Click the Authorize button to enter the x-api-key.

xapikey
Enter the x-api-key, reuse from any other installed and configured Nodinite Monitoring Agent.

Step 6: Add Agent as a new Monitoring Agent Configuration

Instructions on how to add the Nodinite Boomi Monitoring agent as a Monitoring Agents is detailed in a shared article, click on the link below to learn more:

Next step

Add or manage a Monitoring Agent Configuration
Configuration
Update
Uninstall

Monitoring Agents
Prerequisites