The Big difference between Oracle BI Applications 7.9.X and 11g is the Integration or ETL tier. 11g no longer uses DAC or Informatica. Instead Oracle Data Integrator replaces those components. This cross-reference I created here is for those thinking of or moving to 11g from 7.9.X. Below, you will find a cross reference guide I created to map between the Informatica/DAC concepts to their ODI counter part(s). After the two cross-reference tables, there are 3 images used as a location reference for these ODI components.
DAC to ODI
|Execution Plan||Load Plan||ODI has a Load Plan Generator, which acts like the Execution Plan generator in DAC.|
|Container||Adaptor folders/topology mapping||No concepts of containers for different sources. Instead ODI uses Adaptor folders along with logical and physical topology mappings using contexts. BIA uses one context ‘global’. There is only one reason to use or create others and that is when you have more than 1 source with the same product line version (PLV). For example, 2 instances of EBS 12.1.3 that need to be sourced. For this there is a whole different setup for this scenario.|
|Subject Area||Fact/Dim Group||ODI uses the same type of concept, except they use Load Plan Components and Fact Groups and Dimension Groups.|
|Tables||Datastores||Datastore(s) are categorized under models and sub-models. They represent the tables/files that can be used as both source and targets.|
|Indices||Constraints||Indices are setup in ODI studio under the Models accordion of Designer tab. When you traverse the model->sub-model->datastore, they will be there under the Constraints folder under the respective datastore (aka table).|
|Task Groups||Load Plan||Not to get too confusing; but, the main Load Plan executed for BIA will be generated from other load plans. Huh!? Think of a Load Plan object in ODI as a definition that contains a hierarchy of steps that can be executed conditionally, in parallel or in series. You can build bigger load plans using other load plans as building blocks. Think legos. Load plans generated by BIACM or LPG plugin use the smaller load plan definitions to build the main one.|
|Task||Task Folder||Tasks, in DAC, relate to the workflows (Incremental/Full). In ODI, this is represented with Task folders which will hold the package(s), interface(s) and procedure(s).|
Informatica to ODI
|Source/Targets||Datastore||Within ODI, no need to specify a table or file more than once as in Informatica. One needed to define table/file more than once as a source and then as a target in different adaptor folders. Easy way to make have these table/file definitions get out of synch. In ODI, this is easier and done only once with defining the Datastore(s). Datastores can used as both source and targets and used in multiple Adaptor folders.|
|Mapping/Mapplet||Interface||These two different types of objects are all handled in ODI as interfaces.
An interface, in ODI, can either be a temporary interface or a main interface. They are distinguished visible with either a yellow(temporary) or blue (main) icon . Yellow/temporary interfaces replace mapplets and blue/main interfaces replace mappings.
The Business Component (BC) mapplets are replaced with temporary interfaces with SQ suffix (Source Qualifier)
|Transformations||Interfaces||This one is tricky. Transformations in Informatica can be active or passive. Meaning, active transformations can change number of rows that pass through it; passive, does not change number of rows. Transformations in Informatica take N inputs in and M output ports. In ODI 11g there is nothing like that except maybe temporary interfaces. You could also make database functions and use as mapping expressions. Just remember if you can write what you want in a SQL statement you can do the same with combination of both type of interfaces.|
|Parameter/Variables||Variables||In ODI, variables can have two scopes project or global. Variables can have default values and also refresh SQL which is used to set variables and run time when used in packages.|
|Task Sessions||There is no equivalent in ODI, nor need for it in ODI|
|Workflow||Package||Packages are made of sequence of steps organized in an execution diagram. You can use interfaces, procedures and variables as steps. For BIA, packages start refreshing and setting variables. Then go to running the main (blue) interface with diagnostic and error handling steps. Majority of the time there is only one interface being called here. There maybe be multiple interfaces to handle dependencies and run orders.|
Image 1: Adaptors, Task Folders, Packages and Interfaces
Image 2: Models, Sub-models, Datastores, Indexes
Image 3: Load Plan (Components) used to generate the main load plan