- 4 minutes to read

Release Notes

Prerequisites for the Nodinite Boomi Monitoring agent

This page describes the prerequisites to successfully install and run the Nodinite Boomi Monitoring Agent.

graph LR subgraph "Nodinite instance" roNI(fal:fa-code-commit Boomi Monitoring agent) --- roMonitor[fal:fa-monitor-waveform Monitoring] end subgraph "Boomi Integrations Accounts" roMonitor --- roEnv(fal:fa-cloud Environments) roEnv --- roAtoms(fal:fa-atom Atoms) roAtoms ---roPx((fal:fa-gears Processes)) 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 installation of Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server)

Verified Topic
Software Requirements
What Atomsphere rights does the Nodinite Boomi Monitoring agent require?
What Windows User Rights does the Nodinite Boomi Monitoring agent require?
What Firewall settings are required for the Nodinite Boomi Monitoring agent?

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.

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.
    Account 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.

What Firewall settings are required for the Nodinite Boomi Monitoring agent?

The Boomi Monitoring Agent has both inbound and outbound communication:

  1. Between the Monitoring Service and the Boomi Monitoring Agent
  2. Between the Boomi Monitoring Agent and Atomsphere API
graph LR subgraph "Nodinite Instance" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roNI(fal:fa-monitor-waveform Boomi Monitoring agent) roMonitoringService --> |8000/443| roNI end subgraph "Boomi Integrations Accounts" roAzureAPI(fal:fa-cloud Atomsphere API)---roLA(fal:fa-clouds Your Boomi Atoms) roNI --> |443| roAzureAPI end

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 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)

And further with 'Option 1' or 'Option 2' as documented next:

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.

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 Comment
443 HTTPS Secure outbound traffic
5671, 5672 Secure AMQP
9350 - 9354 Net.TCP

2. Between the Boomi Monitoring agent and AtomSphere API

You must whitelist the addresses usually using port 443 according to this article, usually the following:

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

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

Monitoring Agents
Administration