The document describes a tool called OWB2ODI Converter that can help migrate Oracle Warehouse Builder (OWB) projects to Oracle Data Integrator (ODI) projects. It explains that the converter can automate around 90% of the migration process. The key steps in the migration are exporting the OWB project metadata and target schemas, running the converter to generate an ODI project from the exported files, and handling any manual mapping or process adjustments needed between the two platforms. Examples are provided of how various OWB process flow elements like modules, activities, and transformations would be converted to equivalent structures in ODI.

1. From Oracle Warehouse Builder
to Oracle Data Integrator
fast and safe
®

2. SUMMARY
Introduction
General Architecture
What do we Need
How We Migrate OWB Process Flow
Supported Activities
Warning Transition Handling
OWB & ODI Releases Compliance
Some Migration Examples

3. INTRODUCTION
OWB2ODI Converter is a semiautomatic tool
developed by D&T to assist the migration of OWB
projects into ODI projects
OWB2ODI Converter can speed up the migration
process
90% of migration’s manual activities can be cut
back
The conversion can be done either at the
customer or in outsourcing, starting from export
of the OWB project

4. GENERAL ARCHITECTURE
export of schemas
(only structures)
OWB2ODI Converter
Converter
mdl export file
DB
Repository
OWB
Process
flows
Mappings
ODI Project
xml
ODI Topology
xml

5. WHAT DO WE NEED
An OWB .mdl export file of the project to convert
An Oracle physical export of all involved target schema.
Note: We don't need data, only the structures
(exp…ROWS=N or expdp…CONTENT= METADATA_ONLY)

6. HOW WE MIGRATE OWB PROCESS FLOWS
Process Flow Modules ODI Folders
Process Flow ODI Package
Fork Activity ODI Load Plan
Sub Process Flow Activity ODI Scenarios
Mapping Activity ODI Scenarios
Transformation Activity ODI Procedure
Complex Transition ODI Procedure
Warning Transition* “Dummy” ODI
Procedure
* Since ODI does not have a “warning status”, the OWB “warning transition” is handled
depending on each client’s specific needs. See next slide

7. WARNING TRANSITIONS
ODI does not have a “Warning Status”
How to manage?
Customer solution agreement?
Don’t consider at all?
What we do as default:
create a Dummy ODI Procedure

8. SUPPORTED ACTIVITIES

9. OWB & ODI RELEASES COMPLIANCE
OWB release >= 9.2
ODI release >= 10*
*The OWB “Fork Activity” is converted by using the ODI “Load plan” feature that is only
available from ODI v.11.1.1.5 onwards

10. SOME EXAMPLES OF PROCESS FLOWS CONVERSION

11. Example 1 – OWB PROCESS FLOW MODULES
Process Flow Modules ODI Folders

12. Example 2 – OWB FORK ACTIVITY

13. Example 2 – OWB FORK ACTIVITY ( Converted )
OWB Fork Activity ODI Load Plan

14. Example 3 – OWB COMPLEX & TRANSFORMATION ACTIVITY

15. Example 3 – OWB COMPLEX ACTIVITY ( Converted )
OWB Complex Activity ODI Procedure

16. Example 3 – OWB TRANSFORMATION ( Converted )
OWB Transformation ODI Procedure

17. Example 4 – OWB ROUTE ACTIVITY

18. Example 4 – OWB ROUTE ACTIVITY ( Converted )
OWB Route Activity ODI Procedure

19. Largo Promessi Sposi, 4
20142 Milano (Italy)
Phone +39 02 8950 0080
Fax +39 02 8954 9736
Email:
dt.marketing@databtech.net
Websites:
www.databtech.com
www.owb2odiconverter.com
Database & Technology s.r.l.
®