Why Pacemaker?

In the beginning, several interfaces had to be considered for this project. The AS400 had been installad alongside with the original system. The price and stock import had to be adapted by taking the different stock levels into account - based on the newly available Magento 2.3 MSI (Multi Stock Inventory). 

In addition to the transformation of the import files provided by the AS400 system, the import of customers and customer addresses was the biggest challenge in setting up the Unified-Commerce-Platform for HÖGL. To further optimize the complex situations for data import/export, the Pacemaker was integrated.

HÖGL shoe fashion GmbH

Josef Högl founded his company with a lot of pioneering spirit and zest for action, which - grown over 80 years and generations - inspires women around the world with high-quality and fashionable women's shoes.

Challenge

The import files presented by the AS400 could be provided in the required CSV format with UTF-8 encoding. One of the difficulties of the project was to extract the provided data into the different entities and present it in UTF-8 format. Therefore Pacemaker ensures that the conversion and import processes operate efficiently and helps to avoid functional conflicts.

Solution

Among other things, Pacemaker comes with libraries that offer the functionality to convert different import formats into the expected standard CSV format. During the conversion, the accumulated files are extracted from the AS400 system for the respective target entities, such as the customer data. 
The transformation itself was realized based on the Pacemaker libraries with an additional step and fitted seamlessly into the process by a simple adaption of the configuration of the workflow engine.

Result

The conversion and import processes have been optimized for performance, while Pacemaker prevents collision with other procedures such as indexing. This avoids data inconsistency and guarantees that the products displayed in the Online Store are always up-to-date. The processing can be monitored within the Magento backend and is entirely transparent for the customer and the solution partner who manages the unified commerce platform.

Facts and figures

Entities/Frequency

Imported Entities

Products (Delivery Date only)

 

Product Images

 

Prices

 

MSI

 

Customer

 

Customer Adresses

 

Companies

Import Frequency

Stock, MSI + Product: 

  • Frequency: max. every 15 minutes
  • Runtime: ~8 seconds
 

Price 

  • Frequency: max. every 30 minutes
  • Runtime: ~60 seconds
 

Images  

  • Frequency: manual
  • Runtime: ~2 minutes
 

Customer, Customer Addresses + B2B Companies 

  • Frequency: triggered by AS400
  • Runtime: ~1 second

 

Amount of Data

Websites 

~ 50

Stores

~ 50

Store View

~ 70

Attibute Sets

~ 5

Attributes

~ 140

Attribute Options

~ 1.700

Categories

~ 119

SKUs

~ 52.000

 

~ 49.500 Simples

 

~ 2.300 Configurables

Customers

n/a

Customer Adresses

n/a

Companies (B2B)

n/a

Product Images

5 GB, as Akeneo had problems to handle this amount of images

 

Components

Pacemaker 1.1.*

Converter

 

Process-Pipelines

 

Customer Pipeline

 

Price Pipeline

 

Stock Pipeline

M2IF PE 3.7.*

Default Mode (No Single Transaction)

 

Performance Booster (via Batch Processing

 

Multi-Source-Inventory (MSI)

 

Companies

 

System

Magento Version

Magento EE 2.3 + MSI + B2B

PIM

Akeneo 2

ERP

AS400