Prerequisites for Mule ESB Monitoring Agent

Unlock the full potential of your Mule ESB and MuleSoft Anypoint Platform with the Nodinite Mule ESB Monitoring Agent. This page outlines everything you need to get started—ensuring a smooth, secure, and efficient monitoring experience for your integration landscape.

Architecture overview: The Nodinite Monitoring Agent supports both on-premise and cloud/hybrid MuleSoft environments for maximum flexibility.

You can deploy the agent on-premise using TCP/IP for local network access, or in the cloud/off-site using Service Bus Relaying (MicrosoftServiceBusRelayingLink).

We recommend installing the agent close to the Nodinite Core Services. This guide focuses on local network setups, typically on the Nodinite application server.

Mule ESB Application (ZIP)

For Mule ESB version 3.x, use this option for on-premise environments. Mule version 4.x leverages public CloudHub APIs.

The Nodinite Mule ESB Monitoring Agent communicates with a Nodinite-specific Mule ESB Application that you install on each Mule Server Instance you wish to monitor. This application provides direct access to the Mule ESB run-time, ensuring comprehensive monitoring and insight.

Software Requirements

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

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.

• Local named account or domain account (preferred).
• Access and run-time rights
  • Follow the 'How to set logon as a Windows service right' user guide for detailed instructions.

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.

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.

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 :

• Option 1 - Local Network
• Option 2 - Cloud/Hybrid

Option 1 (Local network)

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.

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

This section is applicable for version 3.x.

Only make changes to this value after consulting our support.

Next Step

Install Mule Monitoring Agent

Related Topics

Add or manage a Monitoring Agent Configuration
Monitoring
Administration