Web service
Last updated
Was this helpful?
Last updated
Was this helpful?
The Web Service Connector can be used to consume SOAP based web services. It can also be used to consume WCF services that are not based on SOAP, such as net.pipe and net.tcp bindings.
Create/update Connector In this section the WSDL that describes the web service is specified and there is also a button for creating the actual connector. Before a connector can be created it must have a Name specified. You must provide a valid URI to a WSDL and start Create/update before the connector configuration can be saved. The URI can refer to a file if there are no external references in the WSDL. Note that the file path is relative to Flow Server. If the URI refers to an http endpoint (typically it is) you can, if needed, provide user and password (and optionally domain) before starting Create/update. Do not update the connector unless the remote service has changed.
Runtime configuration After the connector has been created a basic configuration is stored in this section.
Client credentials Setups the client credentials to use when communicating with remote service.
The Web Service Connector is designed to work with Document style WSDL. However, it is important to note that there is another type of WSDL definitions known as RPC (Remote Procedure Call). Some customers have encountered issues when working with RPC style WSDL definitions. This incompatibility can result in in failures in message processing, incorrect data mappings, or runtime errors due to the mismatch between the expected and provided message formats.
To understand if a WSDL is RPC style or Document style requires a closer look at the WSDL definition.
RPC Style - Structure of the soap:body element typically uses use="encoded" and specifies the encoding style
Document Style - Structure of the soap:body element typically uses use="literal"
