I had to create a separate blog post for mappings because when I started creating a mapping (previously interface) I came to know how different it is from the previous versions.
Before we go into details of creating a mapping, lets see what all things are different from the previous versions.
I created a completely nonsensical mapping as you will see below, and trust me, for a person who is accustomed to creating interfaces in ODI for the last four years, it was infuriating
(Note: Creating Models is similar to older versions so that topic will not be elaborated)
Mapping Tab:
Observe the tabs of mapping 'TAB1' , Overview, Logical, Physical .
Now what these tabs mean in previous versions,
Physical in 12c == Flow tab in 11g
Components:
Mapping Tab Changes:
The biggest change in this area is the absence of a separate Target area, all datastores (source and target) now fall in the same canvas. The plus point of this is now you can have multiple datastores as target. But this feature radically changes the way associations are done. For example, if you want to create a join between two tables, dragging a column of table1 to the column of table2 will not create a join (in ODI11g), instead it will create a flow meaning table1 is source and table2 is target. To create a join you have to use the component named 'Join'. How this is achieved will be covered in the following posts, but for now, just remember that building a mapping in 12c is completely different from 11g and it is better to keep the concepts of ODI 11g aside and learn ODI12c as a new tool.
Before we go into details of creating a mapping, lets see what all things are different from the previous versions.
I created a completely nonsensical mapping as you will see below, and trust me, for a person who is accustomed to creating interfaces in ODI for the last four years, it was infuriating
(Note: Creating Models is similar to older versions so that topic will not be elaborated)
Mapping Tab:
Now what these tabs mean in previous versions,
Overview in 12c == Overview in 11g (except that now you cant specify Execution Schema in this tab)
Logical in 12c == Mapping tab in 11g (more on the mapping tab later)Physical in 12c == Flow tab in 11g
Components:
This is something new to 12c, sql functions have been included separately in this tab. You have to drag -n-drop or click on the mapping tab in order to use these functions, I will be covering each of them in the next few blogs (Frankly, I've been struggling to know how to use a few of them)
So far, I feel that these components are a good thing, but even people having a good experience in ODI 11g will find it a bit tedious initially.
ODI Help (Table of contents) is a good place to search and read a brief description of these components
Properties:
This is similar to older version but with addition of some new properties and a change in the layout, take a few minutes to see what is where for the first time and you will be fine next time. And I've already started detesting this word 'Staging Location Hint' (Hint ?? seriously ??), it is the same execution location of previous version.
Mapping Tab Changes:
The biggest change in this area is the absence of a separate Target area, all datastores (source and target) now fall in the same canvas. The plus point of this is now you can have multiple datastores as target. But this feature radically changes the way associations are done. For example, if you want to create a join between two tables, dragging a column of table1 to the column of table2 will not create a join (in ODI11g), instead it will create a flow meaning table1 is source and table2 is target. To create a join you have to use the component named 'Join'. How this is achieved will be covered in the following posts, but for now, just remember that building a mapping in 12c is completely different from 11g and it is better to keep the concepts of ODI 11g aside and learn ODI12c as a new tool.
Live long and prosper !!
