Web Services Error Handling in a Heterogenious Orchestration environment
2013-01-04 04:11 PM
If I understand the interface correctly; I can have a external entity generate a request to execute a workflow using a web services approach leveraging SOAP / WSDL. Execution of the request requires credentials, reference to the appropriate workflow and all required parameters. Assuming that the WSDL is correct, the interface will pass the request to the filter and the workflow execution will commence.
In the case that the web services request is improper, I'm certain there are several classes of error handling / messages that are visible to the requestor to help them understand the problem with their request. In the case of a successful WSDL request and the execution of the workflow abends, what would the requester receive? Would it be passed the full error message from the workflow automation environment, an error indicating that the WFA server has more detail, or would the context of the error condition be lost?
1 REPLY 1
Re: Web Services Error Handling in a Heterogenious Orchestration environment
2013-01-06 09:52 PM
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.
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:
<endTime>Jan 7, 2013 12:30:53 AM</endTime>
<errorMessage>Duplicate volume name vol1_comm.</errorMessage>
<jobType>Workflow Execution - Create a Cluster-Mode Volume 11</jobType>
<plannedExecutionTime>Jan 7, 2013 12:30:27 AM</plannedExecutionTime>
<startTime>Jan 7, 2013 12:30:31 AM</startTime>
Hope this helps. Please let us know if you do not find a correct error message in the SOAP response.