3. AEM - eCommerce Integration Patterns
Gowrishankar Viswanathan
Reference Architecture
3
Web Server, CDN
Application Tier
Web Tier
MDM IAM CRM ERP OMS Data Tier
REST ESB API SSO Payments Services Tier
Enterprise Search Web Apps
AEM eCommerce (PIM / PCM)
Portal Mobile Apps
DAM PoS
Analytics
Target
Campaign
Audience Manager
4. AEM - eCommerce Integration Patterns
Gowrishankar Viswanathan
Platform Evolution
¤ Core Platform consists of
¤ WCM
¤ Commerce Engine
¤ Evolution
¤ New WCM and Commerce Engine
¤ Replace one of existing platforms
¤ Upgrade from a single platform for both content and commerce
¤ Start with Commerce Engine, then introduce WCM (AEM)
4
7. AEM - eCommerce Integration Patterns
Gowrishankar Viswanathan
Unified UI Pattern
7
Web Server
End Users
Browser
AEM
Commerce
Backend
UI
Content
Products
Meta-data
Users
Services
Search
¤ AEM is the only presentation layer
¤ Commerce Engine Integration for importing
Products, Taxonomy, Meta-data into AEM
¤ Run-time integration with Commerce
Engine for dynamic attributes look-up,
authentication, cart
¤ Run-time service calls are stateless
¤ Enterprise Services integration for backend
services, SSO, search and other services as
needed
¤ For high volume catalogues, consider
alternatives to importing as needed
¤ Dynamic lookup from Commerce Engine
¤ Move all products to an Intermediate Layer –
Ex: Search Engine
¤ Apply Web Server Proxy (mod_proxy) to
integrate Ajax services
¤ Develop proxy servlet (as needed) for Author /
Publisher integration with Ajax services
Batch
Real-time
Master Data
8. AEM - eCommerce Integration Patterns
Gowrishankar Viswanathan
Modern Web Application Framework
8
Web Server
End Users
Browser
AEM
Commerce
Backend
Content Services
Products
Meta-data
Users
Services
Search
¤ The Presentation layer is embedded in AEM
¤ Presentation Layer could also be directly
deployed to the Web Server
¤ Commerce Engine would provide
Commerce Services for integration with UI
handlers in front-end
¤ Run-time integration with Commerce
Engine for dynamic attributes look-up,
authentication, cart
¤ Run-time integration with AEM for content
Services
¤ Run-time service calls are stateless
¤ Enterprise Services integration for backend
services, SSO, search and other services as
needed
¤ Complex AEM Preview customization is
needed
¤ Custom Content Entry methods are used in
some cases – Eg: Excel importBatch
Real-time
Products
Meta-data
UI
UI
Master Data
9. AEM - eCommerce Integration Patterns
Gowrishankar Viswanathan
Distributed UI Pattern
9
¤ AEM shares presentation layer with
Commerce Engine
¤ Service based Commerce Engine
Integration for building global UI elements
in AEM and session synchronization
¤ Session Synchronization could be achieved
in multiple ways
¤ Shared Cookie
¤ Pixel include
¤ Commerce Engine is positioned as UI Layer
for Commerce Content
¤ Synchronization of content Activation is
essential
¤ Apply Web Server Proxy (mod_proxy) to
integrate with Commerce UI and Services
¤ Develop proxy servlet (as needed) for Author /
Publisher integration with Content UI and
services
Batch
Real-time
Web Server
End Users
Browser
AEM
Commerce
Backend
Marketing Content
UI
PDP
Checkout
Profile
Users
Services
Search
Master Data