Loading…
Loading…
SOAP-2-REST discovers and observes traffic at your gateway edge — the load balancer or API gateway that legacy SOAP traffic already flows through.
SOAP-2-REST discovers and observes traffic at your gateway edge — the load balancer or API gateway that legacy SOAP traffic already flows through. It ships with a suite of purpose-built connectors, plus a universal generic-HTTP receiver so that no customer is ever blocked.
A note on vendor names. This page names the gateway and load-balancer products that SOAP-2-REST integrates with. That is interoperability information and is expected here. It is not a comparison of SOAP-2-REST to any other product. Each capability below reflects what is implemented in the product.
A connector has up to two sides. A given vendor may expose one or both, and the platform uses whichever mechanism that platform actually exposes:
A documented client-IP injection snippet is provided per vendor so that consumer attribution is accurate at the edge.
Why mechanisms differ per vendor. Discovery and ingest are deliberately not one-size-fits-all. Some platforms expose a clean REST management API and stream syslog; others have no management REST API and are discovered by parsing config, or stream transaction analytics rather than syslog. The connector uses the right mechanism for each — see the per-vendor pages.
| Connector | Discovery | Traffic ingest |
|---|---|---|
| F5 BIG-IP | Edge config + sample X-Client-IP iRule | Syslog via relay |
| Citrix NetScaler / ADC | NITRO REST API | Syslog |
| HAProxy | Data Plane API (Enterprise) / stats socket (OSS) | Access-log feed |
| nginx | Management API (Plus) / config parsing (OSS) | Access-log feed |
| Kemp LoadMaster | REST API | Syslog / access logs |
| A10 Thunder ADC | aXAPI REST API | Syslog |
| Radware Alteon | Vision REST API | Syslog |
| Connector | Discovery | Traffic ingest | |---|---|---| | IBM DataPower | REST management interface | HTTP log target | | CA / Broadcom Layer7 | Restman REST management API | Transaction log feed | | Software AG / IBM webMethods | Mediator + API Gateway REST APIs | Transaction logs | | Perforce Akana | Akana Platform API | Analytics feed | | TIBCO Mashery | Mashery REST management API | Analytics feed | | Oracle API Gateway (OAG) | Management REST interface | Log export |
TIBCO Mashery and nginx do not use syslog ingest. Mashery streams transaction analytics through its API; nginx feeds traffic via its access log. The matrix reflects what each platform exposes — see the per-vendor pages for specifics.
For any edge not in this table, use the generic-HTTP receiver.
For any gateway, application server, or appliance not covered by a dedicated connector, the generic-HTTP receiver accepts traffic via a simple, documented JSON envelope. The operator points their edge's log or webhook target at the receiver and maps their fields once. If your edge can emit accessible HTTP traffic logs, it can feed SOAP-2-REST — so a customer running any gateway product is never blocked.
The dedicated connectors and the generic receiver share the same downstream pipeline: traffic
lands in a unified traffic-log table tagged with a gateway_type, is rolled up into the same
aggregation tables that drive discovery, and is curated into the same
learned examples.
If your traffic already flows through a modern, REST-native API management platform, your services are typically already exposed as REST — which usually means there is no SOAP-to-REST problem to solve at that edge. For the cases where legacy SOAP still flows through such a platform, the generic-HTTP receiver covers it. Dedicated first-class connectors for those platforms are on the post-GA roadmap.
The connector suite targets the mainstream 80% of estates: current and recent releases of mainstream gateways and load balancers, over HTTP/HTTPS. Each connector page states the minimum release line it supports. Out of scope for the standard product (handled as targeted engagements):
Keeping the supported set focused is deliberate: it keeps the shipped connectors dependable and well-tested rather than thinly spread across long-tail edge cases.