- 5 minutes to read

Installing the Mule ESB Monitoring Agent

Unlock seamless monitoring for your MuleSoft Anypoint Platform with the Nodinite Mule ESB Monitoring Agent. This guide covers both the modern Portal-based installation (recommended) and the legacy MSI-based approach for remote servers.

New 7.4.0

Mule ESB Monitoring Agent v7.4.0 and later should be installed using the Nodinite Portal-based scripted installation. This modern approach provides automated installation and configuration with minimal manual intervention.

Why Use Portal-Based Installation?

Automated agent installation and configuration via PowerShell scripts
Configures multiple agents simultaneously with consistent settings
Eliminates manual MSI installations and reduces human error
Centrally manages all environments from the Portal
Includes AI Diagnostics New 7.4.0 for intelligent error analysis
Supports .NET 10 Hosting Bundle for modern runtime performance
Supports gMSA accounts with automatic password rotation

Get Started with Portal-Based Installation

Follow the comprehensive Install Nodinite v7 guide to install the Mule ESB Monitoring Agent using the Portal-based approach. The Portal generates PowerShell scripts that install and configure the agent automatically.

Key Steps:

  1. Register your environment in the Nodinite Portal
  2. Select Mule ESB Monitoring Agent in the Agents configuration tab
  3. Configure agent settings (mule versions, environments, credentials)
  4. Download the installation package with embedded PowerShell scripts
  5. Run the PowerShell script to install and configure automatically

Complete Portal Installation Guide - Step-by-step instructions with screenshots


Warning

Deprecated: The MSI-based installation method is legacy and intended only for remote server installations where the Portal-based approach cannot be used. This method is not recommended for new deployments and will be retired in future versions.

Important

Version 7.4.0+ Users: If you are installing Mule ESB Monitoring Agent v7.4.0 or later, use the Portal-based installation method instead. The MSI approach below is for legacy v6 installations or remote servers only.

When to Use MSI Installation

Use this method only if:

  • You are installing on a remote server that cannot be managed via Portal scripts
  • You are maintaining a legacy v6 environment (upgrade to v7 recommended)
  • You have specific infrastructure constraints preventing automated installation

MSI Installation Prerequisites

Important

You must be a local administrator to have the right to install Windows Services.

Before you begin

Make sure you comply with the prerequisites for the Mule ESB Monitoring agent.

Step 1: Start the installer

Double-click on the MSI file to start the installation of the Nodinite Mule ESB Monitoring Agent.
msi
The installation begins with the MSI package.

Step 2: Accept End User License Agreement (EULA)

The Licensee is ultimately responsible for making sure Nodinite products are used according to the End User License Agreement. Make sure you have the assigned formal rights to install and perform modifications to the target environment before you continue installing any Nodinite products.
EULA
Review and accept the EULA to proceed.

Step 3: Welcome screen

On successful execution of the MSI file, a Welcome screen is presented.
Welcome
The installer welcomes you to the setup process.

Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.

Step 4: Custom setup

Select the Components and Location of the installation. Default settings are recommended.
Custom Setup
Choose components and installation path as needed.

Click the 'Next' button to continue the installation process or click the 'Cancel' button to quit the installer.

Step 5: Service Account Information

Enter the credentials for the Account to run Nodinite Mule ESB Monitoring Agent. Depending on the connection string settings, this account will be used to connect to and monitor Mule environments.

Domain: The name of the Domain the Server belongs to. If a local account is being used, use the name of the server or a . (dot) as Domain
User: The name of the account
Password: The password for the account.

Note

The account must have 'Log on as Service Right'

Domain service account
Enter the service account credentials here.

Click the 'Next' button to continue the installation process or the 'Cancel' button to quit the installer.

Insufficient Privileges

Error message when account information does not meet Prerequisites for Mule ESB Monitoring Agent.
This error appears if the account lacks required permissions.

If you get this message, the most common reason is that the account is not allowed to run as a service or is not a local Administrator on the server. Follow the guide How to set Logon as a Service right and click retry. If the problem remains, click cancel and restart. Make sure to enter valid credentials!

Tip

Check the local event log if there are errors (both System and Application)

Note

Do not use the Mule Management Console for deployment. Drop the ZIP file directly into the apps directory.


Support

If you need help, contact our Support.

Note

Additional troubleshooting information may be found in the Windows Event Logs.

Frequently asked questions

Find more solutions and FAQs for the Nodinite Mule ESB Monitoring Agent in the Troubleshooting guide.


Next Step

Add or manage a Monitoring Agent Configuration
Configuration of the agent
Update
Uninstall

Prerequisites for Mule ESB Monitoring Agent
Monitoring Agents