- 4 minutes to read

Release Notes

Prerequisites for Mule ESB Monitoring Agent

This page describes the prerequisites for installing and running the Nodinite Mule ESB Monitoring Agent.

graph LR subgraph "Nodinite" roNI(fal:fa-code-commit Mule ESB Monitoring agent) --- roMonitor[fal:fa-monitor-waveform Monitoring] end subgraph "Mule ESB (v3.x)" roMonitor --- |On-Premise|roDB1("fal:fa-random Instances with Nodinite Monitoring Mule Application
(zip)") end subgraph "Cloudhub / Anypoint (v4.x)" roMonitor --- |Hybrid|roCH(fal:fa-cloud Cloudhub Environments) end

Instances of this agent can be installed on-premise using TCP/IP for local network access and/or in the cloud/off-site using Service Bus Relaying (see also the external link for additional information MicrosoftServiceBusRelayingLink).

We recommend that you keep this agent close to the Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server).

Mule ESB Application (ZIP)

This section is applicable for version 3.x. Use this option with on-premise environments. Mule version 4.x uses the public CloudHub APIs.

With Nodinite, the Nodinite Mule ESB Monitoring Agent communicates with a Nodinite-specific Mule ESB Application that you install on all Mule Server Instances to monitor. The Application itself accesses the Mule ESB run-time locally.

Verified Topic
Software Requirements
What Windows User Rights does the Nodinite Mule ESB Monitoring agent require?
What Mule ESB User rights does the Nodinite Mule ESB Monitoring agent require?
What Cloudhub user rights does the Nodinite Mule ESB Monitoring agent require?
What Firewall settings does the Nodinite Mule ESB Monitoring agent require?

Software Requirements

This section applies to the Nodinite application server (usually), you will install the Nodinite Mule ESB Monitoring Agent as a Windows Service.

Product Version/Edition
Windows Server Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.8 or later New 6.0
Mule ESB 3.7 and later
MuleSoft ESB Mule runtime engine 4.0 and later
MuleSoft ESB Anypoint platform, on-premise and/or hosted in Cloudhub

Versions 6.0 and later make use of the .NET Framework 4.8 or later.
Version 5.4 make use of the .NET Framework 4.6.2 or later.
Versions before 5.4 make use of the .NET Framework 4.5.2 or later.

What Windows User Rights does the Nodinite Mule ESB Monitoring agent require?

The agent is installed as a Windows Service usually on the Nodinite application server. Virtual machines are supported.

What Cloudhub user rights does the Nodinite Mule ESB Monitoring agent require?

This section is applicable for version 4.x.

The Nodinite Mule ESB Monitoring Agent requires the Cloudhub Admin right. Apply this setting to each environment.
Cloudhub Admin is required
To enable monitoring of the Anypoint instance, apply the Cloudhub Admin right to each environment.

What Mule ESB User rights does the Nodinite Mule ESB Monitoring agent require?

This section is applicable for version 3.x.

The Nodinite Mule Monitoring Application (Zip file) needs to be installed into the Mule ESB server instance (repeat for each node to be monitored)

What Firewall settings does the Nodinite Mule ESB Monitoring agent require?

The Mule ESB Monitoring Agent has both inbound and outbound TCP-based communication:

  1. Between the Monitoring Service and the Mule ESB Monitoring Agent
  2. For version 3.x, between the Mule ESB Monitoring Agent and instances with the Nodinite Mule ESB Monitoring Application (install ZIP file)

The agent can be installed On-Premise using TCP/IP and/or in the Cloud using Service Bus Relaying.

graph LR subgraph "Nodinite Instance" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roNI(fal:fa-monitor-waveform Mule ESB Monitoring agent) roMonitoringService --> |8000/443| roNI end subgraph "Mule ESB (v3.x)" roSQLDB(fal:fa-random Instances with Nodinite Mule ESB Monitoring Application) roNI --> |8084, ...| roSQLDB end subgraph "CloudHub (v4.x)" roNI --> |443| roCH(fal:fa-cloud-arrow-up Anypoint CloudHub platform) end

1. Between the Monitoring Service and the Mule ESB Monitoring Agent

The following ports must be allowed on the Windows server where the agent is installed and running :

Port Name Inbound Outbound TCP UDP Comment
53 DNS The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts´ file)
443 TCP - - eu1.anypoint.mulesoft.com
443 TCP - - anypoint.mulesoft.com

Option 1 (Local network)

Port Name Inbound Outbound TCP UDP Comment
8000 RPC Communication is initiated by the Monitoring Service

Option 2 (Cloud/Hybrid)

Use Service Bus Relayed connections when Nodinite and the agent are on totally different networks.

Nodinite uses the same principle technique as the On-Premise data gateway, see 'Adjust communication settings for the on-premises data gateway' user guide.

Port Name Inbound Outbound TCP UDP Comment
443 HTTPS Secure outbound traffic
5671, 5672 Secure AMQP
9350 - 9354 Net.TCP

2. Between the Mule ESB Monitoring Agent and instances with the Nodinite Mule ESB Monitoring Application

This section is applicable for version 3.x.

Port Name Inbound Outbound TCP UDP Comment
8084 TCP Default

Only make changes to this value after consulting our support.

Next Step

Install Mule Monitoring Agent

Add or manage a Monitoring Agent Configuration
Monitoring
Administration