SBM Orchestration Guide → Orchestration Procedures → Using the Scope, Throw, and Compensate Steps to Handle Faults From Web Services → Using the Scope Step → Tutorial: Creating An Empty Synchronous Orchestration Workflow for the Scope Step to Handle Named Faults

Tutorial: Creating An Empty Synchronous Orchestration Workflow for the Scope Step to Handle Named Faults

Prerequisites:

You performed the steps in Tutorial: Creating a Practice Process App for Fault Handling.

In this exercise, you add an empty synchronous orchestration workflow to the FaultHandlingOrch in the FaultHandlingProcApp.

To create an empty orchestration workflow that handles named Web service faults:

  1. In App Explorer, under Application Workflows, click NamedFaultAWF.
  2. In the application workflow editor, right-click the GetTickerSymbol transition, and then select Show Actions.
  3. On the Actions tab of the Property Editor, click New.

    The Action Wizard opens and asks, "Which type of action do you want to execute?"

    Under Step 1, Orchestration Workflow should be selected.

  4. Under Step 2, click the and continue executing (asynchronous) link, and then select and wait for reply (synchronous).
  5. Click Next.

    The Action Wizard asks, "When do you want to call the orchestration workflow?"

  6. Under Step 1, select After.

    Step 2 should read Invoke an orchestration workflow and wait for reply (synchronous), after this transition occurs.

  7. Click Next.

    The Action Wizard asks, "Which orchestration workflow do you want to call?"

  8. Under Step 1, select (Add new workflow...).

    The Event With Reply dialog box opens.

  9. In the Name box, type NamedFaultWFWR1.
  10. In the Workflow box, type NamedFaultOWF1.
  11. In the Fields used by event list, select the Title check box.
  12. In the Fields returned by event list, select the Description and Title check boxes.
  13. Click OK.

    Under Step 1, NamedFaultWFWR1 is selected on the menu and EventNoticeWithReply appears in the list. Step 2 now reads Invoke an orchestration workflow and wait for reply (synchronous), after this transition occurs, Call NamedFaultWFWR1.

  14. Click Finish.

    NamedFaultWFWR1 appears below GenericFaultWFWR under Orchestration Links, and NamedFaultOWF1 appears below GenericFaultOWF under Orchestration Workflows in App Explorer.

Related Topics

Tutorial: Creating a Practice Process App for Fault Handling

Copyright © 2007–2016 Serena Software, Inc. All rights reserved.