Migrating from deprecated Classic Commerce APIs in AEM 6.5 LTS
This article provides guidance for migrating to Adobe Experience Manager (AEM) 6.5 LTS when projects depend on the deprecated Classic Commerce and CommerceSession APIs, which are no longer available in this version. It covers migration options, support considerations, and recommended approaches.
Description description
Organizations upgrading to AEM 6.5 LTS can encounter challenges if their ecommerce functionality relies on the deprecated Classic Commerce and CommerceSession APIs, as these APIs are removed in the LTS version. This impacts Production checkouts and related integrations. Key considerations include the feasibility of replicating required API interfaces, the implications for support when using custom compatibility layers, and the need to redesign catalog and product detail page (PDP) rollout strategies that previously relied on CIF Classic features.
Environment
Adobe Experience Manager (AEM) 6.5 LTS (on-premises)
Symptoms
- Loss of core ecommerce functionality due to removal of Classic Commerce and CommerceSession APIs
- Incompatibility of previously used restoration packages
- Need to redesign catalog/PDP rollout mechanisms
Cause
The Classic Commerce and CommerceSession APIs have been removed in AEM 6.5 LTS. This requires migration to supported APIs or implementation of custom solutions, which affects support boundaries.
Resolution resolution
Follow the steps below to resolve the issue:
-
Assess your current usage of the Classic Commerce and CommerceSession APIs to identify all dependencies.
-
Plan migration to supported APIs and approaches:
-
Consider adopting Content Fragment (CF)-backed Product Information Management (PIM) solutions compatible with the Commerce Integration Framework (CIF).
-
Redesign catalog and product detail page (PDP) rollout strategies to avoid reliance on MSM/LiveCopy features specific to CIF Classic.
-
-
If you choose to implement a custom compatibility layer to replicate the deprecated APIs:
-
Ensure the implementation is fully maintained and supported by your organization.
-
Consult your legal team before reproducing any Adobe API interfaces or behaviors in your code.
-
Be aware that support can exclude issues caused by or dependent on this compatibility layer from standard support coverage.
-
-
Don’t attempt to use Classic Commerce restoration packages or packages previously used on earlier AEM versions, as these aren’t supported on AEM 6.5 LTS.
-
Review your migration plan for any additional deprecated APIs and update your codebase to use supported alternatives where possible.
-
After migration, thoroughly test all ecommerce and related functionality to ensure compatibility and stability on AEM 6.5 LTS.