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 XML data within an RDBMS not in memory


By default, ODI will perform XML processing within the default in-memory database, HSQL. For out of the box JVM settings, small XML files, less than 2-3 megabytes, the in-memory database will perform as expected. However, for larger XML files, or when there is a large amount of files, it is easy to exceed the reserved amount of memory for processing within the JVM. When the JVM memory size is exceeded, the JVM will crash, and it is necessary to tune the JVM settings to allow for the large amount of memory the in-memory database will require. The XML JDBC Driver can also be set up to use a relational database for this processing. Similar to the in-memory database, a relational schema will be created in the RDBMS to match the logical schema. The physical schema in the relational database will be managed by ODI; the artifacts will be created, updated, and deleted as needed by the ODI XML JDBC Driver. The set up to use an RDBMS for XML processing...