It's similar to the http transport, but the main difference is that you can pass some static (unchanging) content to the SOAP service to trigger certain functionality.
Lennox
Server: The URL of the SOAP webservice
SOAPAction: The HTTP header to indicate the intent of the request
UserName: (Optional) The username used in the Basic auth header
Password: (Optional) The password used in the Basic auth header
ProxyAddress: (Optional) The URL of the proxy server
ProxyUsername: (Optional) The authentication username for the proxy server
ProxyPassword: (Optional) The authentication password for the proxy server
ErrorMessageXPath: (Optional) The path for where errors are reported in the SOAP response, use an xpath string e.g. //Node/Error
Only works if there's a value in this setting, and the response does not contain <?xml version="1.0"
ReturnOnlySoapBody: (Optional)
If false, it returns the entire response body
If true, it returns everything under the namespace http://schemas.xmlsoap.org/soap/envelope/Body
What it does
{Short explanation of what it does}
Settings
Configuration Params tab: Static xml content to be sent with the SOAP request
What it does
Creates a SOAP request using the message attachment data as the request body
Settings
ResponseDeliveryTypeDetail: The name of the transport where the response of the SOAP service is sent to