SBM Orchestration Guide → Orchestration Procedures → Using the Scope, Throw, and Compensate Steps to Handle Faults From Web Services → Using the Scope Step → Tutorial: Practicing With the Scope Step to Handle Generic Web Service Faults
Prerequisites:
You performed the steps in Tutorial: Creating An Empty Synchronous Orchestration Workflow to Handle Generic Web Service Faults Using the Scope Step.
In this exercise, you use a Scope step in the GenericFaultOWF orchestration workflow.
After you complete the steps in this exercise, your orchestration workflow should look like the one in the following figure:
Figure 1. GenericFaultOWF
Later, when you run the GenericFaultApp Project, you will alter this orchestration workflow so it returns an error message in the Description field.
To use the Scope step in an orchestration workflow to handle generic Web service faults:
In steps 11 through 24, you configure this step to decide between two possible outcomes: the user is valid or the user is not valid.
Be sure to include the quotation marks.
Be sure to include the quotation marks.
Be sure to include the quotation marks.
The following two warning messages appear in the Validation Results:
The required DefaultElement 'GenericFaultOWF\Message' is not mapped or defaulted in 'GenericFaultOWF'
This message warns you that you did not provide a value for the Message working data element. You can ignore the message, or you can set the default value to 0 (zero) to prevent the message from appearing.
Compensation handler is empty.
You can ignore this message, because a compensation handler is not required for this orchestration workflow.
See Step 6: Publish the Process App and Step 7: Deploy the Process App for instructions.
Copyright © 2007–2016 Serena Software, Inc. All rights reserved.