sections in the article
This article lists the vocabulary related to packaged integrations in inriver.
An adapter is a packaged integration, connecting inriver to a specific external system. An adapter is not built on the inriver Integration Framework (IIF).
Adapter built using the integration framework
An adapter built using the Integration Framework is a packaged outbound integration, connecting inriver to a specific external system. It is built on the inriver Integration Framework and uses its adapter delivery approach.
Note! Adapters built using the Integration Framework do not necessarily replace adapters. There are use cases where it might not be applicable to use the Integration Framework, making the two coexist on the same implementation.
Connector is a more general term. It includes adapters and any inbound or outbound integration to and from inriver developed by a partner or customer, including for example any Listener or Scheduled extension.
A partner or customer connecting inriver to an external system for a specific implementation is considered a custom integration and is not to be confused with a packaged integration. Such custom integrations can be built on the inriver Integration Framework to benefit from the advantages that it provides.
Outputs in inriver Syndicate
Outputs in inriver Syndicate are the outcome of a Syndicate extension, for example files that are downloaded or sent to a file location, or data sent to an API.
Adapters, adapters built using the Integration Framework, connectors, outputs in Syndicate, and Syndicate API integrations are all integrations offered in a packaged format that can be reused and hence referred to as packaged integrations.
inriver Syndicate API integrations
inriver Syndicate API integrations are packaged solutions from inriver integrated directly to a target vendor platform.
Please sign in to leave a comment.