Fault Handling
It is one thing to architect,
design, and code the “happy flow” of your automated business processes
and services. It is another thing to deal with situations you do not
want or expect to occur in your processes and services. This session
dives into fault handling in Oracle Service Bus 11g and Oracle SOA Suite
11g, based on an order-to-cash business process. Faults can be divided
into business faults, technical faults, programming errors, and faulty
user input. Each type of fault needs a different approach to prevent
them from occurring or to deal with them. For example, apply User
Experience (UX) techniques to improve the quality of your application so
that faulty user input can be prevented as much as possible. This
session shows and demos what patterns and techniques can be used in
Oracle Service Bus and Oracle SOA Suite to prevent and handle technical
faults as well as business faults.
Q&A
This section lists answers to the questions that were raised during the preview event.
Q: Where can retries be configured in Oracle Service Bus?
The
retry mechanism is used to prevent faults caused by temporary glitches
such as short network interruptions. A faulted message is resend
(retried) and might succeed this time since the glitch has passed.
Retries are an out-of-the-box feature that can be used in Oracle Service
Bus and Oracle SOA Suite using the Fault Policy framework. By default,
retries are disabled in Oracle Service Bus. Read the full article.
For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.
