This post describes how ODI can be leveraged to execute processes in parallel, and beyond the parallelisation how these can then be synchronized.
An analysis of the benefits of using a template based approach for data integration, and how this approach is made possible by ODI Knowledge Modules.
ODI automatically generates a table to summarize all errors identified on a server. We review here the structure of this table, and how to locate it on the server.
This post will look into when and how to create a knowledge module. Then it will walk through some of the choices that can be made when designing a Knowledge Module. A complete KM is provided to support the explanations.
Using one of the ODI User Functions that were described in a previous post, we review how to design and use User Functions in ODI.
Using ODI to generate random sample data sets out of thin air, using a combination of Knowledge Module and User Functions.
The posts in this series assume that you have some level of familiarity with ODI. The concepts of Interface, Model and Knowledge Module are used here assuming that you understand them in the context of ODI. If you need more...
If you use an RSS reader, you can subscribe to a feed of all future entries tagged 'Interface'.