Version Management in ODI

8/10/2019 Version Management in ODI

1/5

Working with Version Management in ODI:-

This section describes the versioning of objects like scenarios, Interfaces, packages etc., in Oracle Data

Integrator 11g.

Versioning is a smart method of implementing certain condition or multiple conditions, objects for a

particular interface, package or scenario without having to create multiple objects. A version is a backup

copy of an object. It is checked in at a given time and may be restored later. Versions are saved in the

master repository. They are displayed in the Version tab of the object window as shown below in the

screen shot.

The following objects can be checked in as versions:

Project, Folder

Package, Scenario

Interface, Procedure, Knowledge Module

Sequence, User Function, Variable Model, Model Folder

Solution

Load Plan

Versioning of an object is useful when we are trying to apply an Application Patch to Oracle BI Application

Environment. Consider the situation in which the application patch which we are trying to apply is affecting

the object in which we had done some customizations. In such case if we have done customizations as per


2/5

the customization methodology i.e., the outof-the box ETL task should have been copied and both the

original task and copied task are versioned then we can use the compare utility. Below are the high level

steps to be followed:

1.)

Before applying customization we need to create a version for the object.

2.)

All the customizations should be developed to separate folders. Eg: - CUSTOM_SDEContains all

the customizations done to the SDE mappings.

3.)

All the Patch objects should be imported in separate folders. Eg: - PATCH_SDEContains all the

Patch objects which are related to SDE Mappings. This is to have a copy of the patched objects in

separate folder.

4.)

Prior to application of patch, create a version of outof-thebox ETL Task.

5.)

After applying the patch, we can compare the current version with prior version to identify any

changes. While applying the patch ensure that it is applied in the OOB folder.

6.)

The OOB Mappings should get over written but we do have a version of the old object which can be

used to compare. We can now compare the OOB version of the object and the Patched object.

7.)

Manually apply these changes to the copied task that was customized i.e., the tasks present in the

custom folders.

8.)

Regenerate the scenario for the customized task so that Load plan would pick these changes.

Below are some sample screenshots. Please do note that these are just sample screenshots and actual

folders structures in ODI would vary across different projects and would depend on the coding standards.

Screenshot showing Customization Folder:-

Screenshot showing Out -Of-Box Folder:-


3/5

Screenshots showing the Folder for Patch objects:-

Screenshot showing the compare Utility in ODI:-


4/5

Screenshot showing the 3 versions:-

Screenshot for Comparison of OOB and Patching versions:-


5/5

Screenshots showing the comparison:-

By comparing the version we can identify the differences between Out of Box and Patch versions of the

object. The difference is the change in the logic for the Revenue Amount column as shown.

We will now apply the difference in the Customized Object which is present in the Custom Folders. We will

baseline the old code created a version for future reference and apply this change. Once unit testing is

completed we will create a new scenario and make changes in the load plan so that this change gets

reflected in the next loads.

Documents

Version Management in ODI