Which WSO2 API Manager versions are supported?
WSO2 supports each product version for at least three years from release, and release lines introduced from March 2024 for at least seven. Its matrix lists API Manager 4.3 to 4.7 and 4.1 as available, 4.2 as deprecated to 22 March 2027, and 4.0 and 3.2 as extended life only. AceMQ supports any version WSO2 has released.
Who answers when WSO2 fails in production, and how fast?
A named AceMQ senior engineer answers within 15 minutes, 24/7, when the WSO2 gateway or identity layer fails in production. Lower severities get a first response within 1 hour, 4 hours or the next business day. The engineer who takes the first call stays on the case, and every P1 ends with a written root-cause analysis.
How does a WSO2 consulting engagement with AceMQ start?
A WSO2 engagement starts with a free consultation with a senior engineer, booked in our reply within 1 hour. A platform assessment of 1 to 2 weeks follows, covering topology, gateway and key manager settings, mediation sequences, registry state and how deployments move between environments. Written findings and a plan arrive within a week.
What does moving from Enterprise Integrator to Micro Integrator involve?
Micro Integrator is a lighter, container-first runtime with its own deployment and configuration model, so it is not a drop-in replacement. Sequences and proxy services largely carry over, but registry use, tooling and older analytics or business process components need rework. AceMQ inventories artifacts, migrates in batches and runs both in parallel.
How risky are WSO2 major version upgrades?
Riskier than most teams expect, because configuration models and component layouts change between major versions and databases need migration scripts. AceMQ treats an upgrade as a migration: new version alongside the old, database migration against a copy, API artifacts re-imported, validation on real traffic, then cutover with a rollback path.
Why is throttling inconsistent across our WSO2 gateway nodes?
The nodes are deciding independently. WSO2 distributes throttle decisions through the traffic manager, and if its event topic does not reach every gateway, each one falls back to what it sees locally, so the total scales with node count. AceMQ checks traffic manager connectivity from every node first, as the fastest test.
Why does token validation get slower as load rises?
Usually the gateway token cache is disabled or expiring too fast, so each request becomes a synchronous check against the key manager. Identity Server's database then becomes the bottleneck, not the gateway. A cache expiry matched to token lifetime and a datasource sized for real concurrency normally restore latency.
We have a WSO2 subscription. Why add AceMQ?
A WSO2 subscription is the source of product fixes and WSO2 Updates, and you keep it for those. It does not give you an engineer who runs your deployment: the gateway cluster, key manager database, custom mediators and Kubernetes platform. AceMQ covers that layer and hands WSO2 a diagnosed case when a fault is a product defect.
Can we work with AceMQ on WSO2 without a long contract?
Yes. AceMQ works on WSO2 in two ways: ad hoc engagements for a defined piece of work, such as a health check, an upgrade or an incident, or an annual partner engagement that covers 24/7 support, proactive reviews and named engineers. Many teams start ad hoc and move to an annual partnership once the first engagement is done.
How much does AceMQ WSO2 support or consulting cost?
Every AceMQ proposal is tailored to your requirements: your WSO2 environment, the SLA you need, the hours of cover and the scope of work. Most contracts run $24,000–72,000 a year, depending on the SLA, the scope and how WSO2 is deployed, with aggressive discounts when several technologies share one contract. Request a quote and AceMQ replies within 1 hour.
Kubernetes
Kafka
PostgreSQL
Docker
Azure
