What's the difference between monitoring WSO2 EI vs. Micro Integrator?
WSO2 EI (6.x, 7.x): Monitors Proxy Services (SOAP/REST entry points), APIs, Sequences, Endpoints, Message Processors, Carbon servers. Agent connects via JMX (port 9999) + Carbon Management Console APIs (port 9443). Remote Actions: Start/Stop Proxy Services, Start/Stop APIs, Connect/Disconnect Endpoints, Restart Carbon servers. WSO2 MI (1.x, 4.x): Monitors APIs (primary artifact, replaces Proxy Services), Sequences, Endpoints, Message Processors, MI runtime (no Carbon Console—lightweight architecture). Agent connects via MI Management API (port 9164, REST-based)—must be enabled in deployment.toml: [management_api] enable = true. Remote Actions: Start/Stop APIs, Connect/Disconnect Endpoints (no Proxy Services—migrated to APIs in MI). Key difference: MI simplified architecture (no Carbon Console, API-centric, smaller footprint), EI legacy architecture (Carbon framework, supports both Proxy Services and APIs for backward compatibility).
Related Questions
See all FAQs: [Troubleshooting Overview][]