Oracle Data Integrator 11g Knowledge Modules Description

RKM Oracle 

Reverse-engineers tables, views, columns, primary keys, non unique indexes and foreign keys.

JKM Oracle 10g Consistent (Streams)

Creates the journalizing infrastructure for consistent set journalizing on Oracle 10g tables, using Oracle Streams.

JKM Oracle 11g Consistent (Streams)

Creates the journalizing infrastructure for consistent set journalizing on Oracle 11g tables, using Oracle Streams.

JKM Oracle Consistent
Creates the journalizing infrastructure for consistent set journalizing on Oracle tables using triggers.

JKM Oracle Consistent (Update Date)
Creates the journalizing infrastructure for consistent set journalizing on Oracle tables using triggers based on a Last Update Date column on the source tables.


JKM Oracle Simple



Creates the journalizing infrastructure for simple journalizing on Oracle tables using triggers.


JKM Oracle to Oracle Consistent (OGG)



Creates and manages the ODI CDC framework infrastructure when using Oracle GoldenGate for CDC. See Chapter 26, "Oracle GoldenGate" for more information.


CKM Oracle



Checks data integrity against constraints defined on an Oracle table.


LKM File to Oracle (EXTERNAL TABLE)



Loads data from a file to an Oracle staging area using the EXTERNAL TABLE SQL Command.


LKM File to Oracle (SQLLDR)



Loads data from a file to an Oracle staging area using the SQL*Loader command line utility.


LKM MSSQL to Oracle (BCP SQLLDR)



Loads data from a Microsoft SQL Server to Oracle database (staging area) using the BCP and SQL*Loader utilities.


LKM Oracle BI to Oracle (DBLINK)



Loads data from any Oracle BI physical layer to an Oracle target database using database links. See Chapter 17, "Oracle Business Intelligence Enterprise Edition" for more information.


LKM Oracle to Oracle (DBLINK)



Loads data from an Oracle source database to an Oracle staging area database using database links.


LKM Oracle to Oracle (datapump)



Loads data from an Oracle source database to an Oracle staging area database using external tables in the datapump format.


LKM SQL to Oracle



Loads data from any ANSI SQL-92 source database to an Oracle staging area.


LKM SAP BW to Oracle (SQLLDR)



Loads data from SAP BW systems to an Oracle staging using SQL*Loader utilities. See the Oracle Fusion Middleware Application Adapters Guide for Oracle Data Integrator for more information.


LKM SAP ERP to Oracle (SQLLDR)



Loads data from SAP ERP systems to an Oracle staging using SQL*Loader utilities. See the Oracle Fusion Middleware Application Adapters Guide for Oracle Data Integrator for more information.


IKM Oracle AW Incremental Update



Integrates data in an Oracle target table in incremental update mode and is able to refresh a Cube in an Analytical Workspace. See Chapter 21, "Oracle OLAP" for more information.


IKM Oracle Incremental Update



Integrates data in an Oracle target table in incremental update mode.


IKM Oracle Incremental Update (MERGE)



Integrates data in an Oracle target table in incremental update mode, using a MERGE statement.


IKM Oracle Incremental Update (PL SQL)



Integrates data in an Oracle target table in incremental update mode using PL/SQL.

IKM Oracle Multi Table Insert
Integrates data from one source into one or many Oracle target tables in append mode, using a multi-table insert statement (MTI).


IKM Oracle Slowly Changing Dimension

Integrates data in an Oracle target table used as a Type II Slowly Changing Dimension.

IKM Oracle Spatial Incremental Update

Integrates data into an Oracle (9i or above) target table in incremental update mode using the MERGE DML statement. This module supports the SDO_GEOMETRY datatype.

IKM Oracle to Oracle Control Append (DBLINK)

Integrates data from one Oracle instance into an Oracle target table on another Oracle instance in control append mode.

This IKM is typically used for ETL configurations: source and target tables are on different Oracle instances and the interface's staging area is set to the logical schema of the source tables or a third schema.

SKM Oracle

