Examining the anatomy of the interface flow

Once we've created all our definitions and references for the data that we want ODI to transform and transport, we can focus on what precisely it is that we want to take place in terms of data mappings and transformations, that is we can look into creating ODI Interfaces. We have already seen that ODI uses an E-LT approach and architecture, but what does that mean in detail? What actions are performed, where, and at what time during the overall flow, and what components will perform those actions?

In this section we will walk through three very simple yet common ODI data flows to examine and explain these aspects of ODI's operational behavior.

ODI Interfaces are the objects used to transform and transport data from one or more sources to a target, so each of these flow examples will be implemented in a separate interface.

Example 1: Database and file to database

This example forms the foundation of many ETL jobs. It's a simple case of loading data...