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

Processing all files in a directory


Now that we have a mechanism in place to detect files, it will be important to know which files are available in order to process them. Today we may be receiving EMP001.TXT, EMP001.TXT, and EMP003.TXT. Later we may receive other similar files. If the sequence of file names can easily be predicted, we can build the expected names in a variable and wait for the expected file. However if the file names are unpredictable and random, then we need to know what we have received before we can process them. This is what we will focus on within this recipe.

Getting ready

We can start from where we left off in the previous recipe and build the examples of this recipe into that package, or we can create an entirely new package. In either case, we will still need the files EMP001.TXT, EMP002.TXT, and EMP003.TXT in the c:\temp directory.

To make sure that our example is reusable, we will create a table with the following structure:

Create table FILESLIST (
  BATCH_ID number...