Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • Informatica ActiveVOS 9.2.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Welcome to Informatica Process Developer
  3. Using Guide Developer for the First Time
  4. Getting Started with Informatica Process Developer
  5. About Interfaces Service References and Local WSDL
  6. Planning Your BPEL Process
  7. Participants
  8. Implementing a BPMN Task or Event in BPEL
  9. Implementing a BPMN Gateway or Control Flow
  10. Using Variables
  11. Attachments
  12. Using Links
  13. Data Manipulation
  14. Compensation
  15. Correlation
  16. What is Correlation
  17. What is a Correlation Set
  18. Creating Message Properties and Property Aliases
  19. Adding a Correlation Set
  20. Deleting a Correlation Set
  21. Adding Correlations to an Activity
  22. Rules for Declaring and Using Correlation Sets
  23. Correlation Sets and Engine-Managed Correlation
  24. Event Handling
  25. Fault Handling
  26. Simulating and Debugging
  27. Deploying Your Processes
  28. BPEL Unit Testing
  29. Creating POJO and XQuery Custom Functions
  30. Custom Service Interactions
  31. Process Exception Management
  32. Creating Reports for Process Server and Central
  33. Business Event Processing
  34. Process Central Forms and Configuration
  35. Building a Process with a System Service
  36. Human Tasks
  37. BPEL Faults and Reports

Designer

Designer

Back Next

Adding a Fault Handler for a Scope

Adding a Fault Handler for a Scope

You can add multiple catch handlers and one catch all handler for each scope in your process.
For explanations of these handlers, see Defining Catch and CatchAll Fault Handlers and Catching Undeclared and SOAP Faults.
To add a catch handler to a scope:
  1. Select a scope container on the Process Activities tab of the Process Editor canvas.
  2. Drag an
    Error catch event
     into the scope or near the border of a collapsed scope, as the illustration shows.
  3. In the Properties view, select the following optional values:
    1. Select the
      Catch All Faults
       checkbox and leave the other properties blank.
    2. Fault Name
      . See Selecting a Fault Name for details. For a discussion on whether or not to add a fault name, see Fault Handling Processing Rules and Rules for Catching Faults in a Catch Activity.
    3. Fault Variable
      . Type in name for the variable described by the variable definition. For a discussion on whether or not to add a fault variable, see Fault Handling Processing Rules and Rules for Catching Faults in a Catch Activity. If you have selected a Fault Name, the fault variables picklist displays only compatible variables.
    4. Variable Definition
      . Select the
      Dialog (...) Button
       at the end of the row to open the Variable Definition dialog. See Adding a Fault Variable Definition for details. For a discussion on whether or not to add a a fault variable, see Fault Handling Processing Rules and Rules for Catching Faults in a Catch Activity.
  4. Drag an activity into the catch handler, such as a reply. For a boundary event, you must link the handler to an activity to execute. The activity must be an activity that has not yet executed.
  5. If you are using a boundary event, you cannot use certain activities. See Catch and Catch All Boundary Events and Compensate, Compensate Scope and Rethrow.
  6. Fill in the properties for the activity to handle the fault.
To add the catch all handler for a scope:
  1. Select a scope on the Process Activities tab of the Process Editor canvas.
  2. Drag an
    Error catch event
     into the scope or near its border.
  3. In the Properties view, select the
    Catch All Faults
     checkbox.
  4. Drag an activity into the catch all handler, such as an assign or compensate.
    If you are using a boundary event, you cannot use certain activities. See Catch and Catch All Boundary Events and Compensate, Compensate Scope and Rethrow.
  5. Fill in the properties for the activity to handle the fault.
The following illustration shows an example of Catch All fault handler added for a scope.
Tip
: If you collapse the fault handler, you can add a background color from the Properties view. Right-mouse-click the handler and select
Collapse Container
.
0 COMMENTS
We’d like to hear from you!