Professional Documents
Culture Documents
Agenda
Model Overview Reverse Engineering Model Creation Complex File Driver Lab Overview Q&A
<Insert Picture Here>
Model Overview
What Is a Model?
Models are the objects that will store the metadata in ODI.
They contain a description of a relational data model. It is a group of datastores stored in a given schema on a given technology.
A model typically contains metadata reverse-engineered from the real data model (Database, flat file, XML file, Cobol Copybook, LDAP structure) Database models can be designed in ODI. The appropriate DDLs can then be generated by ODI for all necessary environments (development, QA, production)
Relational Model
ODI is strongly based on the relational paradigm. In ODI, data is handled through tabular structures defined as data stores. Data stores are used for all types of real data structures, including flat files, Extensible Markup Language (XML) files, and Java Message Service (JMS) messages.
Description in ODI
Data store; Column Not Null/Mandatory; Default value Primary keys; Alternate keys Not unique indexes; Alternate keys Reference Condition
Reverse Engineering
Customized reverse-engineering
Read metadata from the application/database system repository, then writes these metadata in the ODI repository Uses a technology-specific strategy, implemented in a Reverseengineering Knowledge Module (RKM)
ODI Repository
Model (Metadata)
Delimited format
MS SQL Server
JDBC Driver
Standard Reverse-engineering
Data Model
System tables
Customized Reverse-engineering
Note
Reverse engineering is incremental. New metadata is added, but old metadata is not removed.
Model Creation
Note
A model is always defined in a given technology. If you change a models technology, you must recheck every object related to that model.
2
3
Complex Files
Introduction
New technology Driver parameters KMs to use
Supported/non-supported
Compare to XML Insert graphic C.4.
26
Complex Files
Introduction New technology Concepts and processes similar to XML files
Main difference: Step that transparently translates the Native File into an XML structure that is used internally by the driver but never persisted
nXSD file + Complex Files driver ODI is able to reverseengineer, read, and write information from complex files
27
001|Oracle Data Intagrator EE|20000,2,+40000+ 002|Application Adapter for ODI|10000,5,+50000+ 003|BPEL Process Manager Enterprise Edition|20000,2,+40000+ 004|BPEL Process Manager Standard Edition|10000,5,+50000+ 005|BPEL Process Manager Developer Edition|1000,20,+20000+#110000
<sequence>
<element name="purchaser" type="tns:partnerType" /> <element name="seller" type="tns:partnerType" /> <element name="line-item" type="tns:line-itemType" ... </sequence> Complex File Schema (nXSD) generated with Native Format Builder Wizard. </complexType>
...
28
ODI
Complex File Driver
XML to
relational
XML
Complex File
XML nXSD
29
JDBC URL:
jdbc:snps:complexfile?f=<native file location>&d=<native schema>&re=<root element name>&s=<schema name>[&<property>=<value>...]
Property
f
Value
<native file name>
Description
Native file location (mandatory)
Use slash "/" in the path name instead of back slash "\" Possible to use an HTTP, FTP or File URL (Files located by URL are read-only.)
d re
Native Schema (nXSD) file location (mandatory) Name of the root table element of the schema (mandatory) Case sensitive Used for reverse-engineering
<schema name>
Relational schema name where the complex file is loaded (mandatory) Select when creating the phys. schema under the Complex File data server
30
Connects to the PROD20100125_001.csv file described by products.nxsd and exposes this file as a relational structure in the PRODUCTS schema
31
Lab Overview
Model
MYSQL_SRC Predefined
SPECIFIC_SEQ, SRC_CITY, SRC_CUSTOMER, SRC_ORDERS, SRC_ORDER_FORM, You will reverse SRC_ORDER_LINES, SRC_PRODUCT, engineer SRC_REGION
TRG_COUNTRY
TRG_PRODUCT
TRG_SALES
TRG_REGION
TRG_PROD_FAMILY
TRG_CUSTOMER
TRG_CITY