SOAP Request 2

Executes a SOAP Request.

Version History

4.0.0.0 Initial release for new platform
4.0.0.1 Bug fixes
4.0.0.2 Added support for BindingName
4.0.0.3 Misc bug fixes
4.0.0.4 Fixed "Path is not of a legal form" bug when invoked at a DropPoint
4.0.0.5 More bug fixes
4.0.0.6 Still bug fixes
4.0.0.7 More bug fixes to stabilize loading of samples at both DropPoint and in-cloud
4.0.0.8 Bug fixes for DropPoint execution
4.0.0.9 Even more bug fixes for DropPoint execution
4.0.1.1 Added support for NTLM Authentication

Properties

Connection

Type: Connection InputOutput
The Connection Property

Url
Type: String
The URL to the endpoint.

WsdlUrl
Type: String
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.

DontFilterPropertiesByAttribute
Type: Boolean
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.

ServiceName
Type: String
When the endpoint hosts multiple services, provide the name of the service you want the connection to use. Normally this Property can be left blank. If the endpoint defines multiple services, an error listing the available names will be thrown when attempting to obtain samples or invoke the Node. Place the name of one of these services in this field to enable the Node to target the correct one.

BindingName
Type: String
When provided, indicates the name of the binding that should be selected (as defined in the WSDL). This can be left blank if there is only one binding. If multiple bindings are present and this is left blank, an error will be thrown listing the available bindings.

CustomBindingMessageEncoding
Type: List

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

AuthenticationModel
Type: List

Username
Type: String
The Username to be passed as part of a Client Credential. e.g. for NTLM would be domain\username

Password
Type: String
The Password to be passed as part of a Client Credential.

Action

Type: String Input
The SOAP Action to be performed - see Remarks.

RequestXml

Type: Xml Input
The XML request payload - see Remarks.

CustomHeaders

Type: Multiline Text Input
Provides a way to set custom HTTP headers on the request. Provide one header per row in the form Header-Name: Value

ResponseXml

Type: Xml Output
The XML response payload - see Remarks.

RequestOutputXml

Type: Xml Output
If the SOAP Service defines output parameters, they will be presented here.

Remarks

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.