« Best Practices building Data Services with ODI-EE | Main | Using an ODI Procedure to Loop Through a Command »

How to Customize ODI-EE through Knowledge Modules

In this article entitled "Developing a Knowledge Module in Oracle Data Integrator", Uli Bethke outlines what Knowledge Modules (KMs) are and how to customize and build an Integration Knowledge Module.

Uli writes:

The power of KMs lies in their reusability and flexibility—for example, you can develop and implement a loading strategy for a fact table and then, with a click of a mouse, apply this loading strategy to all of your fact tables. If you adapt your ELT strategy to changing business requirements and modify the associated KM, all interfaces that use the KM inherit the changes. You can mix and match different programming languages, types, and styles (native RDBMS SQL, scripting languages such as Jython or JavaScript, or even Java). This is what makes these KMs extremely flexible. This innovative approach is called Oracle Data Integrator Declarative Design and can be up to 10 times faster than traditional ETL approaches.

At Oracle we're constantly innovating our broad coverage of Knowledge Modules. Check out our OTN page for ODI-EE and click on Knowledge Module Reference to get more information.

TrackBack

TrackBack URL for this entry:
http://blogs.oracle.com/mt/mt-tb.cgi/12425

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

About This Entry

This page contains a single entry from the blog posted on June 12, 2009 9:19 AM.

The previous post in this blog was Best Practices building Data Services with ODI-EE.

The next post in this blog is Using an ODI Procedure to Loop Through a Command.

Many more can be found on the main index page or by looking through the archives.

Top Tags

Powered by
Movable Type and Oracle