Database & Technology is an Italian company that specializes in consulting, support, and training for business intelligence and database administration. They have expertise in Oracle Data Integrator and Oracle Golden Gate. Since 2008, they have been performing migrations from Oracle Warehouse Builder to Oracle Data Integrator using a semi-automated tool they developed, which saves clients significant time and money compared to manual migrations. The tool migrates metadata such as projects, locations, modules, and mappings from OWB to equivalent components in ODI.

1. Oracle Data Integration Solutions
EMEA Partner Community Forum
11th - 12th February 2014
Prague, Czech Republic
Massimo Sposaro - marketing manager
Alessandro Drago - technical team leader
Database & Technology

2. From Oracle Warehouse Builder
to Oracle Data Integrator fast and safe

3. Database & Technology
Database & Technology was founded in Milan, Italy in 1999.
We specialize in providing consulting services, support and training with regard
to business intelligence and database administration.
We have excellent Oracle Data Integrator and Oracle Golden Gate skills and our
highly-experienced professionals are certified in these technologies.

4. Database & Technology
In addition, since 2008 we have been performing OWB to ODI migrations, having
designed and developed a semi-automated tool that allows any company to
migrate to ODI,
saving them a great deal of time and money compared to a manual migration.
For having developed this migration tool, we have been referenced by Oracle
Corporation itself.
We are also offering our experience in migrating from OWB to ODI using
the tool recently developed by Oracle regarding migrations from the
latest release of OWB11g to the latest release of ODI12c.

5. From
Oracle Data Integration
Statement of Direction:
So if client has to migrate or wants to migrate from OWB to ODI, a transfer of
the OWB components to equivalent ODI components needs to be planned

6. About the Converter
 OWB2ODI Converter is a semi-automatic tool developed by D&T to assist the
migration of OWB projects into ODI projects
 OWB2ODI Converter can speed up the migration process significantly
 The conversion can be done either at the customer or in outsourcing,
starting from export of the OWB project

7. Product overview
OWB2ODI Converter acquires OWB repository’s metadata and it generates
the corresponding ODI repository.
Algorithms in OWB are transferred in ODI and OWB operators are
transformed in corresponding ODI operators.
Supported versions
OWB v. 9.2 or higher
ODI v. 10g or higher

8. Conversion process
After initial assessment phase with the client, a specific Converter
component extracts metadata from the OWB .mdl file.
In their own laboratories, D&T uses the OWB2ODI Converter to
automatically generate the corresponding ODI project from the original
OWB one.
The generated ODI project is sent to the client for the acceptance test.

9. General architecture

10. How Converter Migrates OWB Metadata
OWB2ODI Converter can migrate:
 OWB Project
ODI Project
 OWB Location
ODI Topology Logical Schema
 OWB Module
ODI Folder
 OWB Mapping
ODI 11g: ODI Packages
ODI Interfaces
ODI Temporary Interfaces
ODI 12c: ODI Package
ODI Mapping

11. How Converter Migrates OWB Metadata
Migration to ODI 11g
Complex Mappings need to be split into several interfaces to generate the same SQL Code

12. How Converter Migrates OWB Metadata
Migration to ODI 12c
Many similarities between ODI 12c and OWB mapping. Little rework for particular
combination of operators

13. Where is it semi-automatic?
KM
OWB
Topology
ODI
Mappings
Process
flows
Mappings
DT Analyze
Conversion
Load Plan

14. Why is it semi-automatic?
Locations VS Topology

15. Why is it semi-automatic?
Datastore Management
 Access to updated metadata
 Management of NOT BOUND operators
 Management of operators with NO LOCATIONS
 Synchronization between NOT BOUND operators and BOUND operators
 Customize Models organization (SubModel hierarchy)

16. Why is it semi-automatic?
KM Management
 Setting Customize KM on Mapping
 Ready to run mappings

17. OWB to ODI Conversion
Manual process
Assessment
Manual
recognition
Automatic process
Automatic
Automatic
Conversion
Test
Debugging and
iterative test
Manual
coding
Manual
verification
Manual
verification
Manual
debugging and
verification
Full tested
converter

18. Conversion standard timing
Assessment
.mdl file
1/2 days
Assessment
report
Assessment meeting
Conversion
.mdl file
DB’s schema
(no data)
ODI Topology
xml
5/10 days
ODI Project
xml

19. Architecture: typical scenarios
(Pre-conversion)
Scenario 1
Scenario 2
Enterprise job scheduler
Oracle Workflow
(for example)
Oracle Warehouse
Builder
Project
Workflow manager
Oracle Warehouse
Builder
Project
Application logic

20. Architecture: typical scenarios
(Post-conversion)
Scenario 1
Scenario 2
Enterprise job scheduler
Oracle BPEL
(for example)
Workflow manager
Oracle Data Integrator
Project
Oracle Data Integrator
Project
Application logic

21. OWB to ODI Conversion project
Success Story
Scenario PEDW (Pirelli Enterprise DW)
 OWF (400 flows)
 OWB v. 10.2 (2.300 mappings)
 Oracle DB v. 10g
 ODI v. 11.1.1.6
 Platforms (Oracle, Sql Server, SAP, sequential files, …)

22. Our Partners:
Ireland
Brazil
Netherlands
Belgium

23. Database & Technology
Largo Promessi Sposi, 4
20142 Milano, Italy
Phone +39 02 8950 0080
Fax
+39 02 8954 9736
Mobile +39 348 6979791
Email:
massimo.sposaro@databtech.com
alessandro.drago@databtech.com
dt.marketing@databtech.net
Websites:
www.owb2odiconverter.com
www.databtech.com
OWB to ODI
migration group