API-gateway connectors

This page covers the legacy-API-gateway connectors other than IBM DataPower (which has its own page as the lighthouse for this tier): CA / Broadcom Layer7, Software AG / IBM webMethods, Perforce Akana, TIBCO Mashery, and Oracle API Gateway (OAG). They all reuse the DataPower pattern — read-only management-API discovery plus a transaction-log feed normalized into the canonical transaction shape.

A note on vendor names. This page names the API-gateway products SOAP-2-REST integrates with. That is interoperability information, not a comparison. Each capability below reflects what is implemented in the product.

---

At a glance

| Connector | Discovery | Traffic ingest | |---|---|---| | CA / Broadcom Layer7 | Restman REST management API | Transaction log feed (syslog TXN or JSON audit) | | Software AG / IBM webMethods | Mediator + API Gateway REST APIs | Transaction events (JSON over HTTP destination, or syslog) | | Perforce Akana | Akana Platform API | Transaction analytics (JSON webhook, or syslog) | | TIBCO Mashery | Mashery REST management API | Transaction analytics (real-time event webhook) | | Oracle API Gateway (OAG) | Management REST interface | Log export (syslog/access-log text or JSON log target) |

---

CA / Broadcom Layer7

• Discovery — the Gateway Management API (Restman) enumerates published services and their endpoints.
• Ingest — two surfaces are handled: a syslog TXN transaction-log line (legacy / all versions, via the log sink) and a JSON audit record (v10+ REST log sink / audit-log forwarder). Each carries request ID, service name, client IP, method, URI, status, and latency.

---

Software AG / IBM webMethods

• Discovery — the Mediator and API Gateway REST APIs enumerate the published APIs and their endpoints.
• Ingest — transaction events, emitted either as a JSON transaction record over an HTTP destination (all versions) or as JSON-in-syslog / key=value syslog from an alternate logging profile. Fields include transaction ID, API name, client IP, method, request URI, response code, and total time.

---

Perforce Akana

• Discovery — the Akana Platform API enumerates APIs and their endpoints.
• Ingest — Akana streams transaction analytics as a JSON event over an HTTP webhook destination (the primary path), with a syslog key=value form also supported. Fields include message ID, API name, operation, client IP, request verb/path, response code, and duration.

---

TIBCO Mashery

• Discovery — the Mashery REST management API enumerates services and endpoints.
• Ingest — Mashery streams transaction analytics, primarily via its real-time event webhook (JSON), available where the Real-Time Event Notification feature is enabled. Fields include the transaction UUID, service/endpoint names, request path, method, status code, total time, and client IP.

Mashery does not use syslog ingest. Its real-time signal is the analytics event webhook; a syslog key=value form is best-effort only. This matches what the platform exposes — see the note in the connectors overview.

---

Oracle API Gateway (OAG)

• Discovery — the OAG management REST interface enumerates the configured services and endpoints.
• Ingest — OAG exports traffic via its Open Traffic Event Log — either a syslog / access-log text format (TXN-style lines, all OAG / Vordel lineage) or a JSON HTTP log target (OAG 11g+ / 12c "Open Traffic Event" export). Fields include request ID, service name, client IP, HTTP method, request URI, status, and duration.

Oracle OAG ships in v1.0; its field-shape validation is finalized with the first customer running OAG. OAG's log field names and JSON schema vary across the product lineage (Vordel API Gateway → Oracle API Gateway 11g → 12c) and are governed by the operator's log-template configuration, so the connector accepts a wide set of token aliases and the exact field mapping is confirmed during first-customer onboarding.

---

What lands in the platform

All five connectors normalize their transaction records into the canonical shape — front-end URI, back-end URI, service name, client IP, gateway IP, HTTP method and status, latency, and optional payloads/headers where the gateway provides them. Records land in the unified traffic-log table tagged with the connector's gateway_type (layer7, webmethods, akana, tibco_mashery, oracle-oag), roll into the same aggregation tables that drive discovery, and feed the same observability and learned-example surfaces. Non-transaction events (policy changes, system alerts without a service/method/status signal) are recognized and skipped rather than ingested as traffic.

---

A note on body capture

These connectors are primarily transaction-level: they reliably capture the request metadata that discovery, dashboards, and SLO reports need. Request/response body capture depends on what each gateway's log surface exposes; for DataPower, a processing-policy log action captures bodies (see the DataPower page).

---

Scope

The legacy-API-gateway connectors target current and recent releases over HTTP/HTTPS. Several vendors' log field names are operator-configurable and confirmed against the first customer running that platform (notably Layer7 across firmware lines, Akana, and Oracle OAG). Modern, REST-native API management platforms are addressed by the generic-HTTP receiver today, with dedicated connectors on the post-GA roadmap — see the connectors overview.

---

All Specaria SOAP to REST docs