Introduction

The Intershop Integration Hub is a platform for connecting different systems and applications in e-commerce projects. This document outlines the architecture, purpose, and features of the platform, as well as the business processes it covers.

The target audience for this document are developers working on Intershop implementation projects. The platform is meant to facilitate the exchange of orders, order history, inventory, customer data, prices, and product information, among other business objects.

The Intershop Integration Hub uses a low-code approach, meaning integration can be achieved without extensive programming. It provides a flexible and scalable solution for automating business processes, reducing manual effort, and improving efficiency. Features such as monitoring, logging, data mapping, and transformation are included to help manage integrations effectively.

This document provides an overview of the Intershop Integration Hub and its capabilities, aimed at helping developers understand the platform and make informed decisions on how to use it in their projects.

References

• https://simplifier.io/en/

• https://community.simplifier.io/doc/current-release/integrate/connectors/

• https://community.simplifier.io/doc/current-release/integrate/business-objects/

Architecture

The Intershop Integration Hub fits well into a composable architecture as the low-code integration layer that connects the packaged business capabilities and the systems of record. The Intershop Integration Hub offers a range of connectors that allow for the integration of different systems and applications, without the need for custom code.

The Intershop Integration Hub is based on the low-code platform Simplifier, operated by Intershop.

There are two typical integration scenarios between Intershop ICM/IOM and the Intershop Integration Hub.

1. Intershop calls the Integration Hub.

   1. In this scenario, the Integration Hub has a business object configured that exposes its methods as REST API. This REST API is then called by Intershop ICM or IOM, for example, by a service adapter of the ICM Managed Service Framework.

2. The Integration Hub calls Intershop ICM or IOM.

   1. In this scenario, the Intershop REST API is called by the Integration Hub. A business object configured in the Integration Hub controls the flow of data using business object script. The business object uses preconfigured connectors to easily connect to ICM/IOM or the systems of record.

Connectors

The Intershop Integration Hub comes with a set of standardized connectors, most importantly REST, SOAP, SAP RFC, ODATA V2, CSV. These connectors can be easily configured and interactively tested.

Connectors can be generated automatically using the connector wizard for SAP, OpenAPI (Swagger) documentation for REST, or a SOAP WSDL.

Connectors do not contain any business logic, they basically just wrap the API calls, similar to Postman collections.

For more information see: https://community.simplifier.io/doc/current-release/integrate/connectors/.

Business Objects

To implement mapping or caching logic, the Intershop Integration Hub provides the concept of Business Objects. Business Objects can have functions (methods). Functions have input and output parametes. The function itself is implemented in so called Business Script which is a variation of JavaScript. Within the business script it is easily possible to call connectors and to handle the JSON responses. This approach is very flexible, so that even complex mapping or caching logic can be implemented quickly and efficiently.

Every business object function is automatically exposed as REST API and can be used externally.

For more information see: https://community.simplifier.io/doc/current-release/integrate/business-objects/.