Steps for ODI Migration from One Environment to other

Steps for Code Migration from DEV to other Environment

(On Target Environment) Take backup of Security Settings and ODI Repository.

·         ODI Repository: Backup the target ODI repository by taking a database dump of the ODI repository schema using Oracle Database export utility.

·         Security Backup: Similarly, you may backup just the security metadata from the target ODI repository. To do this, invoke the security export dialog as  shown below.

\And Now Click on “Export”.

STEP 5 : On Source Environment: Now, login to the ODI repository in the source environment from ODI Studio. Export the customized objects using Smart Export by clicking on the icon on the top right of the Designer tab and choosing “Export…” as shown. Then choose “Smart Export” in the dialog that pops up.

When you drag the objects into the Smart Export, the dependent objects are computed and automatically dragged in as well. For example, when task folders containing interfaces are dragged in, the data stores corresponding to the interfaces are automatically dragged in. Thus, if you have changed an interface and the corresponding target data store, it is enough to drag the interface/task folder and the data store will be automatically exported. After you drag and drop the required objects into the smart export window, you can review what is going to be exported including the dependent objects before executing the export.

Note: When dragging and dropping mapping folders, you may be asked for a confirmation whether to automatically add all objects with the same release tag; in this case, select NO.

On Target Environment: Copy the export files to a drive on the target machine. Log in to the ODI repository in target environment from ODI Studio. Invoke the “Import” -> “Smart Import” option by clicking on the same icon on the top right of the Designer tab. Select the file to be imported; in case of multiple files to be imported, select the files one at a time in the same sequence as they were exported.

Verify Things and Click “Next”  and then Click on “Finish” .

Click Next and  review the import before submitting. Complete the import.

 On Target Environment Now Import topology settings which we have taken in STEP 4 Now, you need to import the topology settings from the backup taken in step 4. For this, click on “Import” from topology navigator and  then “Smart Import”. Select the xml file that was created in step 4 and complete the import.

Review and Close.

Go to “Topology” then “Physical Architecture” then “Oracle” then “BIAPPS_ODIREP” and Double Click on it.

2: Go to “Definition” tab and now you will see the User and Password box.

If these details are not there then put the right credentials as below.

3: Then go to “JDBC” tab and check JDBC Driver and JDBC URL details. If these details are not present then put these details.

4:  Now Click on “Test Connection”

Check Default Checkbox is enabled for all physical schema or not ?

1) Connect to the ODI repository using ODI client

2)  Navigate to ODI > Topology > Physical Architecture > Technologies >  Oracle and Expand  BIAPPS_BIACOMP ( CM Read only Data server used for ETL ) data server.

3) Click on Physical schema registered under this data server.

4) Check for Default check box option is selected or not.

 If not please check this option and save the physical schema changes.

5). Each of the Datawarehouse (DW), ODI_REP or BIACM data servers should have a default data schema.

So, if not already done, perform the above steps for DW data server as well