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.
Facts and figures
Entities/Frequency
Imported Entities | Products (Delivery Date only) |
---|---|
Product Images | |
Prices | |
MSI | |
Customer | |
Customer Adresses | |
Companies | |
Import Frequency | Stock, MSI + Product:
|
Price
| |
Images
| |
Customer, Customer Addresses + B2B Companies
|
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 |