What's the difference between monitoring WSO2 EI vs. Micro Integrator?
For Nodinite, very little: both run on the JVM, and the JMX Monitoring Agent monitors both the same way. Each WSO2 Enterprise Integrator or WSO2 Micro Integrator server is one Application Host with CPU and Heap Size thresholds (Configuration). What differs is how you enable JMX remote on the WSO2 side.
Comparison
| WSO2 Enterprise Integrator 6.x | WSO2 Micro Integrator (EI 7.x, MI 4.x) | |
|---|---|---|
| Runtime | Carbon-based server on the JVM | Lightweight runtime on the JVM |
| Built-in JMX | Carbon JMX server, RMIRegistryPort 9999 and RMIServerPort 11111 in carbon.xml, sign-in with a WSO2 admin-role user |
MBeans for local JConsole access; WSO2 recommends Prometheus for remote monitoring |
| Recommended for Nodinite | Standard JVM JMX remote options in the startup script (for example integrator.sh) |
Standard JVM JMX remote options in the startup script (for example micro-integrator.sh) |
| What Nodinite monitors | JVM CPU and heap memory | JVM CPU and heap memory |
Sources: WSO2 Carbon JMX-Based Monitoring, WSO2 EI 7.0 JMX Monitoring, WSO2 MI 4.2 JMX Monitoring. Verify ports and file names for your version.
The standard JVM options, including how to use a single port through firewalls, are in Enable JMX Remote Monitoring.
What Neither Covers
The JMX Monitoring Agent doesn't read WSO2 artifacts (proxy services, APIs, sequences, endpoints, message processors), doesn't use the Carbon management console or the Micro Integrator Management API, and can't start or stop artifacts. For service-level checks, use the Web Services Monitoring Agent.