Prerequisites for the Nodinite Boomi Monitoring agent
Prepare your environment for seamless, secure monitoring of Boomi integrations with Nodinite. This page details everything you need to install and run the Boomi Monitoring Agent, including software, network, firewall, and user rights requirements.
✅ Ensure compatibility with modern cloud and on-premise setups
✅ Meet all software and network prerequisites for reliable monitoring
✅ Secure your environment with proper firewall and user rights settings
✅ Benefit from proactive alerts and streamlined administration
You will learn how to:
- Install and configure the Boomi Monitoring Agent for Nodinite
- Set up required software and network access
- Apply best practices for security and administration
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 'Azure Relay FAQs').
Tip
We recommend that you keep this agent close to the installation of Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server)
Software Requirements
The Nodinite Boomi Monitoring Agent is a Web Application installed in IIS, and is usually installed on the Nodinite application server.
| Product | Comment |
|---|---|
| ASP.NET Core | ASP.NET Core 8.0 New 1.0.23 |
Versions 1.0.0.14 - 1.0.0.22 make use of the .NET 7 Versions prior to 1.0.0.14 make use of the ASP.NET 5
You must use a modern browser like Edge or Chrome. Add /swagger last in the address to test it out.
You must have ASP.NET Core installed.
Important
You must download and install the ASP.NET hosting bundle.
- Host ASP.NET Core on Windows with IIS
- ASP.NET Core 7.0 Runtime (v7.0.0) - Windows Hosting Bundle Installer!
Supported Versions
Cloud technologies are evolving fast and Boomi deprecates older versions of their API's now and then. Nodinite will always support the API's supported by Boomi. This means you need to update Nodinite and the Boomi Monitoring Agent from time to time.
Make sure to subscribe to the Release Notes
What AtomSphere User rights does the Nodinite Boomi Monitoring agent require?
- The agent uses the Atomsphere API to manage information and to modify the state of your Boomi Environment(s). Therefore the account used must be Administrator.
Role based security using least privileges are being evaluated, stay tuned.
What Windows User Rights does the Nodinite Boomi Monitoring agent require?
The agent is installed as a Web Application within the IIS, usually on the Nodinite application server. Virtual machines are supported.
- The App Pool can be configured to run with limited access rights.
- The built-in
ApplicationPoolIdentityIdcan be used- During the installation, you must add the full control right for the IIS App Pool assigned to the Web Application.
The specific settings are detailed on the Install the Nodinite Boomi Monitoring agent user guide.
- The built-in
What Firewall settings are required for the Nodinite Boomi Monitoring agent?
The Boomi Monitoring Agent has both inbound and outbound communication:
- Between the Nodinite Monitoring Service and the Nodinite Boomi Monitoring Agent
- Between the Nodinite Boomi Monitoring Agent and Atomsphere API
1. Between the Monitoring Service and the Boomi 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 | Nodinite Version | Comment |
|---|---|---|---|---|---|---|---|
| 53 | DNS | All | The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts file) |
And further with 'Option 1' or 'Option 2' as documented next:
Option 1a (Nodinite v7 - IIS hosted on local network)
| Port | Name | Inbound | Outbound | TCP | UDP | Nodinite Version | Comment |
|---|---|---|---|---|---|---|---|
| Custom | HTTP/HTTPS | v7 | Agent IIS site port (configured during installation in the Portal). Only required if agent is on a remote IIS server |
Note
Nodinite v7 IIS Hosting: When agents are hosted in IIS on the same server as the Nodinite application (typical installation), firewall rules are not required between the Monitoring Service and the agent. The custom port is assigned during installation via the Nodinite Portal and only needs to be opened if the agent is hosted on a remote IIS Windows Server.
Option 1b (Nodinite v6 and earlier - Windows Service on local network)
| Port | Name | Inbound | Outbound | TCP | UDP | Nodinite Version | Comment |
|---|---|---|---|---|---|---|---|
| 8000 | RPC | v6 and earlier | Communication is initiated by the Monitoring Service. Only used with legacy MSI installer on remote Windows servers |
Note
Nodinite v6 Legacy: Port 8000 is only used when agents have default installations on remote Windows servers using the legacy MSI installer. This port is not required for Nodinite v7 IIS-hosted agents.
Option 2 (Cloud/Hybrid - All versions)
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.
The following ports must be open for outbound communication with '*.servicebus.windows.net' from both on-premise and off-site (Nodinite Windows Server(s) and where the agent is installed):
| Port | Name | Inbound | Outbound | TCP | UDP | Nodinite Version | Comment |
|---|---|---|---|---|---|---|---|
| 443 | HTTPS | All | Secure outbound traffic | ||||
| 5671, 5672 | Secure AMQP | All | |||||
| 9350 - 9354 | Net.TCP | All |
2. Between the Boomi Monitoring Agent and Boomi AtomSphere API
Server types: Agent Server (Boomi Monitoring Agent), Boomi Cloud (AtomSphere API endpoints).
Boomi AtomSphere API Connection (Agent → Boomi Cloud)
The agent connects to the Boomi AtomSphere API to retrieve monitoring data for Boomi Atoms and integrations.
| Direction | Source | Destination | Protocol | Port(s) | Purpose | Notes |
|---|---|---|---|---|---|---|
| Outbound | Agent Server | Boomi Cloud (AtomSphere API) | TCP | 443 (HTTPS) | AtomSphere API communication | Monitor Boomi Atoms and integrations |
| Inbound | Boomi Cloud | Agent Server | TCP | 443 (HTTPS) | Response traffic | Allowed automatically by stateful firewalls |
Tip
Boomi API Endpoints: You must whitelist the following Boomi AtomSphere API addresses on port 443:
For a complete list of Boomi hostnames and IP addresses, review the Boomi documentation - Hostnames and IP Addresses for Platform.
Tip
Boomi Authentication: The agent requires an Administrator account to access the AtomSphere API. Role-based security with least privileges is being evaluated for future releases.
Tip
API Versioning: Boomi deprecates older API versions periodically. Ensure you update Nodinite and the Boomi Monitoring Agent regularly. Subscribe to Release Notes for updates.
Note
No Inbound Rules on Boomi Cloud: Boomi AtomSphere API is a cloud service accessed outbound from the Agent Server. No inbound firewall rules are required on the Boomi side.
Note
DNS Resolution: All servers (Agent Server) require outbound access to DNS on TCP/UDP port 53 for name resolution. This is already listed in section 1 and applies universally. You can optionally solve this using entries in the local
hostsfile on each server.
Important
Stateful Firewalls: Most modern Windows Firewall implementations are stateful, meaning inbound response traffic for established outbound connections is automatically allowed. The inbound rules listed above are primarily for reference and troubleshooting scenarios where stateful inspection may be disabled or restricted.
Frequently asked questions
Additional solutions to common problems and the FAQ for the Nodinite Boomi Integrations Monitoring Agent exist in the Troubleshooting user guide.
Next Step
Add or manage a Monitoring Agent Configuration
Install the Nodinite Boomi Monitoring agent