Book Image

Oracle Data Integrator 11g Cookbook

Book Image

Oracle Data Integrator 11g Cookbook

Overview of this book

Oracle Data Integrator (ODI) is Oracle's strategic data integration platform for high-speed data transformation and movement between different systems. From high-volume batches, to SOA-enabled data services, to trickle operations, ODI is a cutting-edge platform that offers heterogeneous connectivity, enterprise-level deployment, and strong administrative, diagnostic, and management capabilities."Oracle Data Integrator 11g Cookbook" will take you on a journey past your first steps with ODI to a new level of proficiency, lifting the cover on many of the internals of the product to help you better leverage the most advanced features.The first part of this book will focus on the administrative tasks required for a successful deployment, moving on to showing you how to best leverage Knowledge Modules with explanations of their internals and focus on specific examples. Next we will look into some advanced coding techniques for interfaces, packages, models, and a focus on XML. Finally the book will lift the cover on web services as well as the ODI SDK, along with additional advanced techniques that may be unknown to many users.Throughout "Oracle Data Integrator 11g Cookbook", the authors convey real-world advice and best practices learned from their extensive hands-on experience.
Table of Contents (19 chapters)
Oracle Data Integrator 11g Cookbook
Credits
Foreword
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Creating a temporary interface (subquery)


During normal application development, there may be times when the complexities of the functional requirements extend beyond the capabilities of a single ODI interface. To address these situations, and with the release of version 11g, ODI allowed temporary interfaces to be used as subqueries. Using a temporary interface allows developers to split up the complex logic into multiple interfaces. While a comprehensive list of use cases is impractical to mention here, this section will provide an example of one of the two basic types of temporary interfaces available:

  • Temporary interfaces using persistent data stores (target tables that already exist or will be created within the designated target schema)

  • Temporary interfaces using non-persistent data stores (target tables that are not instantiated but will be used to form a subquery within other interfaces)

In this recipe, we will demonstrate the implementation of a non-persistent temporary interface used...