Integration Knowledge Modules (IKM)

1. Role of the IKM:
• The IKM is responsible for writing the final, transformed data to the target tables.
• Each mapping uses a single IKM for each target that is being loaded.
2. IKM Execution Assumptions:
• When the IKM is started, it assumes that all loading phases for the remote servers have already been executed.
• This means:
• All remote source data sets have been loaded into "C$" temporary tables in the staging area via LKMs (Load Knowledge Modules).
• The source datastores are either on the same data server as the staging area or transparent access mechanisms have been set up for remote sources.
3. IKM Actions:
• The IKM’s primary task is to execute "Staging and/or Target" transformations, joins, and filters on the C$ temporary tables (or tables on the same data server or accessible through transparent access).
• The resulting data set after transformations and processing is typically:
• Written into an "I$" temporary table, or
• Directly loaded into the target table.
4. Data Writing Methods:
• Depending on the selected IKM in the mapping, the final transformed data can be:
• Appended to the target table.
• Compared for incremental updates or for slowly changing dimensions (SCDs).
5. Types of IKMs: There are two types of IKMs based on the server setup:
• IKMs for same-server staging and target datastore:
• These IKMs assume that the staging area and the target datastore are located on the same server.
• IKMs for remote staging and target datastore:
• These IKMs are used when the staging area and target datastore are on different servers.