Working with SOAP
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.
Getting ready
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 use Orchestrator itself. Orchestrator has a SOAP as well as a REST interface.
The SOAP interface of Orchestrator is scheduled to disappear but at the time of writing this, we can still use it.
To add a SOAP-based service to the Orchestrator host, we need its WSDL address; for Orchestrator, this is https://[IP or FQDN Orchestrator]:8281/vco/vmware-vmo-webcontrol/webservice?WSDL.
How to do it...
Again, this recipe is split into different parts.
Adding a new SOAP client
Before we can execute any SOAP operations, we need to add the SOAP interface of a host to Orchestrator:
Open the Orchestrator Client and switch to the Design mode.
Make sure that you have imported the SSL Certificate...
