This recipe focuses on the interaction between Orchestrator and a SOAP-based server. We will learn how to add a SOAP host to Orchestrator and execute SOAP operations.
We need a host that can present SOAP operations for Orchestrator to use. If you don't have a SOAP host that you can access, you can follow our example.
Orchestrator's SOAP API has been retired and is not available anymore.
To add a SOAP-based service to the Orchestrator host, we need its WSDL address.
For our example, we will use http://www.webservicex.net to test our SOAP plugin. The WSDL we will use is http://www.webservicex.net/globalweather.asmx?WSDL .
Again, this recipe is split into different parts.