What is an ODI Knowledge Module (KM)?

by Ashok Das

Knowledge Modules (KM), components of Oracle Data Integrator’s Open Connector Technology, are generic, highly specific, and reusable code templates that defines the overall data integration process. Each Knowledge Module contains the knowledge required by ODI to perform a specific set of actions or tasks against a specific technology or set of technologies, such as connecting to this technology, extracting data from it, transforming the data, checking it, integrating it, etc.

Oracle Data Integrator provides a large number of knowledge modules out-of-the-box. Knowledge Modules are also fully extensible. The code can be opened and edited through a graphical user interface to implement new integration methods or best practices (for example, for higher performance or to comply with regulations and corporate standards).

ODI Uses Six Different Types of Knowledge Modules

1. RKM (Reverse Knowledge Module) is used to perform a customized reverse-engineering of data models for a specific technology. It extracts metadata from a metadata provider to ODI repository. These are used in data models. A data model corresponds to a group of tabular data structures stored in a data server and is based on a Logical Schema defined in the topology and contains only metadata.

2. LKM (Loading Knowledge Module) is used to extract data from heterogeneous source systems (files, middleware, databases, etc.) to a staging area. These are used in Interfaces. An interface consists of a set of rules that define the loading of a datastore or a temporary target structure from one or more source datastores.
3. JKM (Journalizing Knowledge Modules) are used to create a journal of data modifications (insert, update, and delete) of the source databases to keep track of changes. These are used in data models and for Changed Data Capture.
4. IKM (Integration Knowledge Module) is used to integrate (load) data from staging to target tables. These are used in Interfaces.
5. CKM (Check Knowledge Module) is used to check data consistency i.e., constraints on the sources and targets are not violated. These are used in the data model’s static checks and interface flow checks. Static check refers to constraints or rules defined in the data model to verify the integrity of source or application data. Flow check refers to declarative rules defined in interfaces to verify an application’s incoming data before loading it into target tables.
6. SKM (Service Knowledge Module) is used to generate code required for data services. These are used in data models. Data Services are specialized web services that enable access to application data in datastores and to the changes captured for these datastores using Changed Data Capture.