Previous Step

IH-ETL Guided Setup Step 5 - Relationship Mapping

After you configure the mapping, you are ready to see what the data looks like. Run an integration test and view a summary of the results for the sample data. The summary includes total numbers for relationships that were created, mapped classes, partial and incomplete payloads that IRE couldn’t process. You can also view detailed messages from RTE and IRE. After you view the details in the summary page, you can return to any step to make adjustments and then rerun the integration. Below is an example:

1. Click “Preview Mapping Results”

2. Click “Run Integration”

Be aware that this executes your transform map and loads data into CMDB. You always have the options to rollback loaded data later.

3. Execution might take a little while. After it executes you should see your results

4. Click “Edit Mapping” or “Mark as Complete”

The system prompts you to roll back your changes or retain your data.

5. If you want to delete the CIs created by your preview, select “Perform Rollback”

6. If you want to retain the CIs in your CMDB, select “Retain Data”

Tips and Caveats

A conditional class lets you map different sets of data records to different target classes according to specific column values, or the status of a specific plugin.

Preview Result Size

Use property “sn_int_studio.preview.size” to control preview result size (max 10k). By default, IH-ETL will only process 100 input rows.

Partial Payload

• IRE unique identification requires that the payload item has source_native_key values, or the full set of the identification criterion attributes specified for the CI class, or both
• IRE isolates items for which data sources did not provide enough information to uniquely identify the CI and therefore processing cannot continue
• Some of these items are identified as partial items, which get stored for potential later processing
• For example: SCCM has multiple feeds such as a disk feed and a computer feed. The disk feed might have complete information about the disk but insufficient information about the computer CI that it depends on

Below are scenarios that will be identified as partial payload

• MISSING_MATCHING_ATTRIBUTES –— Item does not have identification criterion attributes to use at least one identifier entry for matching
• REQUIRED_ATTRIBUTE_EMPTY –— Unable to create a CI because a required attribute is missing
• MISSING_DEPENDENCY –— Dependent CI is missing a dependency relation which is specified in the payload
• INSERT_NOT_ALLOWED_FOR_SOURCE –— An IRE data source rule prevents the specified data sources from creating CIs of the specified class

Partial payload IRE documentation

Refer to FAQ section for common error scenarios and solutions

Incomplete Payload

A payload item is determined to be an incomplete item if:

• It does not contain all the data necessary for IRE unique identification, and
• It has an error that is not associated with a partial item

IRE unique identification is not possible if neither source_native_key, nor the full set of identification criterion attributes specified for the CI class, is provided.

Incomplete payload IRE documentation

Refer to FAQ section for common solutions

Additional Resources

Landing page

IH-ETL common error scenarios

Next Step

FAQs and debug process for common error scenarios