Exception Handling :
It is important to define reusable, extensible, and agile approach to handle exceptions at process level and other unknown exceptions for the integration processes. Using a common exception handler service with extensible interface can provide the flexibility, re-usability, and extensibility.
• A Common Exception Handling Service will provide the exception handling capabilities for the integration services for this architecture. It will be invoked by all the services for performing actions in case of exceptions. This service will have the ability to be extended for functionality and in terms of actions in response to the corresponding exceptions.
Following functionality can be included in Common Exception handling services:
* Send email notification to support resource based on error severity and error category.
* Retry transaction for certain error types
* log error details in Error and log tables for analysis and reporting.
* Send error to Worklist Application to initiate Human Workflow.
• Fault Management Framework for BPEL Services: A generic fault management framework is recommended for handling faults in BPEL processes. If a fault occurs during runtime in an invoke activity in a process, the framework catches the fault and performs a user-specified action defined in a fault policy file associated with the activity. If a fault results in a condition in which human intervention is the prescribed action, you perform recovery actions from Oracle BPEL Control. The fault management framework provides an alternative to designing a BPEL process with catch branches in scope activities.
