- 2 minutes to read

WSO2 Enterprise Integrator - Monitoring

Nodinite helps you monitor WSO2 Enterprise Integrator and WSO2 Micro Integrator from one place. The WSO2 Monitoring Agent connects by using JMX on port 9999 for WSO2 Enterprise Integrator and the Management API on port 9164 for WSO2 Micro Integrator. You can track Proxy Services, APIs, Sequences, Endpoints, Message Processors, and runtime health with a default polling interval of 30 seconds.

  • ✅ Monitor WSO2 Enterprise Integrator 6.x and 7.x together with WSO2 Micro Integrator 1.x and 4.x from one Monitoring Agent.
  • ✅ One Monitoring Agent can monitor unlimited services and servers when network access to JMX or the Management API is available.
  • ✅ Use Remote Actions to start, stop, restart, connect, and disconnect resources without opening the native administration tools.
  • ✅ Run the same monitoring design for Windows, Docker, and Kubernetes deployments.
  • ✅ Share service status with operations and business teams by using Monitor Views and alerting.

What the Monitoring Agent Watches

The Monitoring Agent polls WSO2 every 30 seconds by default. You can change the polling interval to any value between 15 and 120 seconds to balance faster alerting against additional load.

WSO2 Enterprise Integrator

For WSO2 Enterprise Integrator, the agent connects to JMX on port 9999 and can watch:

  • Proxy Services
  • APIs
  • Sequences
  • Endpoints
  • Message Processors
  • Carbon servers

WSO2 Micro Integrator

For WSO2 Micro Integrator, the agent connects to the Management API on port 9164 and can watch:

  • APIs
  • Sequences
  • Endpoints
  • Message Processors
  • Runtime health

Remote Actions

Remote Actions let authorized users respond quickly when a monitored resource needs intervention. Depending on the platform and permissions, you can:

  • Start or stop Proxy Services and APIs
  • Connect or disconnect Endpoints
  • Restart Carbon servers
  • Work from the Web Client instead of logging on to each WSO2 host

Monitoring Architecture

flowchart LR EI["WSO2 Enterprise Integrator
JMX : 9999"] --> AGENT["WSO2 Monitoring Agent"] MI["WSO2 Micro Integrator
Management API : 9164"] --> AGENT DOCKER["Docker deployments"] --> EI K8S["Kubernetes deployments"] --> MI AGENT --> POLL["Polling interval
15-120 seconds"] AGENT --> VIEWS["Monitor Views
business service status"] AGENT --> ALERTS["Alarm Plugins
Email, Teams, PagerDuty, webhook"] AGENT --> ACTIONS["Remote Actions
Start, Stop, Restart, Connect"] classDef runtime fill:#E3F2FD,stroke:#1565C0,color:#0D47A1,stroke-width:2px; classDef platform fill:#E8F5E9,stroke:#2E7D32,color:#1B5E20,stroke-width:2px; classDef agent fill:#FFF3E0,stroke:#EF6C00,color:#E65100,stroke-width:2px; classDef output fill:#F3E5F5,stroke:#7B1FA2,color:#4A148C,stroke-width:2px; class EI,MI runtime; class DOCKER,K8S platform; class AGENT agent; class POLL,VIEWS,ALERTS,ACTIONS output;

Next Steps

  • Troubleshooting Overview — Review common questions about credentials, licensing, Docker, Kubernetes, and detection speed.
  • POC — Start a proof of concept for WSO2 monitoring in your environment.
  • Monitor Views — Share WSO2 service status with business and operations teams.
  • Alarm Plugins — Send alerts to email, Teams, PagerDuty, or a webhook target.