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

Automated recovery concepts


Combining the design rules and patterns from Chapter 3, Building the Core – Enterprise Business Flows, Chapter 4, From Traditional Integration to Composition – Enterprise Business Services, and Chapter 5, Maintaining the Core – the Service Repository, and from this one, we can assume the following:

  1. The Service Repository with all the service metadata elements is properly maintained. We have clear associations between services, endpoints, and Audit messages under the roof of processes. Simply put, every process has a distinct service invocations footprint. Technically, it can be presented as a master tModel for a task-orchestrated service if we look at the UDDI analogy.

    Tip

    The preceding assumption is too bold. In dynamic compositions, the sequence of service invocations and even the number of invocations (that is, footprint) can be different for the same abstractly defined process. The key here is to watch out for the services with specific service roles, sometimes...

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 €18.99/month. Cancel anytime