Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
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
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
Authors (2):
Arrow left icon
Robert van Molken Robert van Molken
Author Profile Icon Robert van Molken
Robert van Molken
Philip Wilkins Philip Wilkins
Author Profile Icon Philip Wilkins
Philip Wilkins
Arrow right icon
View More author details
Toc

Table of Contents (14) Chapters Close

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?

Getting ready


Before we build our first integration, let's get acquainted with the APIs we are going to use in this first service. As shown in the preceding diagram our inbound call is a SOAP request and therefore we need a WSDL definition which defines the inbound API. Our outbound call is a REST request to a service we host on apiary (https://apiary.io) and uses the API Blueprint standard (https://apiblueprint.org) to define the REST API.

Let's start with the inbound or source definition as shown in the following screenshot. The WSDL has one operation which uses an input, output, and a fault message:

The messages reference an XSD which defines the structure for our input, output, and fault message is as follows:

The WSDL is available in the downloads as ICSBook-Ch2-FlightAirlines-Source.WSDL.

As you can see the WSDL contains one synchronous operation called AllAirlines, which uses elements from the embedded XML schema for the input, output, and fault message. In Chapter 1,Introducing the...

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 $19.99/month. Cancel anytime
Banner background image