In ODI 12c, Knowledge Modules (KMs) have two different types of implementation styles i.e. Template-style and Component-style.
With a new introduction to a Component-style KMs, is there any difference from ODI 11g when loading data into a flat file ?
The current available Component-style KMs are Loading KMs (LKMs) and Integration KMs (IKMs).
The style of a KM can be seen in the physical view properties of the Mapping Editor.
When you create an ODI 12c Mapping to load data into a flat file, ODI computes a default deployment specification containing execution units and groups based on the logical design and the Topology of those items and any rules you have defined.
In ODI 12c, there is no longer the Staging Area different from target checkbox on the Definition tab of your Mapping.
By default, the staging location is collocated on the target (i.e. when Preset Staging Location is set to <Blank>, target execution unit is used as staging location.)
As a general rule, if the target data server has join and transformation capabilities (classic SQL capabilities), it is advised to use the engine of this data server for the transformations.
However, if the target server does not have adequate SQL capabilities (for example, if the target is a MOM or a file), you can choose another transformation engine, which can be another data server, or the internal engine working in memory, which causes ODI to automatically move staging to a different location.
A files must also be visible to the Agent. This means to say that the Agent must be able to directly access the file system (local or mounted network disk partition) on which the file resides.
Choice of Knowledge Modules :
1. Depending on a source technology, ODI 12c uses Extract Knowledge Module (XKM) to extract data from source to a staging area of your choice.
For Example, XKM SQL Extract, XKM Oracle Extract
2. The choice of LKM will depend on the choice of Staging Area.
For Example, LKM SQL Multi-Connect, LKM SQL to File
3. If you choose LKM SQL Multi-Connect, you will have an opportunity to choose a legacy Template-style KM (for example, IKM SQL to File Append) to load data from Staging Area to File. Otherwise, An Integration KM will be automatically set to <Default> value.