SOAP

You can access third-party web services that are hosted in the cloud or on-premises environment. You can also invoke a SOAP API in a flow service by using a SOAP connector.

The features supported for SOAP connectors are as follows:

• A SOAP connector implementation follows the WS-I Basic Profile 1.1 specification.
• SOAP connectors can be created by uploading a WSDL file or by using a valid WSDL URL that can be accessed over a network.
• SOAP connectors can be created with WSDLs that are annotated with WS-Security policy or policies.
• SOAP connectors with SOAP version 1.1 and 1.2 and Style/Use as Document/Literal and RPC/Literal (RPC/Encoded model is not supported for SOAP version 1.2).

The supported SOAP binding types are as follows:

• SOAP over HTTP
• SOAP over HTTPS
• Authentication type: HTTP basic token.

SOAP connectors have the restrictions as mentioned here:

• The WSDL and associated schemas must be accessible through a publicly or locally accessible URL.
• Only WSDLs with WS-Security policies are supported. Any other policies, for example, WS-Addressing, WS-Reliable Messaging, are not supported. If you create SOAP connectors with WSDLs having non-WS-Security policies, exceptions might appear while running flow services.
• Manual addition of WS-Security policies in a SOAP connector is not supported. SOAP connectors with WS-Security can only be created using WSDLs that already have WS-Security policies annotated.
• SOAP over JMS is not supported.
• Only basic authentication is supported. Other authentication types such as Digest, NTLM and Kerberos are not supported.
• File attachment or upload is not supported during service execution.