- Deploying User Guide
- Introduction to the AEM Platform
- Deploying AEM
- Deploying and Maintaining
- Recommended Deployments
- Application Server Install
- Custom Standalone Install
- Command Line Start and Stop
- Configuring node stores and data stores in AEM 6
- Revision Cleanup
- How to Run AEM with TarMK Cold Standby
- RDBMS Support in AEM 6.4
- Oak Queries and Indexing
- Indexing via the Oak-run Jar
- Oak-run.jar Indexing Use Cases
- Troubleshooting Oak Indexes
- Opting Into Aggregated Usage Statistics Collection
- Troubleshooting
- Configuring AEM
- Basic Configuration Concepts
- Logging
- Configuring OSGi
- OSGi Configuration Settings
- Run Modes
- Web Console
- Replication
- Replicating Using Mutual SSL
- Troubleshooting Replication
- Expiration of Static Objects
- Version Purging
- Monitoring and Maintaining Your AEM instance
- Offloading Jobs
- Single Sign On
- Resource Mapping
- Enabling HTTP Over SSL
- Consistency and Traversal Checks
- Performance Guidelines
- Performance Optimization
- Assets Performance Guide
- Configuration How-To Articles
- Removing the Geometrixx Sites
- Configuring Web Console
- Upgrading to AEM 6.4
- Upgrading to AEM 6.4
- Planning Your Upgrade
- Assessing the Upgrade Complexity with the Pattern Detector
- Backward Compatibility in AEM 6.4
- Upgrade Procedure
- Using Offline Reindexing To Reduce Downtime During an Upgrade
- Performing an In-Place Upgrade
- Lazy Content Migration
- Using the CRX2Oak Migration Tool
- Pre-Upgrade Maintenance Tasks
- Post Upgrade Checks and Troubleshooting
- Upgrading Custom Search Forms
- Sustainable Upgrades
- Upgrading Code and Customizations
- Upgrade Steps for Application Server Installations
- List of Obsolete Bundles Uninstalled After the Upgrade
- Repository Restructuring
- Repository Restructuring in AEM 6.4
- Common Repository Restructuring in AEM 6.4
- Sites Repository Restructuring in AEM 6.4
- Assets Repository Restructuring in AEM 6.4
- Dynamic Media Repository Restructuring in AEM 6.4
- Forms Repository Restructuring in AEM 6.4
- E-Commerce Repository Restructuring in AEM 6.4
- Repository Restructuring for AEM Communities in 6.4
- eCommerce
- Best Practices
eCommerce Overview
AEM generic eCommerce is available as part of a standard installation and provides you with the full functionality of the eCommerce framework.
Adobe provides two versions of the Commerce Integration Framework:
| CIF on-prem | CIF Cloud | |
|---|---|---|
| Supported AEM versions | AEM on-prem or AMS 6.x | AEM AMS 6.4 and 6.5 |
| Back-end | - AEM, Java - Monolithic integration, pre-build mapping (template) - JCR repository |
- Magento - Java and Javascript - No Commerce data stored in JCR repository |
| Front-end | AEM server-side rendered pages | Mixed page application (hybrid rendering) |
| Product catalog | - Product importer, editor, caching in AEM - Regular catalogs with AEM or proxy pages |
- No product import - Generic templates - On-demand data via connector |
| Scalability | - Can support up to a few million products (depends on the use-case) - Caching on Dispatcher |
- No volume limitation - Caching on Dispatcher or CDN |
| Standardized data model | No | Yes, Magento GraphQL schema |
| Availability | Yes: - SAP Commerce Cloud (Extension updated to support AEM 6.4 and Hybris 5 (default) and maintains compatibility with Hybris 4 - Salesforce Commerce Cloud (Connector open-sourced to support AEM 6.4) |
Yes via open source via GitHub. Magento Commerce (Supports Magento 2.3.2 (default) and compatible with Magento 2.3.1). |
| When to use | Limited use-cases: For scenarios where small, static catalogs may need to be imported | Preferred solution in most use-cases |
Deploying Other Implementations
NOTE
For information about concepts and administering eCommerce implementations, see Administering eCommerce.
For information about extending eCommerce capabilities, see Developing eCommerce.