Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletter Hub
Free Learning
Arrow right icon
timer SALE ENDS IN
0 Days
:
00 Hours
:
00 Minutes
:
00 Seconds
Arrow up icon
GO TO TOP
Implementing Oracle Integration Cloud Service

You're reading from   Implementing Oracle Integration Cloud Service Click here to enter text.

Arrow left icon
Product type Paperback
Published in Jan 2017
Publisher Packt
ISBN-13 9781786460721
Length 506 pages
Edition 1st Edition
Arrow right icon
Author (1):
Arrow left icon
Robert van Molken Robert van Molken
Author Profile Icon Robert van Molken
Robert van Molken
Arrow right icon
View More author details
Toc

Table of Contents (21) Chapters Close

Implementing Oracle Integration Cloud Service
Credits
Foreword
About the Authors
About the Reviewer
www.PacktPub.com
Customer Feedback
Preface
1. Introducing the Concepts and Terminology FREE CHAPTER 2. Integrating Our First Two Applications 3. Distribute Messages Using the Pub-Sub Model 4. Integrations between SaaS Applications 5. Going Social with Twitter and Google 6. Creating Complex Transformations 7. Routing and Filtering 8. Publish and Subscribe with External Applications 9. Managed File Transfer with Scheduling 10. Advanced Orchestration with Branching and Asynchronous Flows 11. Calling an On-Premises API 12. Are My Integrations Running Fine, and What If They Are Not? 13. Where Can I Go from Here?

Enhanced techniques


We have covered the simplest and most common use cases of publish and subscribe, but we should understand some of the more advanced approaches. Let's explore them in this section.

Multiple sources

We may wish to extend our integration to accommodate multiple source systems with the source data differing a little bit, so the same source connection cannot be reused. Thus, the goal would be to achieve something along these lines:

However, the problem we have here is that the publish integration has no way to transform the payload so it is consistent, and the process of creating a subscription relates to the publish integration not a connection description for the ICS messaging solution. So the question is: How we can solve this? There is an architectural concept we will introduce shortly to help here, but from an integration creation process, we would implement things in the following way:

Canonical data model pattern and normalizers

In Chapter 1, Introducing the Concepts...

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 $15.99/month. Cancel anytime
Visually different images