- 3 minutes to read

Release Notes

Prerequisites for the JMX Monitoring Agent

This page describes the prerequisites to successfully install and run the Nodinite JMX Monitoring Agent to Monitor JVM CPU and Memory.

Software Requirements

The Nodinite JMX Monitoring Agent is a hosted Windows Service using NSSM and is usually installed on the JVM application server.

Product Version/Edition
Windows Server with IIS Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
ASP.NET Core Runtime v6 Hosting Bundle .NET 6
JVM OpenJDK
NSSM Download

For obvious reasons, JMX Monitoring must be enabled in the JVM Application to monitor.

Below is an example configuration with parameters to enable JMX Monitoring using an unauthenticated connection not using SSL on a Java Application:

java -Dcom.sun.management.jmxremote.port=5002
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false 
-jar $ACME_HOME/lib/AcmeApp_v1337.jar server start

Firewall

Depending on where you install the Nodinite JMX Monitoring Agent with respect to Nodinite Monitoring Service and your IBM MQ Queue managers you may need different firewall configurations on different servers. The following illustration shows the agent installed on its own server.

The Nodinite JMX Monitoring Agent has both inbound and outbound communication:

  1. Between the Nodinite Monitoring Service and the Nodinite JMX Monitoring Agent.
  2. Between the Nodinite JMX Monitoring Agent and the Java Spring Boot Application (Gateway).
  3. Between the Nodinite Java Spring Boot Application (Gateway) and the JVM Application.
graph LR subgraph "Nodinite Core Services Server" roMonitoringService(fal:fa-watch-fitness Monitoring Service) end subgraph "JMX Environment #1" roBoomiAtom1(fab:fa-java Java Virtual Machine) end subgraph "JMX Environment #2" roBoomiAtom2(fal:fa-atom Boomi Atom) end subgraph "Host with Agent" subgraph "Spring Boot" roGW(fal:fa-hard-drive JMX API Gateway
.jar package) end subgraph "IIS" roJMXAgent(fal:fa-monitor-waveform JMX Monitoring Agent) ---|8080|roGW end roGW --- |5002| roBoomiAtom1 roGW --- |5002| roBoomiAtom2 roMonitoringService ---|80,443, ...| roJMXAgent end

1. Between the Nodinite Monitoring Service and the Nodinite JMX 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)
Port Name Inbound Outbound TCP UDP Comment
80 RPC Communication is initiated by the Monitoring Service and the port in use depends on your IIS configuration
443 RPC Communication is initiated by the Monitoring Service and the port in use depends on your IIS configuration

If you use SSL or custom ports then additional ports needs to be opened

2. Between the Nodinite JMX Monitoring Agent and the Java Spring Boot Application (Gateway)

The communication is most likely local and Firewalls should normally not block this communication.

Port Name Inbound Outbound TCP UDP Comment
8080 TCP

3. Between the Nodinite Java Spring Boot Application (Gateway) and the JVM Application

Port Name Inbound Outbound TCP UDP Comment
5002 HTTPS Secure outbound traffic

The actual port in use depends on the JMX Monitoring configuration for your JVM Application.

Frequently asked questions

Additional solutions to common problems and the FAQ for the Nodinite JMX Monitoring agent exist in the Troubleshooting user guide.

Next Step

Installing the JMX Monitoring Agent
Add or manage a Monitoring Agent Configuration

JMX Monitoring Agent
Monitoring Agents
Administration