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
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?

Invoke a cloud endpoint using SoapUI


To test our cloud endpoint we are going to use SoapUI again to simulate our flight tracking and incident system. Instead of creating a new SOAP project, we have created one for you to use to make these steps easier. Import the SoapUI project from the chapter resources. This can be done through the File menu and selecting Import Project. Open the project file FlightScheduleUpdate-Ch10-soapui-project.xml, which can be found in the book's resources for this chapter. This SoapUI project contains the SOAP binding to send messages to our orchestration and a test suite with two test cases. The first test case includes four calls to the orchestration, each with a different flight identification and a different outcome. Each call takes a different path in the orchestration. The second test case will call the orchestration twice; one call executes the otherwise branch and the other call will result in a fault as shown in the following screenshot:

Before we can...

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