Aia Error Handling Framework Oracle
Contents |
ecosystem. This chapter includes the following sections: Section 13.1, "Introduction to the Error Handling Framework" Section 13.2, "Introduction to Error what is error handling framework in oracle Handling for Business Faults" Section 13.3, "Introduction to Error Handling for
Plsqldoc
BPEL and Mediator System Faults" Section 13.4, "Introduction to Error Handling for Oracle B2B Errors" 13.1 Introduction aia async error handling bpel process to the Error Handling Framework This section includes the following topic: Section 13.1.1, "Fault Categories." Figure 13-1 provides a high-level overview of the Error Handling Framework. Figure clear sql 13-1 Key Features of Error Handling Framework Components 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
Aiaasyncerrorhandlingbpelprocess
faults. Works across integration patterns. Adopts the Oracle SOA Suite 11g tech stack. Error Notifications Error notifications are emailed to suitable actor roles, such as integration administrators, and FYI roles, such as customer service representatives. Provides visibility into error context. Drill-down to the Oracle Enterprise Manager Console Flow Trace page from the error notification email. View errors in the context of an AIA flow trace. Enables customization of error notification content. Add key fields to the error notification body. Add or remove fields from error notification content. Issue error notifications to suitable Actor and FYI roles. Provide a link to Oracle BPM Worklist for error details, if desired. Enables error notification throttling. Control the number of error notifications issued for a specific error. Regulate the issuance of error notifications by time interval and number of errors. Oracle BPM Worklist Integration Centralized user interface to access error details that are assigned for resolution or for informational purposes. Accessible to administrators and end-users. Decoup
Architecture (AIA) Foundation Pack 11gR1: Essentials Next Fault handling in AIA Close Oracle Application Integration Architecture (AIA) Foundation Pack 11gR1: Essentials by Hariharan V Ganesarethinam Published by Packt Publishing Oracle Application Integration Architecture (AIA) Foundation Pack 11gR1: Essentials Table of Contents Oracle Application Integration Architecture (AIA) Foundation Pack 11gR1: Essentials Credits About the Author Acknowledgement About the Reviewers www.PacktPub.com Support files, eBooks, discount offers and more Preface What this book covers What you need for this book Who this book is for Conventions Reader feedback https://docs.oracle.com/cd/E17904_01/doc.1111/e17366/chapter13.htm Customer support 1. Overview of Oracle AIA Various types of integration Integration architectures What is Oracle AIA? What is Oracle AIA Process Integration Pack? Oracle AIA Foundation Pack concepts Components of AIA Foundation Pack Oracle AIA Reference Architecture The role of Oracle Fusion Middleware Summary 2. Enterprise Business Objects Overview of Enterprise Business Objects Exploring EBO Core EBO Core https://www.safaribooksonline.com/library/view/oracle-application-integration/9781849684804/ch10s02.html EBO groups Structure of EBOs Extending EBOs Industry EBOs Infrastructure components Summary 3. Enterprise Business Messages Overview of Enterprise Business Message (EBM) Exploring AIA EBMs Structure of EBM EBM use cases Summary 4. Enterprise Business Services Overview of Enterprise Service Bus Structure of the EBS definition Exploring Enterprise Business Service Library Types of EBS Understanding the EBS architecture EBS design principles EBS implementation Summary 5. Application Business Connector Services ABCS in AIA ABCS Architecture Key definitions of ABCS architecture Design principles of ABCS Developing ABCS Summary 6. Enterprise Business Flow Overview of Enterprise Business Flow EBF architecture Building Enterprise Business Flow Business use case for EBF Summary 7. AIA Security Levels of security implementations Security in Oracle SOA Suite Implementing security in AIA Securing ABCS Summary 8. Versioning Importance of version management Services version management AIA versioning Summary 09. AIA Design Patterns AIA message processing patterns Asset centralization pattern Asset extensibility patterns Summary 10. Error Handling and Logging Fault handling in BPEL AIA error-handling framework Fault handling in AIA Enabling error notification Disable error notificati
I wanted to share what Oracle actually recommends and depicts about the AIA error Handler because in projects developers don't use AIA error handler as it should have been used http://serviceorientedarchitecturalconcepts.blogspot.com/2014/05/how-oracle-aia-error-handling-framework.html in recommendations. The Oracle AIA Error Handling Framework is used to capture faults across order processing. Figure belowillustrates the interactions taking place when an order failure is detected by a fulfillment system, such as provisioning and Oracle BRM. The Oracle AIA Error Handling Framework: Allows custom enrichments to the fault message. Publishes the enriched fault message to the AIA Error topic. Provides a mechanism by which the error handling Order Fallout Listener process picks only the messages that are relevant to the order failure. Creation and Submission of a Fault Message to the AIA Error Topic The custom listener selectively picks up the messages from the AIA Error Topic and initiates the appropriate Create Trouble Ticket Business flow, as shown inthe below figure. Initiating Appropriate Create Trouble Ticket Flow Here are the steps: All of the error handling framework enriched fault messages with the order failure details are posted to the AIA Error Topic (AIA_ERROR_TOPIC). Messages that are specific to order failure are stamped with a JMS Correlation ID like AIA_ORDERFALLOUT. The AIAOrderFalloutJMSBridgeService consumes the messages from the AIA_ERROR_TOPIC with JMSCorrelationID like AIA_ORDERFALLOUT and publishes them to the AIA_ORDERFALLOUT_JMSQ queue. (This queue is introduced to persist the order failure messages and ensure the messages are not lost if there are errors.) Messages that are specific to order failure have a JMS Correlation ID of either AIA_ORDERFALLOUT_TTS or AIA_ORDERFALLOUT_CFS, depending on whether the trouble ticket is created directly by Oracle AIA or the order failure notification is sent to Oracle OSM CFS. For more information about how to set up the seed data so that the trouble ticket is created either by Oracle AIA of Oracle OSM, seeSection 27.5.2, "Using Error Type to Control Response to Order Fallout." The AIACOMOrderFalloutNotificationJMSConsumer picks up the fault messages and initiates the appropriate Create Trouble Ticket business flow. For the Create Trouble Ticket business flow: If the JMSCorrelationID = AIA_ORDERFALLOUT_TTS, the trouble ticket is directly created by Oracle AIA. (This is the default configuration.) If the JMSCorrelationID = AIA_ORDERFALLOUT_CFS, the order failure no