SOAP Adapter Capabilities

The SOAP Adapter can consume an external SOAP API in an integration in Oracle Integration. The message received from Oracle Integration can be passed as payload to an external SOAP endpoint by the SOAP Adapter. Any response received from the endpoint can be sent to the next action in the integration for further processing.

The SOAP Adapter can expose inbound SOAP endpoints for accepting SOAP requests that are addressed to a specific URI. The request body is passed to the next activity present in the integration as the message payload, along with the SOAP and HTTP headers.

Note:

The SOAP Adapter treats all endpoints as they are exposed. The SOAP Adapter does not filter or change any of the APIs exposed by the application to which you are connecting. If there is a native adapter for the application to which you are connecting, use that adapter instead. If you choose to use the SOAP Adapter instead of the native adapter, the API restrictions and deprecation policies apply as specified in the respective application’s documentation. To connect to the Oracle HCM Cloud SOAP APIs, see Oracle HCM Cloud Adapter Capabilities.

The SOAP Adapter provides the following capabilities:
  • SOAP Adapter capabilities when configured as a trigger:

    Important:

    Integrations exposed as SOAP APIs (using a SOAP Adapter-specific connection configured as a trigger) cannot accept attachments.
    • Ensures that an incoming structured payload (XML) from a client does not exceed 10 MB in size. If the size of the payload exceeds 10 MB, an HTTP error code message is returned to the client.

    • Ensures that an incoming unstructured payload (MTOM) from a client does not exceed 512 MB in size. If the size of the payload exceeds 512 MB, an HTTP error code message is returned to the client.

    • Allows configuring only HTTPS protocol-based SOAP endpoints for accepting incoming SOAP requests.

    • Supports configuring the inbound SOAP endpoints using the following security policies: HTTP Basic Authentication, WS-Username token-based authentication, OAuth 2.0, and Security Assertion Markup Language (SAML) (see SAML Policy Security Support in the Trigger (Inbound) Direction and OAuth 2.0 Policy Security Support in the Trigger (Inbound) Direction).

    • Supports accessing of standard and custom SOAP/HTTP header properties present in the incoming SOAP request and making them available as part of an Oracle Integration message for any processing in subsequent actions (see Support for Adding Standard and Custom SOAP and HTTP Headers).

    • Enables you to implement the following message exchange patterns on the inbound SOAP endpoint: synchronous request/response, one-way request, and asynchronous request with callback support.

    • Supports TLS server v1.2 in the trigger (inbound) direction.

  • SOAP Adapter capabilities when configured as an invoke:

    • Allows invocation of an HTTPS protocol-based external SOAP endpoint, thereby encrypting the communications using transport layer security (TLS) (see Transport Layer Security Version Support).

    • Allows invocation of HTTP protocol-based SOAP endpoints.

    • Allows invocation of external SOAP endpoints that are unprotected and protected using HTTP Basic Authentication and WS-Username token-based authentication.

    • Allows invocation of external SOAP endpoints hosted on TLS servers v1.1 and v1.2.

    • Supports invocation of two-way, SSL-enabled external SOAP endpoints (see Two-Way SSL Support for Outbound Connections).

    • Supports configuration of standard and custom SOAP/HTTP header properties available to the outbound SOAP request (see Support for Adding Standard and Custom SOAP and HTTP Headers).

    • Supports invocation of external SOAP endpoints that implement the following message exchange patterns: synchronous request/response, one-way request, and asynchronous request with callback support (using WS-Addressing) (see Asynchronous Callback Response Support in the Invoke (Outbound) Direction).

    • Supports propagation of the subject between co-located modules (for example, integrations to processes and processes to integrations). This enables the module to provide custom features and restrictions based on the current subject. When an integration invokes another process or integration, the subject is propagated using a JWT token. Similarly, when a process invokes an integration, it propagates the subject using JWT (see Support for Invoking Co-located SOAP Endpoints).

    • Supports the dynamic discovery of endpoints. This is useful for scenarios in which the endpoint invoked by the SOAP Adapter must be dynamically configured based on runtime logic (see Support for Dynamic Endpoints).

    • Supports the following:

      • Sending binary and nonbinary content as an MTOM attachment (up to 1 GB) as part of a request message while invoking external SOAP APIs.

      • Receiving binary and nonbinary content as an MTOM attachment (up to 1 GB) as part of a response message while invoking external SOAP APIs.