Hi David,
Yes, your understanding is right about using a web services approach leveraging SOAP / WSDL.
Most of the cases of wrong WSDL requests have been handled.
In the case of a successful WSDL request and if the workflow fails for some reason as in the example below, the <errorMessage> attribute will show the exact error message as returned from WFA. This would be the same as the GUI message.
Steps:
1.Workflow to create volumes
2.Giving a volume name which already exists on the cluster
3.Marking the workflow to not to check the reservation table and db
4.When the workflow executes, after it contacts the cluster, it returns a duplicate volume message
Please find below the SOAP response for the job status of the failed workflow:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body>
<ws:getJobStatusResponse xmlns:ws="http://ws.wfa.netapp.com/">
<return>
<endTime>Jan 7, 2013 12:30:53 AM</endTime>
<errorMessage>Duplicate volume name vol1_comm.</errorMessage>
<jobStatus>FAILED</jobStatus>
<jobType>Workflow Execution - Create a Cluster-Mode Volume 11</jobType>
<plannedExecutionTime>Jan 7, 2013 12:30:27 AM</plannedExecutionTime>
<returnParameter>
<name>ClusterName</name>
<value>wfa-cluster</value>
</returnParameter>
<returnParameter>
<name>AggregateName</name>
<value>Test_aggregate</value>
</returnParameter>
<returnParameter>
<name>VolumeName</name>
<value>vol1_comm</value>
</returnParameter>
<returnParameter>
<name>NodeName</name>
<value>wfa-cluster-01</value>
</returnParameter>
<scheduleType>Immediate</scheduleType>
<startTime>Jan 7, 2013 12:30:31 AM</startTime>
</return>
</ws:getJobStatusResponse>
</env:Body>
</env:Envelope>
Hope this helps. Please let us know if you do not find a correct error message in the SOAP response.
-Sharu