Integration Knowledge Modules (IKMs) and Check Knowledge Modules (CKMs) FAQS

1. What are Integration Knowledge Modules (IKMs)?

• IKMs define how data is integrated into the target datastore.
• They control the process of moving and integrating data from the source (or staging area) into the target during the execution.

2. What are Check Knowledge Modules (CKMs)?

• CKMs are used to define how data quality and integrity checks are performed on the data during the integration process.
• They ensure that the data meets the required standards before it is loaded into the target.

3. How do I select IKMs and CKMs?

• Typically, you select one IKM and one CKM for the target datastore.
• To do so, you select the target datastore in the diagram, then configure the IKM and CKM using the property inspector.

4. Can I use different IKMs for different target datastores?

• Yes, each target datastore can have its own selected IKM based on the specific requirements for integrating data into that target.

5. Can IKM handle data movement from a staging area to the target?

• Yes, if the staging area is different from the target, you can select a multi-technology IKM.
• This type of IKM can handle both moving and integrating data from the staging area into the target datastore.

6. What is the relationship between IKMs and CKMs?

• The IKM integrates data into the target, while the CKM ensures that the data quality and integrity are validated during the process.
• Both are typically configured together for effective data integration and validation.

7. What if I can't find the IKM or CKM I need?

• Only built-in Knowledge Modules (KMs) or KMs that have already been imported into the project or the global KM list can be selected. 
• Ensure that the appropriate KMs are imported into your project before proceeding.

8. How do I import KMs into my project?

• To use specific IKMs or CKMs, you need to import them into your project. 
• You can do this by accessing the appropriate module or knowledge base and ensuring the KMs are available in your project or the global KM list.

9. What happens if I select the wrong IKM or CKM?

• Selecting the wrong IKM or CKM could lead to incorrect data integration or validation issues.
• It’s important to ensure that the right modules are selected for the specific requirements of your data flow and target datastore.

10. Can I edit IKMs and CKMs?

• IKMs and CKMs can be modified in the property inspector. However, changes to built-in modules might require adjustments to the underlying configurations.
• Always ensure you have the correct settings for your integration requirements.

Integration Knowledge Modules (IKMs) and Check Knowledge Modules (CKMs)

1. Definition of IKMs and CKMs:
• Integration Knowledge Modules (IKMs) define how data is integrated into the target datastore.
• Check Knowledge Modules (CKMs) define how data integrity and quality checks are performed during the integration process.
2. Selecting IKMs and CKMs:
• Typically, one IKM and one CKM are selected for each target datastore.
• The IKM is responsible for integrating data into the target datastore.
3. Handling Staging Areas:
• If the staging area is different from the target datastore, the selected IKM can be a multi-technology IKM. This type of IKM is responsible for moving data from the staging area into the target datastore while handling integration tasks.
4. Defining or Changing IKMs and CKMs:
• To define or change the IKM and CKM, select the target datastore in the data flow diagram.
• Then, use the property inspector to configure or modify the IKM and CKM for that specific target datastore.
5. Important Note:
• Only built-in Knowledge Modules (KMs) or KMs that have already been imported into the project or the global KM list can be selected in the mapping.
• Ensure that the appropriate KMs are imported into the project before proceeding with selection.

Mapping Loading Knowledge Modules (LKMs) FAQS

1. What are Loading Knowledge Modules (LKMs)?

• Loading Knowledge Modules (LKMs) define how data is moved from one execution unit to another, typically from the source to a staging area. They play a crucial role in managing data transfers between different parts of the workflow.

2. How do LKMs work?

• An LKM is selected for each access point in a data flow. It dictates how data should be moved from the source to a staging area, or in some cases, from one staging area to a target when specific conditions are met (e.g., using a single technology IKM for the staging area).

3. When is an LKM used?

• LKMs are used when data needs to be moved between the source, staging area, and target in the execution process. They are selected for each access point to manage the data flow.

4. Can an LKM move data from a staging area to a target?

• Yes, an LKM can move data from a staging area (not located within a target execution unit) to a target, but only if a single technology IKM is selected for the staging area.

5. How do I define or change an LKM?

• To define or change an LKM, select the access point within your data flow diagram and use the property inspector to choose or modify the LKM configuration for that specific access point.

6. Do I need to select an LKM for every access point?

• Yes, each access point in the data flow needs to have an associated LKM to define how data is transferred between execution units.

7. What is the role of the Access Point in LKM configuration?

• The Access Point acts as the connection between two execution units, and an LKM is selected for each access point to control the data transfer between these units.

8. Can an LKM be used for data movement outside of the target execution unit?

• Yes, if the data is being moved from a staging area that is not located within the target execution unit, an LKM can be used to facilitate this data movement to the target.

9. What is the relationship between an LKM and a target?

• The LKM defines how data is moved to the target, either directly from the source or via a staging area, depending on the configuration of the data flow and execution units.

10. Can I use different LKMs for different access points in the same flow?

• Yes, you can select different LKMs for each access point in a data flow, depending on the specific data movement requirements for each connection between execution units.