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

Selecting a Fault Name

Selecting a Fault Name

Define a fault name based on a fault type and variable.
A catch or throw activity has a fault name property that you can open in Properties view. In the
Fault Name
dialog you can make the following selections:
  • Scope Faults
    A scope fault name is typically from the WSDL for a service being invoked. The name of the fault is typically the name of fault on an operation with the target namespace as the qualifying namespace value. If your process uses a People activity (on-premises only), there are some standard Human Task faults included. Select a fault from the list.
  • Standard Faults
    A standard fault is a one defined in the WS-BPEL 2.0 specification. Select a fault from the list. See also BPEL Standard Faults else where in this help.
  • Custom Faults
    A custom fault is one you create and can include a prefix or namespace, if desired. You must use a custom fault name when catching undeclared faults.
The fault name is a required property of a throw activity and an optional property of a catch activity.

0 COMMENTS

We’d like to hear from you!