Upcoming SlideShare
Loading in...5
×
 

Ronald van Luttikhuizen - Effective fault handling in SOA Suite and OSB 11g

on

  • 611 views

De presentatie die Ronald van Luttikhuizen tijdens de Oracle OpenWorld Preview sessie bij AMIS heeft verzorgd.

De presentatie die Ronald van Luttikhuizen tijdens de Oracle OpenWorld Preview sessie bij AMIS heeft verzorgd.

Statistics

Views

Total Views
611
Slideshare-icon Views on SlideShare
609
Embed Views
2

Actions

Likes
0
Downloads
6
Comments
0

1 Embed 2

http://www.docshut.com 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Ronald van Luttikhuizen - Effective fault handling in SOA Suite and OSB 11g Ronald van Luttikhuizen - Effective fault handling in SOA Suite and OSB 11g Presentation Transcript

    • Effective Fault Handling inOracle SOA Suite 11gRonald van Luttikhuizen [Vennster]Guido Schmutz [Trivadis]1-Oct-2012 | Oracle OpenWorld & JavaOne 1|x
    • Guido Schmutz• Working for Trivadis for more than 15 years• Oracle ACE Director for Fusion Middleware and SOA• Co-Author of different books• Consultant, Trainer, Software Architect for Java, Oracle, SOA and EDA• Member of Trivadis Architecture Board• Technology Manager @ Trivadis• More than 20 years of software development experience• Contact: guido.schmutz@trivadis.com• Blog: http://guidoschmutz.wordpress.com• Twitter: gschmutz 2|x
    • Ronald van Luttikhuizen• Managing Partner at Vennster• Oracle ACE Director for Fusion Middleware and SOA• Author of different articles, co-author Oracle SOA Book 11g book• Upcoming book SOA Made Simple• Architect, consultant, trainer for Oracle, SOA, EDA, Java• More than 10 years of software development and architecture experience• Contact: ronald.van.luttikhuizen@vennster.nl• Blog: blog.vennster.nl• Twitter: rluttikhuizen 3|x
    • Agenda1. What is Fault Handling ?2. Fault Handling in SOA vs. traditional systems3. Scenario and Patterns4. Implementation of Scenario5. Summary and Best Practices 4|x
    • Fault Handling● The goal of every programmer should be to write unbreakable software● Extent of achievement depends on how good expected and unexpected exception conditions are handled and managed● Object-oriented languages such as C++ and Java provide an efficient way for handling exceptions using constructs such as try, catch, and finally● With a SOA, most of what is available at language level is still valid and usable● SOA raises different challenges once starting orchestrating services and creating composite applications● Prevention vs. handling 5|x
    • What is a Fault ?● Something happened outside normal operational activity or “happy flow” • Technical error • Programming error • Faulty operation by user • Exceptional business behavior● Prevention and handling 6|x
    • Two Types of FaultsBusiness faults● Faults that service clients can expect and recover from● Failure to meet a particular business requirement● Often: expected, business value, contractual and recoverableTechnical faults● Faults that service clients do not expect and cannot (easily) recover from● Results of unexpected errors during runtime, e.g. null pointer errors, resources not available, and so on● Often: unexpected, technical, implementation and non-recoverable 7|x
    • Business Fault<wsdl:operation name="orderProduct"> <wsdl:input message="order:OrderProductRequestMessage"/> <wsdl:output message="order:OrderProductResponseMessage"/> <wsdl:fault message="order:ProductNotInStockFaultMessage" name="ProductNotInStockFault"/> 1. Service contract <wsdl:fault message="order:CustomerNotFoundFaultMessage" name="CustomerNotFoundFault"/> including fault</wsdl:operation><xsd:element name="CustomerNotFoundFaultMessage"> <xsd:complexType> <xsd:sequence> <xsd:element name="CustName" type="xsd:string"/> 2. Fault message payload <xsd:element name="City" type="xsd:string"/> </xsd:sequence> </xsd:complexType></xsd:element> 8|x
    • Business Fault (II)<soap:Envelope> <soap:Header/> <soap:Body> <soap:Fault> 3. Actual service response <faultcode>CST-1234</faultcode> <faultstring>Customer not found</faultstring> <detail> <CustomerNotFoundFault> <CustName>John Doe</CustName> <City>Long Beach</City> </CustomerNotFoundFault> </detail> </soap:Fault> </soap:Body></soap:Envelope> 9|x
    • Technical Fault<wsdl:operation name="orderProduct”> <wsdl:input message="order:OrderProductMessage"/> <wsdl:output message="order:OrderProductResponseMessage"/> <wsdl:fault message="order:ProductNotInStockFaultMessage" 1. Service contract name="ProductNotInStockFault"/> including fault <wsdl:fault message="order:CustomerNotFoundFaultMessage" name="CustomerNotFoundFault"/></wsdl:operation> 2. Actual service response<soap:Body> <soap:Fault> <faultcode>S:Server</faultcode> <faultstring>Could not connect to URL 127.0.0.1 on port 8001</faultstring> </soap:Fault></soap:Body> 10 | x
    • Agenda1. What is Fault Handling ?2. Fault Handling in SOA vs. traditional systems3. Scenario and Patterns4. Implementation of Scenario5. Summary and Best Practices 11 | x
    • Fault Handling SOA vs. traditional systemsExternal BPM User Multiple service consumers Interface Services part of larger unit Heterogeneous & external components Long running processes ESB Asynchronous Timed events Often enterprise-wideImplemen- Implemen- Implemen- tation tation tation Transactions 12 | x
    • Agenda1. What is Fault Handling ?2. Fault Handling in SOA vs. traditional systems3. Scenario and Patterns4. Implementation of Scenario5. Summary and Best Practices 13 | x
    • Old System with limited scalabilityShort Network interruptions No 7*24 avail. for single instance of credit card service Response sometimes get Fault if product is lostno longer available Not always available 14 | x
    • Patterns for Fault Tolerant SoftwareCompensationException shielding(Limit) retryShare the loadAlternativeException handlerHeartbeatThrottling 15 | x
    • Fault Recovery Strategies● Inaction – Ignore the request● Balk – Admit failure● Guarded suspension – Suspend execution until conditions for correct execution are established● Provisional action – Pretend to perform the request, but do not commit until success is granted● Recovery – Perform an acceptable alternative 16 | x
    • Fault Recovery Strategies● Rollback – Try to proceed, but on failure, undo the effects of a failed action● Retry – Repeatedly attempt a failed action after recovering from failed attempts● Appeal to higher authority – Ask someone to apply judgment and steer the software to an acceptable resolution● Resign – Minimize damage, write log information, then signal definite and safe failure 17 | x
    • Agenda1. What is Fault Handling ?2. Fault Handling in SOA vs. traditional systems3. Scenario and Patterns4. Implementation of Scenario5. Summary and Best Practices 18 | x
    • 19 | x
    • Product ManagementResult Caching Result Cache Problem ● Not to overload the old, non-scalable product system with the new demand Solution ● Use Result Caching to cache the product information (read-only operation) ● Use Service Throttling to limit the number of concurrent requests 20 | x
    • Product ManagementResult Caching Results are returned from cache rather than always invoking the external service ● Product data is rather static, so ideal candidate for caching Proxy Business 1 Product DB Service Service 2 3 Result CacheOSB 21 | x
    • Product ManagementService Throttling Restrict the number of messages on the message flow to a Business Service Message Buffer Proxy Business Product Service Service DBOSB ● Set from Operational Settings on the OSB console 22 | x
    • Credit Card BookingRetry Configuration Retry Problem ● Unstable network between us and the external services Solution ● Use Retry mechanism of OSB to try multiple times ● No Fault Management necessary for service consumer if network interruption is only for a short time 23 | x
    • Credit Card BookingRetry Configuration Configured on the business service in OSB 1 Proxy Business after 2s Credit Card Service Service Service 2OSB 5x 24 | x
    • Credit Card BookingService Pooling Service Pooling Problem ● Credit Card Service does not guarantee 7*24 availability for one single instance Solution ● Use the multiple instances (endpoints) that the company provides and use service pooling feature of OSB ● No Fault Management for the service consumer if at least one endpoint is available 25 | x
    • Credit Card BookingService Pooling Credit Card Service instance 1 Proxy Business Credit Card Service instance 2 Service Service OSB Credit Card Service instance 3 26 | x
    • Order ManagementTransaction configuration Transaction of OSB Service Consumer Transaction of OSB Service Consumer Problem ● Guarantee that the message will be delivered to the order management system Solution ● Make sure that queues are available, even if the Handle Order system is not ● Make sure that queuing run’s in the same transaction as the service consumer 27 | x
    • Transactions in OSBExplanation and Demo of Transactions in OSB 28 | x
    • Order Management (II) Fault Message on Callback ContractFault Message onCallback Contract Problem ● Need to return a Product No Longer Available Business Fault over an Asynchronous MEP Solution ● Design a separate Fault Message and Operation on the Callback contract (WSDL) and use that 29 | x
    • Order Management (II)Fault Message on Callback“Business Fault” modeled as another operation on the Callback WSDL 30 | x
    • Order HistoryFault Management Framework Use Fault Policy Management In Mediator to configure retry Problem ● Order History System not available should have no impact on Business Process Solution ● Use Mediator with Fault Management Framework to configure retry independent of availability of Order History Web Service 31 | x
    • Order History Fault Management Framework<faultPolicyBindings version="2.0.1"> <composite faultPolicy="OrderProcessFaultPolicy"/></faultPolicyBindings><faultPolicies> <faultPolicy version="2.0.1" id="OrderProcessFaultPolicy"> <Conditions> <action ref="RetryAction"/> </Conditions> <Actions> <Action id="RetryAction"> <Retry> <retryCount>3</retryCount> <retryInterval>2</retryInterval> <exponentialBackoff/> <retryFailureAction ref="HumanInterventionAction"/> <retrySuccessAction/> </Retry> </Action> </Actions> </faultPolicy></faultPolicies> 32 | x
    • Order Handling Process Return errors as synchronous response Problem ● Both Product Management and Credit Card Booking can Fault Handling return Business Faults Fault Handling SolutionReply with Fault ● Handle errors and map them to errors returned to the service consumer (i.e. the caller of the process) 33 | x
    • Order Handling Process Return errors as synchronous responseHandle Business Faults in BPEL error handler and reply with an error 34 | x
    • Order Handling Process (II) Handle missing callback with timeout Problem ● Order Processing response message can get lost in the Order Processing system, i.e. the callback message will never arrive in the process Solution ● Timeout on the Wait For Answer with a BPEL pick activityPick with timeout with a timeout ● Undo the process by doing compensation Compensate ● Use the BPEL compensate activity together with compensation handler to undo the Booking of the Credit Card 35 | x
    • Order Handling Process (II)Handle missing callback with timeoutPick Activity for handling callback message with timeout branch c 36 | x
    • Order Handling Process (III)Compensation Handling Problem ● Order Processing callback message can be a Product No Compensation Longer Available Business Fault Handler Solution ● Undo the process by doing compensationHandle Business ● Use the BPEL compensate activity together withFault and Compensate compensation handler to undo the Booking of the Credit Card 37 | x
    • Order Handling Process (III)Compensation HandlingCompensate activity invokes compensation handling on the inner scope• Can only be invoked from within a fault handler or another compensation handler 38 | x
    • Order Handling Process (IV)Non-idempotent operations Problem ● Credit Card Booking is a non-idempotent operation Solution Non-Idempotent ● To avoid BPEL calling the Book Card operation again (not really possible here), we have set the idempotent Property on the partner link to FALSE Idempotent 39 | x
    • Order Handling Process (V) Generic Error Handler w. Fault Policy Framework Problem ● Unexpected (technical) faultUnexpected (technical) error ● Multiple processes that deal with unexpected faults in their own way Solution ● Use fault handler mechanism to enqueue on error queue without adding process logic ● Create one process to listen to error queue and handle faults ● Retrieve process information by using (composite) sensors 40 | x
    • Order Handling Process (V) Generic Error Handler w. Fault Policy Framework<faultPolicyBindings version="2.0.1"> <composite faultPolicy="GenericFaultPolicy"/></faultPolicyBindings><faultPolicies> <faultPolicy version="2.0.1" id="GenericFaultPolicy"> <Conditions> <action ref="GenericAction"/> </Conditions> <Actions> <Action id="GenericAction"> <javaAction className="nl.vennster.GenericHandler“ defaultAction=“HumanIntervention"> <returnValue value="HumanIntervention" ref=" HumanIntervention"/> </javaAction> </Action> </Actions> </faultPolicy></faultPolicies><property name="oracle.composite.faultPolicyFile">oramds:/apps/fault-policies.xml</property><property name="oracle.composite.faultBindingFile">oramds:/apps/fault-bindings.xml</property> 41 | x
    • Order Handling Process (V)Generic Error Handler w. Fault Policy Framework Explanation of generic fault handler 42 | x
    • Agenda1. What is Fault Handling ?2. Fault Handling in SOA vs. traditional systems3. Scenario and Patterns4. Implementation of Scenario5. Summary and Best Practices 43 | x
    • SummaryIssue Solution ProductOverloading product management system ThrottlingResult cache OSBCredit Card Service does not guarantee 7*24 uptime due to e.g. Muliple endpoints OSBnetwork problems Service poolingGuarantee message delivery to order management system Availability of queues OSB (and SOA Suite for XA Enqueue and dequeue in service consumer propagation to OSB) transactionReturning business fault over async MEP from order management Separate operation and fault message OSB and SOA Suite (callbacksystem contract between the two)Order history service not available Retry in Mediator using fault policy framework SOA SuiteBusiness fault handling from service to process to consumer Catch faults in process and reply fault to OSB and SOA Suite (correct consumer contracts)Detect missing response message Timeout in pick activity SOA SuiteHandle product no longer available Compensation SOA SuiteAvoid calling credit card booking twice Set non-idempotent property SOA SuiteProcesses needing to deal with unexpected technical faults. All Fault policy frameworks, error queue, generic SOA Suiteprocesses solving it in their own way using process logic. error handler, SOA Suite APIs & composite sensors. 44 | x
    • Best Practices● Differentiate between business and technical faults● Design service contracts with faults in mind: formally describe business faults in service contracts● Don’t use exceptions as goto’s● Design with criticality, likeliness to fail, and cost in mind● Differentiate fault patterns in OSB and BPM/BPEL • OSB: Retry, throttling, transaction boundaries • BPM/BPEL: Compensation, business fault handling, generic fault handler, timeout● Handle unexpected errors generically● Make services autonomous● Fault-handling on scope of services and in wider perspective 45 | x