introduction to adobe experience manager based e commerce
TRANSCRIPT
© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
A virtual developer conference for Adobe Experience Manager
Introduction to Adobe Experience Manager Based eCommerceVarun Mitra | Partner Training Instructor
© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.
Introduction to Adobe Experience Manager Based eCommerce
2
1 | Introducing the eCommerce Framework2 | eCommerce Concepts with Elastic Path3 | Catalog blueprint and section blueprint capabilities4 | Identifying Best Practices for Stores .
© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 3
Introducing the eCommerce FrameworkeCommerce Architecture
© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 4
The Adobe Experience Manager eCommerce architecture consists of four layers:1. eCommerce components
Adobe Experience Manager eCommerce components provide the front-end functionality and the shop as viewed by the user. They rely on the eCommerce API to retrieve product data and perform actions related to the commerce eCommerce engine.
2. eCommerce API The central piece of the Adobe Experience Manager eCommerce architecture is the
Adobe Experience Manager eCommerce API. Based on the API, front-end components can be built to implement an eCommerce application.
The Adobe Experience Manager eCommerce API is fixed, and cannot be adapted.
AEM eCommerce Architecture
© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 5
3. eCommerce provider implementation The eCommerce API can be implemented to integrate with a third-party eCommerce
application, or you can create a custom (native) implementation. Out-of-the-box, Adobe Experience Manager provides a native implementation based
on CRX/JCR, as well as an implementation to integrate Elastic Path.
4. eCommerce engine The eCommerce engine is the eCommerce backend integrated in the provider
implementation. In most cases, it is a third-party eCommerce software, such as Elastic Path or an existing or legacy eCommerce solution.
The sample native implementation provided by Adobe Experience Manager for the geometrixx demo site uses the CRX repository itself as the eCommerce engine.
AEM eCommerce Architecture
© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 6
eCommerce Concepts with Elastic Path The integration framework
provides the mechanisms and components for:
Connecting to an eCommerce system
Pulling data into Adobe Experience Manager
Displaying data and collecting the shopper's responses
Searching data from both systems Returning transaction details
This means:1. Shoppers can instantaneously
register and shop2. Price changes are immediately
visible to shoppers
3. Products can be added as required
© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 7
Catalog Management
Master and Sales Catalog
Product data cache
Catalog blueprint Product pageTemplates
Experience
Physical touch points
Marketing data
Elastic Path eCommerce
© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 8
Catalog Management (cont’d) Catalog Blueprint
Provided by Adobe Experience Manager to create a catalog and is in /content/catalog
Catalog Has a specific LiveSync mechanism tied to catalogs
Product importer configuration Full product import Retrieve live price
© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 9
Best Practices For all implementations, keep the
following in mind: As product, stock-keeping units, and
categories can be numerous, try to use the fewest nodes possible to model the content.
Avoid duplication. Or, when used, think about how many nodes your duplication will lead to.
Tag your content to prepare the query optimization.
Scaling eCommerce:1. Offload asset post processing to
a dedicated instance.2. Only import product data.3. Import throttling and batch
saves.
© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential.© 2016 Adobe Systems Incorporated. All Rights Reserved. Adobe Confidential. 10
Varun [email protected]
LinkedIn: Varun mitra