Tuesday 11 October 2011

ODI Knowledge modules


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.

MONDAY, 9 MAY 2011

Importing Knowledge Modules in ODI 11g

Hi Guru's,

I will discuss 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.




Thanks Gurus
Ram Kumar Lanke


SATURDAY, 7 MAY 2011

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. 

www.odiguru.com
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.

1 comments:

Unknown said...

Hi All,



I'm facing this issue i.e;



we are implementing CDC

my Source is Turbo image

Target is ms sql server

But we don't have a JKM for Turbo image, So what i should do this situation.

if i want to use customize the JKM, How it write could you pls tell me steps ?

which LKM , IKM's are impot ?

after importing KM's In mapping level Flow tab any conditions i have to give ( Target level )?



Thanks in advance,

Post a Comment

Twitter Delicious Facebook Digg Stumbleupon Favorites More

 
Powered by Blogger