
White paper Converter OWB>ODI downloadable in .pdf format.
To allow you to test the quality of our service, we are offering, free of charge, a partial migration from OWB to ODI on 10 mappings and 4 process flows. If you are interested, please write to us at : dt.marketing@databtech.net

Both small and large companies are increasingly using information systems as support for their decisions. These information systems have specific characteristics: different types of sources and different types of targets. In recent years we have seen an increase in mergers and integration between national and international companies, and very often the need arises to conglomerate structures and information after these processes have taken place.
For this reason, companies using Oracle Warehouse Builder (OWB) find themselves having to manage ETL flows with targets that include not only Oracle databases and files, but also those of DB2, MSServer and other applications, which cannot be done with OWB. Oracle has recently introduced a new ELT application called Oracle Data Integrator, which, unlike OWB, allows you to use a wide range of products as both sources and targets for data flows. A main feature is that supported targets are not limited to database objects, but include a wide range of file types, such as CSV and Excel files.
However, data migration from Oracle Warehouse Builder to Oracle Data Integrator is not so straight forward. The only currently available solution is manual migration, in which a team has to re-implement the OWB mapping with the different ODI logic. All this costs the company a large amount of time, money and human resources, as well as requiring an initial phase for learning how to operate the new tool.

Database & Technology has developed a solution known as the OWB2ODI Converter to reduce the times and costs for migrating from Oracle Warehouse Builder to Oracle Data Integrator to a minimum.
The OWB2ODI Converter is a semi-automatic tool for converting OWB projects into ODI projects. The tool was specifically designed to recreate the logic implemented in the OWB project in the new logic of the ODI project, while keeping the semantics and functions implemented in the initial project unchanged.
Tests carried out on company projects showed that the time required for migration was drastically reduced by using the OWB2ODI Converter.
After a careful analysis of the results, it became clear that the benefits gained from using the OWB2ODI Converter tool, rather than manual conversion, increase in proportion to the size and complexity of the project.
The OWB2ODI Converter is composed of three components.
The first one reads the OWB metadata from the OWB design repository using
OMB Plus. This metadata is stored in a temporary Oracle database schema
that is used by the second component, the Java application. This application
manipulates the metadata to generate new metadata for the ODI technology.
The last step of the conversion is an ODI scenario, which saves the new
metadata in the ODI repository.
