Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Applied SOA Patterns on the Oracle Platform

You're reading from   Applied SOA Patterns on the Oracle Platform Fuse together your pragmatic Oracle experience with abstract SOA patterns with this practical guide

Arrow left icon
Product type Paperback
Published in Aug 2014
Publisher
ISBN-13 9781782170563
Length 572 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Sergey Popov Sergey Popov
Author Profile Icon Sergey Popov
Sergey Popov
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. SOA Ecosystem – Interconnected Principles, Patterns, and Frameworks FREE CHAPTER 2. An Introduction to Oracle Fusion – a Solid Foundation for Service Inventory 3. Building the Core – Enterprise Business Flows 4. From Traditional Integration to Composition – Enterprise Business Services 5. Maintaining the Core – Service Repository 6. Finding the Compromise – the Adapter Framework 7. Gotcha! Implementing Security Layers 8. Taking Care – Error Handling 9. Additional SOA Patterns – Supporting Composition Controllers Index

Complex exception handling


Before we discuss the essential steps in exception handling in an agnostic composition controller implemented in the CTU SOA farm, we will mention the importance of clear and consistent identification of all fault messages related to certain process instances. You could use a standard Ora ECID for this purpose in addition to the initial Java-based labeling process instance at the beginning of every BPEL:

  1. Go to the Receive activity tab at the top and select Edit after a right-click.

  2. In the Properties tab, click on the green cross and select tracking.ecid from the drop-down list. Assign it to the variable of your choice. Use it within your Message Tracking Records Object.

We will start with recalling the structure of the composition controller (async Service Broker). Basically, it has two parts (if we omit the standard initialization): acquiring the execution plan and looping through EPs elements. Thus, we should have three exception scopes: sequentially, one for master...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at R$50/month. Cancel anytime