Skip to main content

In my previous blog I demonstrated how ODI Scenarios can be exported with one click using ODI's Toolbox features. In this blog, I will show how to do the same for ODI Scenario imports. Just like the manual exports from ODI Studio, you always have the option to manually import each Scenario one at a time to your ODI Execution Repository. But if you have a lot of them to import, it can get tedious and time consuming.

It is a common practice within ODI to export ODI Packages, Interfaces, Procedures, Variables, Scenarios, and other artifacts. You always have the option to go to ODI Studio and manually right click on each artifact and click export, but it can get pretty hairy and time consuming if you have more than a handful of them. Add to that, if you are exporting ODI Scenarios to be deployed to another environment, you have to regenerate them before exporting. So now, you also have to individually regenerate every Scenario before individually exporting them.

It is a common scenario within ODI to want to know the results of the execution of a package or interface (aka ELT) and execute additional logic based on the initial result. For instance, you might want to execute interface X only if there were no inserts made into the target table of interface Y. Another scenario could be you want to send an email notification to an Admin if there were more than n number of inserts or updates made to the target table of the interface.

In my previous blog, I showed how to do an ELT from Oracle DB to XML in ODI.  Every ELT uses a Loading Knowledge Module (LKM), which describes how the data is loaded from one system to another, and an Integration Knowledge Module (IKM), which describes how the data is integrated in the target system. These Knowledge Modules are fully extensible and can be edited from within ODI Studio.

Oracle Data Integrator (ODI) is Oracle's data integration platform engineered to provide fast and easy data transformation and data integration processes, through E-LT (Extract - Load Transform) mechanism, between different technologies.  For example, using ODI's transformation mechanism I can create daily snapshots of my data residing in an Oracle DB and store these snapshots in a XML format.  These XML snapshot files can serve as XML payloads for an external web-service to consume this data.

Subscribe to ODI