Executes a SOAP Request.
18.104.22.168 Added support for SOAP services that define output parameters
22.214.171.124 Added support for CustomBinding with MTOM or Binary encoding. Also added support for custom HTTP headers
126.96.36.199 Bug Fixes
188.8.131.52 Bug Fixes
184.108.40.206 Support for Web Services that don't generate a service contract with DataMember (or equivalent) attribute decorations on properties.
220.127.116.11 Added System.Data assembly reference to the list of supported references
18.104.22.168 Added support for byte array response data types
Type: Connection InputOutput
The URL to the endpoint.
The URL to the WSDL for the endpoint. This is typically the service endpoint with the text ?wsdl appended). If omitted, the Url property will be used to obtain the WSDL.
Default - Custom binding will not be used
Binary - Binary encoding will be specified in a custom binding
Mtom - MTOM encoding will be specified in a custom binding. Note that MTOM is only available in Full Trust environments and will therefore the Node must be run through a DropPoint
Indicates that all service operation properties should be included rather than only those decorated with DataContract (or equivalent) attributes. Try this option if you are not seeing certain properties in the Node Samples.
The Connection Property
Type: String Input
The SOAP Action to be performed - see Remarks.
Type: Xml Input
The XML request payload - see Remarks.
Type: Multiline Text Input
Provides a way to set custom HTTP headers on the request. Provide one header per row in the form
Type: Xml Output
The XML response payload - see Remarks.
Type: Xml Output
If the SOAP Service defines output parameters, they will be presented here.
The SOAP Request Node permits integration with any SOAP service. Begin by adding the SOAP Request Node and then creating a new Connection for the Node.
Provide the WSDL endpoint in the WsdlUrl property and the endpoint in the Url property, then click the Refresh Metadata button, finally test and save the Connection. The description of the SOAP service will now be stored within Flowgear against the Url you have specified.
Back on the Workflow, the Node Samples list will now contain a list of all transactions supported by the endpoint that was specified. Select the desired sample in order to begin formulating the request.