sections in the article
This article gives an overview of the inriver Integration Framework (IIF) is and its features.
About the integration framework
The Integration Framework is the foundation when building adapters and outbound integrations going forward. By providing standard functionality in a standard format, the framework lets you create adapters and integrations with less effort and higher quality.
The Integration Model is configured as a server setting called INTEGRATION_MODEL that applies to all your adapters and/or integrations built using the Integration Framework.
To understand how the configuration of the Integration Model works, read this article. Note! to access further documentation you need an inriver License. 
Fill in the Contact us form here for more information or Book a Demo with us here.
Key features
Below is a summary of the key features of the Integration Framework:
- Transforms each customer’s unique Elastic Data Model into a standard integration model through configuration only.
- Supports custom EntityTypes.
- Provides out-of-the-box functions for delta functionality.
- Provides standard functions to deliver Product data, Bundles, Catalog data, and Value lists in JSON format.
- Simplifies processing of the feedback data.
Integration framework components
Below is an illustration describing the different components of the integration framework.
- The blue blocks are existing systems.
- The green blocks are components provided out of the box as part of the integration framework.
- The orange blocks are target system-specific implementations required.
Read more about the core components of the Integration Framework in this article.
Supported inriver concepts
In addition to the standard inriver functionality, the Integration Framework supports the following inriver concepts:
- Bundle/Look
- Custom EntityTypes
- LinkEntityType
- Delta processing
- Product variations, including
- SKU as an EntityType
- SKU as a structured field (JSON)
- Specifications
- Softlinks (The use of a CVL field on both source and target entities, to link them together.)
- Multi-channel/Multi-store setup
- Process Feedback loop
- Channel filters
Creating adapters
Since the Integration Model is provided as metadata and the available standard functionality provides the required data, there is less need for inriver-specific skills to create outbound integrations.
Read more about creating adapters using the Integration Framework in this article.
Accessing the integration framework
You must have a license agreement in place to download and use the Integration Framework. Interested to learn more? Fill in the Contact us form here for more information.
Once you have a license you will be able to access the download link in this article. Note! If no license is in place you will receive an error message when attempting to use the link.
Further reading
Get an inriver license to view below content:
Comments
4 comments
Link is broken: "https://servicecenter.inriver.com/hc/en-us/articles/360010238859"
Hi @....
Thank you for flagging this! :)
Currently the link/article you are referring to is only available for a selected early access group, That is why it seems broken to you.
I am happy that you are interested to learn more about the integration framework! I can imagine that we will announce when we release more documentation! So continue to keep an eye open! ;)
If you have more questions let me know.
Nicky
Nicky Lilja ,
It'd probably be worth flagging all articles about restricted/limited access features as such so the reader knows it's not something they can use.
Hi Steven Christensen , Yes I agree. We will have a look at how we will visualize this.
Thank you both !
Please sign in to leave a comment.