Which two best describes a situation where AIA’s error handling framework is invoked?
A.
At every BPEL receive activity whether or not an error has occurred
B.
At every ESB service invocation
C.
When a BPEL partner link experiences an invocation error
D.
When a mediator service experiences an error
Explanation:
There are two categories of faults:
1) Business faults
Business faults are generated when there is a problem with the information being processed. For
example, a credit card number is invalid.
Error actions for business faults that are internal to BPEL are configured in catch blocks. These
are business faults that are thrown by a throw activity. Error notifications and logging for these
business faults are handled by AIAAsyncErrorHandlingBPELProcess.
Error actions for business faults from external applications and services are configured using the
Composite Fault Policy Framework. These are business errors that are returned by an invoked
service or application when using a BPEL invoke activity. Error notifications and logging for these
business faults are handled by oracle.apps.aia.core.eh.CompositeJavaAction.
2) System faults
System faults occur as a result of problems within the running of the BPEL process or Mediator
service component. For example, data cannot be copied properly because the variable name is
incorrect or because of transformation errors.
Error actions for system faults are configured using the Composite Fault Policy Framework. Error
notifications and logging for system faults are handled by
oracle.apps.aia.core.eh.CompositeJavaAction.
Note: The AIA Error Handling Framework provides the following key features for integration
services operating in an AIA ecosystem.
* Unified Error Handling Approach
* Works across technologies, including BPEL and Mediator components, business-to-business
(B2B), and ODI.
* Works across categories of faults, including business and system, run-time, and technical faults.
* Works across integration patterns.* Adopts the Oracle SOA Suite 11g tech stack.