Mapping Knowledge Modules

1. Definition of Knowledge Modules (KMs):
• Knowledge Modules (KMs) define how data is transferred between data servers and loaded into data targets.
• There are different types of KMs based on their specific function, such as IKMs, LKMs, EKMs, and CKMs.
2. Importing Knowledge Modules:
• KMs that are to be used in a data flow must either be imported into the project or be available as global KMs.
• These KMs must be available to select for defining how data flows and transformations will be handled in your mapping.
3. Types of Knowledge Modules:
• IKMs (Integration Knowledge Modules):
• IKMs define how the actual transformation and loading of data is performed.
• They are responsible for transforming the data and inserting it into the target system.
• LKMs (Loading Knowledge Modules):
• LKMs specify how data is transferred between one data server to another.
• They define the mechanism of moving data from source to target (e.g., using JDBC or database links).
• CKMs (Check Knowledge Modules):
• Flow Control CKMs: Used to check for errors in the data flow during the loading of records into a target datastore.
• Static Control CKMs: Used to check for errors in a table at any time, allowing you to check whether the data satisfies constraints.
• CKMs can be launched on a model to validate the integrity of data before or after loading.
• EKMs (Extract Knowledge Modules):
• EKMs are used to extract data from the source systems before processing and transformation. (Note: EKMs are not mentioned in detail in the provided notes, but they are typically used for extraction tasks.)
4. Selecting Knowledge Modules:
• You can select an appropriate KM for each task based on the specific needs of the data integration process.
• For example, you can select:
• JDBC to transfer data between two databases.
• Oracle Database Link to transfer data between two Oracle databases.
5. KM Strategy:
• The KM strategy involves choosing the correct Knowledge Modules based on the data flow, transformation needs, and error-checking requirements.
• For each step of the flow, you choose a KM to specify how the task (e.g., loading, transformation, checking) will be performed.