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 variables in KM options (and reusing the variables in an interface, package, and so on)


There are times when it is useful to insert a variable within a KM option and later access that variable's value within an interface or procedure. A typical use case might be to provide the primary directory path for a log file and then add a file name to the path definition from an interface. In this recipe, we will create a log path variable, embed it into a new option within a duplicated copy of an IKM, then create an interface that will amend the IKM option by adding a file name to the path.

How to do it...

  1. Within your project, insert a new Variable called PV_PATH_LOG.

    • Select the data type as Alphanumeric (if the path were to be greater than 255 characters in length, we would need to use the Text data type)

    • Select the Keep History option as No History

  2. Duplicate the IKM SQL Control Append KM and rename it to IKM SQL Control Append – with logging.

    • Insert a new option for the IKM called DIRECTORY_FILE_PATH...