Generates data access Web services for Oracle databases. See "Working with Data Services" in the Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator for information about how to use this SKM.

Encrypting and Decrypting a KM or Procedure

Encrypting a Knowledge Module (KM) allows you to protect valuable code. An encrypted KM cannot be read or modified if it is not decrypted. The commands generated in the log by an Encrypted KM or procedure are also unreadable.

Oracle Data Integrator uses a DES Encryption algorithm based on a personal encryption key. This key can be saved in a file and can be reused to perform encryption or decryption operations.

WARNING: 

There is no way to decrypt an encrypted KM or procedure without the encryption key. It is therefore strongly advised to keep this key in a safe location.

To Encrypt a KM or a Procedure: 

In the Projects tree in Designer Navigator, expand the project, and select the KM you want to encrypt.

Right-click and select Encrypt.

In the Encryption Options window, you can either:

Encrypt with a personal key that already exists by giving the location of the personal key file or by typing in the value of the personal key.

Or click Get a new encryption key to have a new key generated.

Click OK to encrypt the KM. If you have chosen to generate a new key, a window will appear with the new key. You can save the key in a file from here.

Note: If you type in a personal key with too few characters, an invalid key size error appears. In this case, please type in a longer personal key. A personal key of 10 or more characters is required.

To decrypt a KM or a procedure: 

In the Projects tree in Designer Navigator, expand the project, and select the KM you want to decrypt.

Right-click and select Decrypt.

In the KM Decryption window, either

Select an existing encryption key file;

or type in (or paste) the string corresponding to your personal key.

Click OK to decrypt.

Importing Knowledge Modules in ODI 11g

How to import Knowledge Modules

Go to Designer 
Go to the Project 
Go to the Knowledge Modules
Right click and click on Import Knowledge Modules




Select the directory from where you want to import the knowledge modules



Select the Knowledge Module to be imported.




Then it generates report of all the KM import , once the Import is successful .


Then the imported KM will be visible under the respective KM category.






open the imported KM by double clicking on it.
Change the name.
And click on save.

This is the way to import KM.

Introduction to Knowledge Modules

Knowledge Modules (KM) implement “how” the integration processes occur. Each Knowledge Module type refers to a specific integration task:

Reverse-engineering metadata from the heterogeneous systems for Oracle Data Integrator (RKM).


Handling Changed Data Capture (CDC) on a given system (JKM)


Loading data from one system to another, using system-optimized methods (LKM). These KMs are used in interfaces.


Integrating data in a target system, using specific strategies (insert/update, slowly changing dimensions) (IKM). These KMs are used in interfaces


Controlling Data Integrity on the data flow (CKM). These KMs are used in data model's static check and interfaces flow checks.


Exposing data in the form of web services (SKM).




A Knowledge Module is a code template for a given integration task. This code is independent of the Declarative Rules that need to be processed. At design-time, a developer creates the Declarative Rules describing integration processes. These Declarative Rules are merged with the Knowledge Module to generate code ready for runtime. At runtime, Oracle Data Integrator sends this code for execution to the source and target systems it leverages in the E-LT architecture for running the process.

Knowledge Modules cover a wide range of technologies and techniques. Knowledge Modules provide additional flexibility by giving users access to the most-appropriate or finely tuned solution for a specific task in a given situation. For example, to transfer data from one DBMS to another, a developer can use any of several methods depending on the situation:

The DBMS loaders (Oracle's SQL*Loader, Microsoft SQL Server's BCP, Teradata TPump) can dump data from the source engine to a file then load this file to the target engine

The database link features (Oracle Database Links, Microsoft SQL Server's Linked Servers) can transfer data directly between servers 

These technical strategies amongst others corresponds to Knowledge Modules tuned to exploit native capabilities of given platforms. 

Knowledge modules are also fully extensible. Their code is opened and can be edited through a graphical user interface by technical experts willing to implement new integration methods or best practices (for example, for higher performance or to comply with regulations and corporate standards). Without having the skill of the technical experts, developers can use these custom Knowledge Modules in the integration processes.