- 0 minutes to read

Release Notes

Prerequisites for the Nodinite Mule ESB Logging agent

This page describes the prerequisites to successfully install and run the Nodinite Mule ESB Logging Agent.

graph LR subgraph "Nodinite Instance" roNI(fal:fa-monitor-waveform Mule ESB Logging Agent) end subgraph "Anypoint instances in the cloud" roCloudhubAPI(fal:fa-cloud Cloudhub API)-->roIS(fal:fa-database Internal storage) roNI --> |API| roCloudhubAPI roFlow2(fal:fa-sitemap Flow) -->|Log4J| roIS end subgraph "Mule ESB instance on-premise" roFolder(fal:fa-folder Folder) roNI --> |SMB| roFolder roFlow(fal:fa-sitemap Flow) --> |Log4J| roFolder end

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

Verified Topic
Software Requirements
What folder rights does the Mule ESB Logging Agent require?
What Anypoint Cloudhub rights does the Mule ESB Logging Agent require?
What Windows User Rights does the Mule ESB Logging Agent require?
What Firewall settings are required for the Mule ESB Logging Agent?

Software Requirements

The Mule ESB Logging Agent is a Windows Service and is usually installed on the Nodinite application server.

Product
Windows Server Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.5 or later

Supported Versions

Cloud technologies are evolving fast and MuleSoft deprecates older versions of their API's every now and then. Nodinite will always support the API's supported by MuleSoft. This means you need to update Nodinite and our Mule ESB Logging Agent from time to time.

Make sure to subscribe to our Release Notes

What folder rights does the Mule ESB Logging Agent require?

If you are using Mule ESB on-premise and are using the Log4J file appender logged events are created on either local disk or a Windows File share (SMB). Logged events are consumed by the Mule ESB Logging Agent and therefore requires Read, Write and Change.

What Anypoint Cloudhub rights does the Mule ESB Logging Agent require?

  • The agent uses the MuleSoft Anypoint Cloudhub API to read logged events with tracked properties. Therefore the agent needs access rights provided by the Configuration.

What Windows User Rights does the Mule ESB Logging Agent require?

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

What Firewall settings are required for the Mule ESB Logging Agent?

The Mule ESB Logging Agent has both inbound and outbound communication:

  1. Between the Mule ESB Logging Agent and SMB File share or folder
  2. Between the Mule ESB Logging Agent and Cloudhub API
  3. Between the Mule ESB Logging Agent and the Log API
graph LR subgraph "Nodinite Instance" roNI(fal:fa-monitor-waveform Mule ESB Logging Agent) end subgraph "Anypoint instances in the cloud" roCloudhubAPI(fal:fa-cloud Cloudhub API)-->roIS(fal:fa-database Internal storage) roNI --> |443| roCloudhubAPI end subgraph "Mule ESB instance on-premise" roFolder(fal:fa-folder Folder or SMB File share) roNI --> |135-139, 445,... | roFolder end

1. Between the Mule ESB Logging Agent and SMB File share or folder

The Mule ESB Logging Agent uses the SMB protocol to access the remote file share. The following TCP ports must be open

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 with user-defined entries in the hosts file in each Windows server instance), review the following 'Microsoft' user guide
135-139 SMB Microsoft file sharing SMB
445 SMB Direct-hosted SMB traffic

For the full documentation, please visit the Microsoft [SMB: File and printer sharing ports should be open][FilePorts] page and Internet firewalls can prevent browsing and file sharing

2. Between the Mule ESB Logging Agent and Cloudhub API

Port Name Inbound Outbound TCP UDP Comment
443 HTTPS Secure outbound traffic with the Cloudhub API

3. Between the Mule ESB Logging Agent and the Log API

When Logging is enabled the Mule ESB Logging Agent requires one of the following outbound TCP ports to be open for access the Log Api (configurable)

Port Name Inbound Outbound TCP UDP Comment
80 HTTP default for HTTP
443 HTTPS default for HTTPS

Note

If the Mule ESB Logging Agent and the Log API is on the same server you should stick with HTTP for performance and information is not outside the server

Frequently asked questions

Additional solutions to common problems and the FAQ for the Nodinite Mule ESB Logging Agent exist in the Troubleshooting user guide.

About MULE ESB

  • Anypoint Studio 6 requires Requires Java8

Next Step

Add or manage a Monitoring Agent Configuration
Install the Mule ESB Logging Agent

Administration
Monitoring Agents