Adobe Experience Manager as a Cloud Service brings many new features and possibilities to manage your AEM projects. This document highlights the important differences for Commerce capabilities between Commerce Integration Framework (CIF) for On-premise, Adobe Managed Service and Experience Manager as a Cloud Service. For other changes, see the generic changes to Experience Manager as a Cloud Service.
The main differences as compared to Experience Manager 6.5 are in the following areas:
The Classic Commerce Integration Framework which included a Product Importer to import and store product catalogs in Experience Manager is no longer available in Experience Manager as a Cloud Service. The use of Classic CIF is not supported in Experience Manager as a Cloud Service and projects using Classic CIF will have to replace the Classic CIF implementation with the supported version as described in CIF on Experience Manager as a Cloud Service
Shown below are the different deployment models for Commerce Integration Framework for the different AEM offerings:
|AEM On-premise||AEM Managed Services||AEM Cloud Service|
|How to deploy CIF Authoring tools for Magento backend||Refer to CIF Connector supported on AEM 6.5||Refer to CIF Connector supported on AEM 6.5||AEM as a Cloud Service needs to be provisioned with CIF add-on. Contact your sales representative for more details|
|How to deploy CIF Venia Project||AEM package install||Deployment done via Cloud Manager||Project moved into Cloud Manager Git Repository and deployment done via Cloud Manager|
For additional documentation on how to use CIF with AEM Managed Service or AEM On-premise, refer to Commerce Integration Framework
CIF Classic/Quickstart version of Commerce Integration Framework may be used on AEM On-premise offering for very limited use-cases. However, this is not the recommended solution.
Customers moving from an AEM on-premise or Managed Services installation to AEM as a Cloud Service need to do a few minor adjustments on the AEM project.
The first adjustment, as described above, is needed for the CIF Connector. The CIF Connector is replaced by the CIF add-on which is deployed by Adobe. Therefore do not install the CIF Connector on AEM as a Cloud Service. Also, the use with the local AEM Cloud SDK is not supported, Adobe provides the CIF add-on also for local development.
Second, understand the AEM Project Structure and the characteristics of AEM as a Cloud Service. Adapt your project setup to the AEM as a Cloud Service layout.
The main differences here are:
Check out the AEM Venia Reference Store project on GitHub. This project provides Maven profiles for AEM as a Cloud Service and on-premise deployments which take into account the different framework conditions.