Beruflich Dokumente
Kultur Dokumente
Change Record
Contents......................................................................................................................2
Introduction..................................................................................................................3
Demonstration.............................................................................................................4
Getting Started............................................................................................................5
Section 1: Models and Metadata..................................................................................8
Section 2: Projects.....................................................................................................18
Section 3: Operator....................................................................................................49
Section 4: Metadata Navigator...................................................................................51
Section 5: Lightweight Designer.................................................................................56
Section 6: Common Format Designer.........................................................................57
Conclusion: Overall Questions....................................................................................64
Architecture
Design Time
Development
ODI Design-Time Environment Development Servers and
Applications
User Interfaces
Topology/Security Data
Code Execution CRM
Administrators Warehouse
Agent
Design-time Execution Log Data Flow Return Codes Legacy
Metadata/Rules Repositories Conductor
Designers ERP
ESB Files /
XML
Scenarios
and Projects
Releases
Production
ERP
Thin Client
Metadata Lineage ESB Files /
Metadata XML
Data Stewarts
Navigator
Note: Oracle Data Integrator was designed at the outset to support a wide range of
technologies, including Oracle and non-Oracle. Some components were configured
to demonstrate how ODI plays into a non-Oracle technology stack, but do not
function due to missing third party software. These include:
• MySQL: There are several objects defined in the MySQL – Sales db model
which are not used in the working part of the demonstration. MySQL has been
installed and tested, but has been removed prior to distribution of this VM
image.
• In folder Demo > Packages > Main Flow > Steps > Error Email we have a
notification step. Not mail client has been configured on this VM image.
Replace the mail details with your own.
• Web Services: In folder Demo > Packages > Main Flow > Steps >
GetStockQuote has an example of calling a web service. This does not
function, and is only an example. Substitute your own web service to see how
this works.
• Web Services: Further, data sources can be exposed as a web service,
although a web services engine is required. This demonstration was originally
configured with Apache Axis2, however this was removed prior to distribution.
The configuration remains as an example.
Go to Start>All
Programs>Oracle>Oracle Data
Integrator and run Designer
Reverse Engineering
Step What you should do What you should say What you should see
2. Create a new Model. To We’ll start by creating a model for our target
do this, click on the add Oracle Enterprise Data Warehouse schema.
model button. To do this, we’ll add a model.
5. Click back to the Note that we can use a filter to reduce the
Reverse tab and number of table names that are retrieved by
change the % in the using the Mask option. For instance here,
Mask field to W_AFFL_ we tell ODI that we only want tables that
%. Then, click back to begin with W_AFFL_. Clicking back to the
the Selective Reverse Selective Reverse tab, we see that only a
tab. subset of the tables are shown.
Step What you should do What you should say What you should see
Step What you should do What you should say What you should see
1. Right-click the model With all of this metadata, we can A PDF report of your model.
Oracle - Staging and easily generate PDF documentation
choose Print -> Print for all of your data integration
Model... objects. Here, we are generating a
Oracle Data Integrator PDF report of the model.
will automatically
generate a PDF report
including all of our
metadata
Create an Interface
Step What you should do What you should say What you should see
4. The join between the Note that the join between the Excel
two tables will be and MSSQL tables was created
created automatically: automatically. This is because of a
but we need to modify known relationship between the
it. tables.
Must be a right outer
join and performed on We do need to modify this join
the staging area. however. It needs to be on the
Staging Area we are joining data
To change this, click from a non-relational source.
on the join icon. In Remember that the ODI architecture
the bottom panel, takes advantage of the database
you’ll want the engines already in use, so the join
following (Note, stay will need to happen on an
in the implementation appropriate database server.
tab):
<text>: By default, the target database is
DIRECT_LIST.FROM_C used as the staging area. So in this
ON_WID=CA.FROM_C case, the data necessary data from
ON_WID (Note: should the two tables will be loaded into the
be there already) Oracle database where they will be
Execute On: Staging then joined.
Area
Step What you should do What you should say What you should see
Click the
DATASOURCE_NUM_
ID column and:
- set value to 1
- scroll down in the
panel and uncheck the
Check Not Null
checkbox
Click the
ETL_PROC_WID
column and:
- set value to 2
- scroll down in the
panel and uncheck the
Check Not Null
checkbox
7. We’re going to use the We can also use an expression Expression Editor:
expression editor editor to help us with the building of
here. Click on the the mappings. For instance, I’d like
DIRECT_FLG field and to build the mapping for the
in the panel, click the DIRECT_FLG field. Clicking on the
expression editor button brings me a
button. contextual editor. (a) For instance,
here I can see available standard
Select Oracle in the functions for the Oracle database
drop down and click since I am going to execute this
OK. expression in Oracle.
Then (b):
- Type “CASE WHEN
” in the text window
- Double-click
INTEGRATION_ID
under DIRECT_LIST in
the left panel.
- Type “ IS NOT
NULL THEN '1' ELSE
'0' END”
- Click OK
- Change Execute On
radio button to
Staging Area
10. Drag from Notice that the final two columns are
SRC_CA.TO_ACCNT_I now mapped because the column
D names matched. Next we want to
to define a join between the new table
W_AFFL_AA_H .TO_A and the existing tables.
CCNT_ID
11. Click on the Flow tab The work that I just did in the Details
tab of the interface was simply to
define at a functional level how data
will be transformed. Notice that at
no time did I worry about how data
would physically be moved and
integrated. This is all set up from
the Flow tab. In effect we are
separating the WHAT in the Details
tab from the HOW in the Flow tab.
12. (a) Click on the SS_3 The purpose of this Flow tab is to
(-1 – FILE_GENERIC) select which Knowledge Modules we
source box. want to use to generate our flow.
The KMs are completely open and
(b) Click on the LKM customizable flow templates. They
dropdown menu to will combine with the metadata that
show different KMs. we’ve defined up to now and
generate scripts and code that the
database can understand such as
SQL and loader scripts.
17. Expand the node you By expanding this step, you can then
just double clicked in see every single step that was
the tree. executed. In every one of these
steps is stored the code that was
Double click task 13 sent to the database. Everything is
(13 – Integration - visible to you. This makes it very
load W_AFFL_CA_H - easy to audit every single thing that
Insert flow into I$ was executed.
table)
Has this step failed, you would also
Click on the se the error message and number
Description tab returned by the database.
Step What you should do What you should say What you should see
Step What you should do What you should say What you should see
Go to the Diagram When I run this job, only this one row
tab. Click on the title will be loaded and if the job is
of the SRC_CA table successful, that record will be
in the source. In the automatically deleted from the
bottom panel, check journal.
the Journalized Data
Only checkbox. A
filer will appear
*** THIS IS NOT A WORKING DEMONSTRATION. IT IS ONLY USED AS AN EXAMPLE OF HOW THIS COULD BE
DONE ***
Step What you should do What you should say What you should see
Step What you should do What you should say What you should see
Step What you should do What you should say What you should see
Step What you should do What you should say What you should see
Browse Metadata
Step What you should do What you should say What you should see
4. Click on one of the From this package view, you can drill
Interface icons. Then, down to view information on the
click on the link next objects that make up the workflow.
to where it says For instance, here, we can drill down
Interface. The link to view more detailed information on
will be the name of this particular interface. We can see
the interface you information on all the mappings that
clicked in the previous were build to populate this particular
screen. Click on the table.
Mappings tab. This
will show all mappings
for this interface.
*** LIGHTWEIGHT DESIGNER HAS NOT BEEN CONFIGURED ON THIS DEMONSTRATION IMAGE ***
Update Interfaces
Step What you should do What you should say What you should see
Step What you should do What you should say What you should see
Click OK.
Click the Add
Reference icon:
4. Right-click the Oracle With a few clicks, ODI will detect the
- Staging model and difference between its version of the
choose Generate metadata and the metadata on the
DDL. In the Generate actual server and generate the DDL
DDL window, choose to propagate its version.
the ODI
Demo.Generated The DDL is generated as an ODI
Automatically Procedure. It’s possible now to view
Generation Folder: it and execute it.
To Do…