By Juergenkress-Oracle on Jun 29, 2016
New to SOA 12.2.1 is the concept of Resiliency. Oracle has introduced functionality that shuts down adapters when their composite failure meets a certain threshold. In effect, an error circuit breaker! This is extremely helpful to prevent filling up the error hospital with an abundance of errors. When suspended, the failed composite will retry the composite at a defined interval in an attempt to un-suspend the service adapter. The idea is to suspend any inbound adapters so that messages can be queued whenever an error is present and then processed later when the service is fixed.
Currently, resiliency currently only works for a small subset of adapters. These adapters include EDN, File, FTP, AQ, and JMS.
My Example - File Adapter
I deployed a sample project that used a file adapter to read a file and insert those records into a database table. Once the global resiliency policy was configured for the server, there is no special setup or additional configuration needed at the process/project level.
dropped a few files into the staging area that the file adapter read,
and off they went. All the records were inserted into the database as
expected. To cause a failure, I renamed the database table. Now, my
database adapter will no longer be able to find the table it needs to
insert into. I copied a few more files into the staging directory and,
as expected, they disappeared and faulted instances showed up. However,
because I had configured the global resiliency to trigger with three
errors in two minutes the file adapter now shows as suspended. Read the complete article here.
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.