Migrating ODI Components

Migrating Oracle Data Integrator components from one environment to another typically involves exporting Oracle Data Integrator objects and importing them in the new environment. The Development environment is the source and all the subsequent environments are the targets where these objects are imported. The export and import are limited to the custom code only.

Each environment should be built or upgraded using the provided installers. After installation or upgrade of individual environments, the custom code can be exported from the Development and imported into the subsequent environments.

The following sections provide the instructions that cover the custom code migration from one environment to another.

Note: Before importing the code in an environment, purge the execution log if any. Use the Smart export and Smart import option when moving from one environment to other environments.

CM Project

To develop custom code create a custom project and ensure that all custom objects are within this newly created project.

The primary benefit of doing this is that all custom code is completely isolated from the out-of-the-box code. Also, the entire CM project can be exported and imported into the subsequent environment.

CM Models

In addition to a custom project, you may need to create a custom model folder to organize your custom facts, dimensions, staging or replication objects. These should also be exported from the Development environment into the subsequent environment.

CM Metadata

All the CM metadata created during the customizations should be applied into the subsequent environments.

To simplify the process of migrating these:

1. Create a procedure CM_<PROD_FLG>_CREATE_METADATA.

2. Replace the <PROD_FLG> with the appropriate edge product code.

For example: CCB/NMS

3. Add appropriate data population scripts.

These should be written as merge statements so that existing rows are skipped and only new rows are added. In case the metadata requires corrections, use the update clause of the merge statement.

All tasks within the procedure should have the logical schema set to “Metadata”. The schema names should not be hard coded.

In addition, create a package CM_<PROD_FLG>_CREATE_METADATA. Add the created procedure as the first step and add the scenario B1_CFG_METADATA as a second step. After migration the CM project to the new environment, execute this step after the addition of the product instance. This job should be executed in the newly created context for the product.