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

Defining packages and loops for near real-time execution using a hybrid loop


There are many use cases where a specific job may require execution on a continual basis, perhaps the most common of which is when using a changed-data-capture process. A commonly occurring situation in Changed Data Capture (CDC) environments is the requirement that the ELT processes continuously monitor for data changes on the source system, rather than simply executing on a fixed schedule.

Unfortunately, a perpetual ELT process presents some logistical problems such as how to efficiently manage the job logs in the Operator navigator and how to afford an administrator the opportunity to terminate and restart the job. For example, if an ODI scenario is designed to recursively repeat an internal loop, all process activities will be collected into a single, enormous job log. On the other hand, if an ODI scenario is designed to reinvoke itself upon completion of its assigned tasks, the proliferation of individual job...