User Interface and Terminology Changes in ODI 12c - Part 1
By Julien Testut-Oracle on May 01, 2014
Oracle Data Integrator 12c introduces several new exciting and powerful features, for a complete list please look at the New Features Overview document available on OTN. While working on major enhancements we have also made several smaller tweaks to improve the overall user experience. In this blog post series I will describe some of those minor changes, highlighting some of the differences between ODI 11g and ODI 12c. This will help ODI 11g users get up and running quickly with ODI 12c.
The following table lists some of the key terminology changes that have been made in ODI 12c when compared to ODI 11g:
Changes at the Model level
Slowly Changing Dimension Behavior
Setting the Slowly Changing Dimension Behavior in ODI 11g was tedious, you had to open individually each column, go to their Description tab and finally set the SCD Behavior.
In ODI 12c you can now simply set the SCD Behavior for all your datastore’s attributes directly from its Attributes panel.
Changes at the Mapping level
The Flow Control settings have been reorganized; the Controls tab found in ODI 11g Interfaces has been removed.
The Check Knowledge Modules can now be selected in the Physical tab of a 12c Mapping: click on one of your target datastores and select the Check Knowledge Module panel in the Properties window.
You will find the constraints checked by Flow Control in the Logical tab of a Mapping. Click on a target datastore and select the Constraints panel in the Properties window as shown below.
The ‘Maximum Number of Errors Allowed’ and ‘Integration Errors as Percentage’ options have also moved to the Logical tab of a Mapping and are found in the Target panel of a target datastore in its Properties window.
Temporary indexes which were previously defined in the Diagram tab of an Interface are now found in the Physical tab of a Mapping. Click on a Component such as Join or Filter in the Physical diagram to access the Temporary Indexes panel in the Properties window and set the Index Type for each of the nodes.
Quick-EditThe Quick-Edit panel which was a separate tab in an ODI 11g Interface is replaced by the Attributes panel in a Mapping. You can access it easily: simply click on one of your Target datastores and select the Attributes panel in its Properties window as shown below.
ODI 12c replaces the ‘Execute on’ parameter from ODI 11g with ‘Execute on Hint’. The ‘Execute on Hint’ parameter can be set from the Properties window of all Mapping Components such as Join, Filter or Pivot as you can see below.
This ‘Execute on Hint’ parameter can also be set for specific Expressions from the Attributes panel of a datastore or when selecting a given attribute in the Mapping diagram.
Note that this parameter is a hint and as such it can be overridden by ODI if it finds a better execution location at runtime. Execution location changes made directly in the Physical tab of a Mapping, for example by moving a Filter component from one Execution Unit to another one, will take the precedence over any hints provided in the Logical tab.
In ODI 11g you could set the Staging Area location in the Definition tab of an Interface. In 12c you can set a hint called ‘Staging Location Hint’ in the Logical tab of a Mapping. Similarly to the ‘Execute on Hint’ we saw earlier, it can be overridden in the Physical tab.
You can also set the Staging location explicitly in the Physical tab of a Mapping, the ‘Preset Staging Location’ field is found in the Deployment Specification properties panel as shown below:
There are many more changes to talk about, stay tuned for the second blog post in this series!