Common FTP use cases with Orchestration
by Phil Wilkins, Robert van Mölken
Implementing Oracle Integration Cloud Service
- Implementing Oracle Integration Cloud Service
- 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
- Typical workflow and steps to execute
- Connections define our integration points
- Integrations
- Transformation and lookups
- Summary
- 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
- Tweet changes in flight schedules
- Send missing person report by e-mail
- Summary
- 6. Creating Complex Transformations
- 7. Routing and Filtering
- Preparation
- Creating connections
- Creating a filtered integration
- Routing by Message Content
- Creating the Routing Integration
- Extending the filter integration to use a REST source
- Creating the trigger REST connection
- Cloning the filter integration
- Changing the invoke connector
- Defining a multipart filter
- Running the REST filter service
- Summary
- 8. Publish and Subscribe with External Applications
- 9. Managed File Transfer with Scheduling
- Differences between File and FTP connectors
- Scenario
- Prerequisites
- Setting up FTP locations
- Creating the FTP to FTP integration
- Using encryption
- Common FTP use cases with Orchestration
- Extra steps to define structure for file content
- Calculated filenames
- FTP integrations with interesting behaviors
- Summary
- 10. Advanced Orchestration with Branching and Asynchronous Flows
- 11. Calling an On-Premises API
- What kinds of agents exist?
- When can an agent help?
- Prerequisites and deploying an agent
- Building the integration
- Summary
- 12. Are My Integrations Running Fine, and What If They Are Not?
- 13. Where Can I Go from Here?
Having provided a simple illustration, we should explore some of the richer use cases that are likely to be needed. The most likely scenarios are for integrating legacy environments with patterns such as:
- Web service to FTP: most likely to occur when wanting to create a file record of things happening for purposes of audit or where we have a contemporary system needing to send data to a legacy platform. The integration (or part of it) might look like:
- FTP to web service: a case where legacy applications can only expose their data using files, so the only way to gather the data is to read the file in and process from there. For example, you might wish for your Orchestration to include:
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.