SBM Orchestration Guide → Orchestration Procedures → Using the Scope, Throw, and Compensate Steps to Handle Faults From Web Services → Tutorial: Creating a Practice Process App for Fault Handling

Tutorial: Creating a Practice Process App for Fault Handling

In this section, you create a new process app named FaultHandlingProcApp. You will use this process app to practice using the Scope, Throw, and Compensate steps.

You can run the process app at any time after you create an application workflow and deploy the process app. To run the application workflow (project), follow the instructions in the relevant sections of Running the Fault Handling Process App.

To create the practice process app:

  1. Start SBM Composer.
  2. Click the Composer button, and then click New.

    The Create New Process App dialog box opens.

  3. Click Application Process App, and then click Create.

    The Configure Process App dialog box opens.

  4. In the Process app name and Application name boxes, type FaultHandlingProcApp, and then click OK.
  5. In App Explorer, click the All Items filter.
  6. Under Tables, click FaultHandlingProcessApp.
  7. In the Property Editor, change the Name to FaultHandlingPTable, and then press the Tab key.

    PTable stands for primary table.

  8. In the System Fields section of the Table Palette, drag and drop a Description field onto the FaultHandlingPTable (Primary) tab.

    The Description field is added to the table, in alphabetical order. The Description field will also be added to the state and transition forms. Information that is returned by the orchestration workflows you create in this section is displayed in this field and in the Title field.

  9. In App Explorer, click FaultHandlingProcessApp.
  10. On the FaultHandlingProcApp tab, change the Logical name to FaultHandlingApp, and then press the Tab key.
  11. Perform the following steps to create GenericFaultAWF:
    1. In App Explorer, under Application Workflows, click FaultHandlingProcApp.
    2. On the General tab of the Property Editor, change the Name to GenericFaultAWF, and then press the Tab key.
    3. In the application workflow editor, click the Submit transition.
    4. On the General tab of the Property Editor, change the Name to VerifyUser, and then press the Tab key.
    5. Click the New state.
    6. On the General tab of the Property Editor, change the Name to IsUserValid, and then press the Tab key.
  12. Perform the following steps to create NamedFaultAWF:
    1. In App Explorer, right-click Application Workflows, and then click Add New Workflow.

      Under Application Workflows, FaultHandlingApp Workflow should be selected.

    2. On the General tab of the Property Editor, change the Name to NamedFaultAWF, and then press the Tab key.
    3. In the application workflow editor, click the Submit transition.
    4. On the General tab of the Property Editor, change the Name to GetTickerSymbol, and then press the Tab key.
    5. Click the New state.
    6. On the General tab of the Property Editor, change the Name to TickerSymbol, and then press the Tab key.
    7. In the States section of the Workflow Palette, drag Active onto the application workflow editor and drop it to the right of the TickerSymbol state.
    8. Change the Name to BuyRating, and then press the Tab key.
    9. In the Transitions section of the Workflow Palette, drag Regular onto the TickerSymbol state, release the mouse button, and then click BuyRating.
    10. Change the name of the Transition to GetBuyRating, and then press the Tab key.
  13. Perform the following steps to create ThrowAWF:
    1. In App Explorer, right-click Application Workflows, and then select Add New Workflow.

      FaultHandlingAppWorkflow appears under NamedFaultAWF.

    2. Click FaultHandlingAppWorkflow.
    3. On the General tab of the Property Editor, change the Name to ThrowAWF, and then press the Tab key.
    4. In the States section of the Workflow Palette, drag Active onto the orchestration workflow editor, and drop it to the right of the New state.
    5. On the General tab of the Property Editor, change Name to TickerSymbol.
    6. In the Transitions section of the Workflow Palette, drag Regular onto the New state, release the mouse button, and then click the TickerSymbol state.
    7. On the General tab of the Property Editor, change the Name to GetTickerSymbol.
  14. Perform the following steps to create CompensateAWF:
    1. In App Explorer, right-click Application Workflows, and then select Add New Workflow.

      FaultHandlingAppWorkflow appears under ThrowAWF.

    2. Click FaultHandlingAppWorkflow.
    3. On the General tab of the Property Editor, change the Name to CompensateAWF, and then press the Tab key.
    4. In the States section of the Workflow Palette, drag Active onto the orchestration workflow editor, and drop it to the right of the New state.
    5. On the General tab of the Property Editor, change Name to TickerSymbol.
    6. In the Transitions section of the Workflow Palette, drag Regular onto the New state, release the mouse button, and then click the TickerSymbol state.
    7. On the General tab of the Property Editor, change the Name to DemoCompensate.
  15. In App Explorer, right-click FaultHandlingProcessApp, point to Add New, and then select Orchestration.

    The New Orchestration dialog box opens.

  16. In the Name box, type FaultHandlingOrch, and then click OK.
  17. Perform the following steps to import the SerenaSampleTickerService:
    1. In App Explorer, under FaultHandlingOrch, right-click Web Services, and then select Add New Web Service.

      The Web Service Configuration dialog box opens.

    2. In the WSDL box, enter the following URL: http://serverName/Ticker/services/SerenaSampleTickerService?wsdl
      Note: In the SBM On-Demand environment, serverName is the URL that you use to access Application Repository. For example, the server name for Acme Company is http://acme.admin.serenaprocessapps.com. In the on-premise environment, serverName is the name of the server (or local machine) that is running the Tomcat server. The serverName for most local machines is localhost:8085.
    3. Click OK.

      SerenaSampleTickerService appears in App Explorer under Web Services.

  18. Save the process app:
    1. On the Quick Access Toolbar, click the Save locally button.

      A message box opens reminding you that the design elements have been saved to the Local Cache only.

    2. Click OK.

Related Topics

Orchestration Tutorial

Copyright © 2007–2019 Micro Focus or one of its affiliates. All rights reserved.