Video: Introduction to integration framework (IIF)

Introduction to the inriver integration framework (IFF)

The Inriver Integration framework decouples standard adapters to better focus on integrating to the target system, and focus less on the Inriver part of the integration.

To specify how channels are exported the framework sets up the entity type ExportTarget. This entity contains information specific to a channel being exposed throughthe framework.
The PIM model is mapped using the integration_model of the integration framework. This is a JSON document that maps the model to the outbound model.

{
  "IntegrationsMapping": {
    "Product": {
      "EntityTypeId": "Product",
      "UniqueFieldTypeId": "ProductNumber"
    },
    "Variations": [
      {
        "EntityTypeId": "Item",
        "UniqueFieldTypeId": "ItemNumber"
      }
    ],
    "Bundles": [],
    "Catalog": {
      "EntityTypeId": "Channel",
      "UniqueFieldTypeId": "ChannelUniqueId"
    },
    "Category": {
      "EntityTypeId": "ChannelNode",
      "UniqueFieldTypeId": "ChannelNodeUniqueId"
    },
    "Media": {
      "EntityTypeId": "Resource",
      "UniqueFieldTypeId": "ResourceFilename"
    },
    "ExtendedAttributes": [],
    "AttributeGroups": []
  },
  "RelationsConfiguration": {
    "Associations": [],
    "IgnoredLinkTypeIds": [],
    "SoftLinksMapping": {},
    "CategoryConditionalExclusions": []
  },
  "VariationsConfiguration": {
    "StructuredData": {
      "FieldTypeId": "",
      "UniqueField": "",
      "SortOrderField": ""
    },
    "FieldTypeIdForVariationGroupId": "",
    "Variants": {
      "GlobalVariants": [],
      "FieldsetVariants": {},
      "FieldTypeVariants": {}
    }
  }
}

The JSON used for the demo environment.