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

2. Designer

2. Designer

Retry

Retry

Select this policy assertion as described in
Adding Policy Assertions
.
This policy describes when and how many times to retry an invoked service that does not reply.
During process execution, an invoked service can not reply, and, assuming that the service responds with a fault, you can specify how you want to handle the faulting execution.
You can specify the relatively simple policy that the server automatically retries the invocation a certain number of times.
Alternately, you can create a BPEL process to handle retries. For details, see
Retry-Policy Service
.
Add the retry attributes as follows:
Assertion parameter
Description
Default
Interval
Amount of time in seconds to wait between retries
None. You must add a value. Ignored if a service name is specified.
Attempts
Number of times to retry the service
None. You must add a value. Ignored if a service name is specified.
Service
Name of a service implemented by the process. The service is a BPEL process based on a required WSDL operation.
If you specify a service, the attempts and interval values are ignored.
faultList
Faults to include for retries
All faults are retried
faultExclusionList
Faults to exclude for retries
 
On Failure
The state for an invoke activity when the retries are exhausted: Faulted (the default) or Suspended.
Fault
XML Syntax
<abp:retryPolicy attempts="xsd:int"? interval="xsd:int"? service="NCName"? faultList="QNameList"? faultExclusionList="QNameList"? onFailure="fault"/>
Example 1: Policy with a service and fault list:
<wsa:EndpointReference xmlns:s="http://www.activebpel.org/services/retrytests"> <wsa:ServiceName PortName="retrytesterServicePort"> s:retryTesterService</wsa:ServiceName> <wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2002/12/policy" xmlns:abp="http://schemas.active-endpoints.com/ws /2005/12/policy"> <abp:retry service="retryCheckerService"> faultList="{http://xml.apache.org/axis/}* {http://www.active-endpoints.com/2004/06/bpel /extensions/}* {http://www.activebpel.org/services /retrytests}*"/> </wsp:Policy> </wsa:EndpointReference>
Example 2: Policy with attempts and fault exclusion list:
<wsa:EndpointReference xmlns:s="http://www.activebpel.org/services/retrytests"> <wsa:ServiceName PortName="retrytesterServicePort"> s:retryTesterService</wsa:ServiceName> <wsa:Metadata> <wsp:Policy xmlns:wsp="http://schemas.xmlsoap.org/ws/2002/12/policy" xmlns:abp="http://schemas.active-endpoints.com/ws/ 2005/12/policy"> <abp:retry interval="1" attempts="3"> faultExclusionList="{http://xml.apache.org/axis/}*"/> </wsp:Policy> </wsa:Metadata> </wsa:EndpointReference>


Updated March 30, 2020