Informatica v/s Oracle Data Integrator
Design Time
Informatica
ODI
Mapping
Main' interface
Source Qualifier with
SQL Override
SQ' temp interface
Reusable Lookup
Transformation
Lookup to Project
'LKP' temp interface
Using SQL Override to
resolve Dim WIDs
Join to Project 'LKP'
temp interface
Non reusable Lookup
with SQL Override
Lookup to local 'LKP'
temp interface
Non reusable Lookup
without SQL Override
Lookup in interface to
a table
Mapplets
NA
Mapping Parameters
Project Variables
Expression
Transformation
Mapping Expressions
Sequence Generators
NEXTVAL() Function in
Mapping Expression
Update Transformations
IKMs
UNIONs in SQL Override
or UNION transformation
Datasets
WHERE clause in SQL
Override
Filter in Temp
interface
Filter transformation
in Mapping
Filter in Main
interface
Aggregation
Transformation
Aggregate function in
Mapping Expression
UDFs
UDFs - ODI UDFs are
more powerful and flexible than INFA UDFs, converting an ODI UDF to INFA may
require an INFA UDF and a combination of INFA transformations
Design Time
Informatica
ODI
Mapping
Main' interface
Source Qualifier with
SQL Override
SQ' temp interface
Reusable Lookup
Transformation
Lookup to Project
'LKP' temp interface
Using SQL Override to
resolve Dim WIDs
Join to Project 'LKP'
temp interface
Non reusable Lookup
with SQL Override
Lookup to local 'LKP'
temp interface
Non reusable Lookup
without SQL Override
Lookup in interface to
a table
Mapplets
NA
Mapping Parameters
Project Variables
Expression
Transformation
Mapping Expressions
Sequence Generators
NEXTVAL() Function in
Mapping Expression
Update Transformations
IKMs
UNIONs in SQL Override
or UNION transformation
Datasets
WHERE clause in SQL
Override
Filter in Temp
interface
Filter transformation
in Mapping
Filter in Main
interface
Aggregation
Transformation
Aggregate function in
Mapping Expression
UDFs
UDFs - ODI UDFs are
more powerful and flexible than INFA UDFs, converting an ODI UDF to INFA may
require an INFA UDF and a combination of INFA transformations
Run Time
|
||
Informatica
|
DAC
|
ODI
|
Workflow
|
Task
|
Package Scenario and
Load Plan Step. A Package Scenario is closer to an INFA workflow while a Load
Plan Step is closer to a DAC task
|
Session
|
NA
|
Package Step that
implements a Main interface
|
NA
|
Execution Plan
|
Load Plan
|
Parameters
|
Parameters
|
Variables
|
NA
|
Module
|
Offering
|
NA
|
Subject Area
|
Functional Area
|
What is NEW?
• No Lookup files to store Domain Values
• Domain values has to be stored in DB through BIACM(Config Manager)
– Source Domain Values/Members
– Target Domain Values/Members
– Domain Member mapping (Source to Target)
– Golden Gate option for Customers that have significant ETL time pressures
– Introduced SDS(Source Dependent Schema) option.
– SDS is replica of OLTP
SDS can be loaded through Golden Gate
• In place of DAC ,here BIA-CM and BIA-FSM are introduced.
• CM acts as the interface for administering the entire BI Apps environment and configuring ODI
• Environment -specific configurations in Configuration Manager
• Ex: Source system,Target definitions etc
• FSM acts as a lightweight project management tool for configuring a specific BI Application, like Supply Chain and Order Management Analytics,
• Application-specific configurations in Functional Setup Manager
• Ex: Configure Initial Extract Date, Configure Global Currencies etc
• Loads can be created and run from Config Manager
No comments:
Post a Comment