I cross posted on the forum as well. Yes, it is possible (and common use case) to trigger a vCO workflow via WebServices. So, if there is ability to call a web services from VSM, then there should not be any stoppers for this use case.
More about vCO Web Services info:
Documentation about vCO web services could be found here in the part "8. Developing a Web Services Client" :
Examples of how to call a vCO web service could be found here:
Once you download the zip file, go "vco-samples-4.1.0-776/WebService/WebServiceSample/src/com/vmware/client/LaunchWorkflowWithInput.java" for concrete example of calling workflows with input parameters.
Please, let us know if this would work for your case and whether you find any issues.
the vCO also delivers an API (WSDL). With this it is possible to start, trigger and give inputs to the workflows. As shown by Igor there is a special part in the vCO developers guide (Building a simple webclient) which shows the different commands. It is really easy to start a workflow, get the token and ask for the token status (with the token id)...
In the past i wrote a .NET example:
If you are looking for an example in Powershell:
There is also a way to call single actions directly, see the discussion here:
The third way (hardest, but maybe best integration): Wirte a VSM-plugin for vCO, which uses the vCO-Triggers to monitor vSM.
edit: forgot the smilie for the third way
Nachricht geändert durch tschoergez