Migrating from OWB to ODI

ODI 12c provides following Options to migrate from OWB to ODI easier:

  • ODI 12c supports the execution and administration of OWB 11gR2 jobs directly within ODI Studio, ODI Console and Enterprise Manager. This provides a single orchestration and monitoring solution and allows companies to continue running OWB Mappings and perform a phased migration to ODI.
  • A new migration utility that will automatically translate many OWB objects and mappings into ODI equivalents. The migration utility is a command-line tool and requires two patches: one for OWB (17547241) and one for ODI (17053768)

Phased Migration using OWB and ODI run time Integration

In ODI 12c it is now possible to define a connection to an OWB workspace in Topology. Storing the connection and credential details in the ODI repository allows developers to invoke OWB processes in Packages with the OdiStartOwbJob tool. It allows us to monitor the execution of OWB processes in ODI Studio or ODI Console.

Invoking OWB processes in ODI12c is simple. You have to first add the OdiStartOwbJob tool to a Package. Then point the tool to the OWB workspace entry in Topology. This then allows you to browse the content of the OWB workspace and select the specific processes. Once the Package design is complete, you can execute it and monitor its execution in ODI. The OWB and ODI logs have been integrated allowing end users to centrally monitor.

OWB to ODI Migration Utility

In addition to the integration of OWB jobs there is also a metadata migration utility to migrate metadata from OWB 11gR2 to ODI 12c. A wide range of metadata can now be migrated with this initial release ;( you can find a complete list of objects in the documentation. In addition to the patch containing the utility for the OWB migration, there is also a patch for ODI 12c, and new Knowledge Modules to support some of the OWB mapping capabilities.

The migration utility is a command line tool that is executed from OWB home. The utility uses a driver file to specify which modules and objects to migrate. It also has 3 modes of operation, this lets you discover how much of your project will get migrated. The modes are;

• FAST_CHECK – performs a read only check, which is fastest way to understand of how much will be migrated.
• DRY_RUN – a sanity check mode which will try creating objects in-memory using the ODI 12c SDK but will not commit in the ODI repository.
• RUN – performs the migration and commit the newly migrated objects in the 12c repository.

The driver properties file can specify the specific objects to migrate, specify wildcards and lists of objects. The utility produces a report and a log file from its execution. For example:

MIGRATION-OBJECTS=PROJECT.FERRARI-DEMO
ODI MASTER USER=DEV ODI REPO
ODI_MASTER_URL=jdbc:oracle:thin:@localhost:1521 :orcl11204
ODI_MASTER_DRIVER=oracle.jdbc. OracleDriver
ODI USERNAME=SUPERVISOR
ODI WORK REPOSITORY NAME=WORKREP
OWB_WORKSPACE_OWNER=OWB_REPOS
OWB URL=localhost:1521 :orcl11204
OWB-WORKSPACE-NAME=OWB-WKSP
MIGRATION_MODE=RUN

Reference
http://docs.oracle.com/middleware/1212/odi/ODIMG/index.html
http://docs.oracle.com/middleware/1212/odi/ODIDG/app_12c_patch.htm
https://blogs.oracle.com/warehousebuilder/entry/owb_to_odi_migration_utility

Advertisements