Skip to main content

Enactor Approach to Integration

Enactor Approach to Integration​

Slide 13

Data Architecture Overview - Integration​

Data Providers
Master Data Providers
PIM
Merchandise
HR
Master Data →
API Providers
CRM
Inventory
Loyalty
Product / Basket / Order
← API Request / Response →
Enactor
Enactor Central Components
Enactor Estate Manager
Database
Enactor Commerce APIs
↓ Master Data & Configuration↑ Transactions↕ API Request / Response
Store Devices
Database
POS & Mobile Devices
Enactor JavaScript API
Data Consumers
→ Transaction Data Export (Enactor XML / External)
Transaction Data Consumers
Finance
BI
Inventory
Audit / Loss Prevention
← API Request / Response →
API Consumers
Webshop
Mobile Apps
3rd Party Sales Tools
← Data Exchange
Web Front-End
Search & Select
Interactive Sales Tools

Integration Approach​

  • Application Master Data - Typically file import/exports with transforms but also background processes that read and write to messages queues and web services
  • Transaction / Event Data - Typically transactions in XML format posted to web services or message queues and sometimes files
  • Dynamic Data - Generally web service calls or message queues
  • Shared Processes - Generally web service calls orchestrated by Business Process engine
  • POS to embedded Website - Exchanging the data between an Website and the POS using a JavaScript Library

Further Reading​

For additional information and further reading on the Enactor Integration Approach, please see the following guides:

DocumentDescription
Inbound Integration Guide - IntroductionFile-based and master data integration approach
REST API IntroductionAPI and service-based integration approach
Outbound Integration Guide - IntroductionOutbound integration approach