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

Using table names that run in all contexts using getObjectName


Since it's usually beneficial to avoid hard-coding fully qualified schema and object names (doing so can create issues when migrating code between environments), we will often want to employ a simple technique that uses one of the out of the box ODI substitution methods: odiRef.getObjectName.odiRef.getObjectName. This particular method can resolve and return the complete object name for a specified table depending on the context in which the application is currently running. In this recipe, we will examine some of the details of how ODI can resolve a complete database table name using only a base object name.

Getting ready

All references to tables in this recipe are taken from the data samples described in the preface of this book. Be sure to reverse engineer the DEMO_SRC and DEMO_TRG data models before beginning this recipe.

How to do it...

  1. Within a folder of your choosing, insert a new variable called PV_TABLE_CNT.

    • Set the Datatype...