Deprecated and removed features deprecated-and-removed-features

Last update: Wed Apr 24 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

Topics:
Release Information

CREATED FOR:

User
Admin
Developer

Adobe constantly evaluates product capabilities, to over time reinvent or replace older features with more modern alternatives to improve overall customer value, always under careful consideration of backward compatibility.

To communicate the impending removal or replacement of Adobe Experience Manager (AEM) capabilities, the following rules apply:

Announcement of deprecation comes first. While deprecated, capabilities are still available but are not further enhanced.
Removal of deprecated capabilities occurs in the following major release at the earliest. Actual target date for removal will be announced later.

This process gives customers at least one release cycle to adapt their implementation to a new version or successor of a deprecated capability, before actual removal.

Deprecated features deprecated-features

This section lists features and capabilities that have been marked as deprecated with AEM 6.5. Generally, features that are planned for removal in a future release are set to deprecated first, with an alternative provided.

Customers are advised to review if they use the feature/capability in their current deployment, and make plans to change their implementation to use the alternative provided.

Area

Feature

Replacement

Version (SP)

Sites

The Adobe AEM Managed Polling Configuration service: com.day.cq.polling.importer.impl.ManagedPollConfigImpl

The Adobe AEM Analytics Report Sling Importer service. See Connecting to Adobe Analytics and Creating Frameworks - Configuring the Import Interval

6.5.19.0

Screens

ActiveMQ in Adobe Experience Manager (AEM). ActiveMQ was used for communication between two AEM Publish instances.

Adobe recommends that customers now use a load-balancer.

6.5.18.0

Experience Fragments properties for Social Media Status.

6.5.11.0

Sites

Content fragment templates, for creating simple content fragments.

Model-based structured content fragments now.

6.5.11.0

Creative Cloud integration

AEM to Creative Cloud Folder Sharing was introduced in AEM 6.2. It provides a way to give creative users access to assets from AEM, so that they can open them in Creative Cloud applications and upload new files or save changes to AEM. A new capability released in Creative Cloud application, Adobe Asset Link, provides a better user experience and more powerful access to assets from AEM directly from inside Photoshop, InDesign, and Illustrator. Adobe does not plan to make further enhancements to the AEM to Creative Cloud Folder Sharing integration. While the feature is included in AEM, customers are advised to use replacement solutions.

Customers are advised to switch to new Creative Cloud integration capabilities, including Adobe Asset Link or AEM desktop app.

Assets

AssetDownloadServlet is disabled by default for the publish instances. For more details, see AEM security checklist.

Configuration described at AEM Security checklist.

Integrations

The screen Experience Manager Cloud Services Opt-In is deprecated since the Experience Manager and Adobe Target integration is updated in Experience Manager 6.5. The integration supports the Adobe Target Standard API. The API uses authentication by way of Adobe IMS and Adobe I/O Runtime. It supports the growing role of Adobe Launch to instrument Experience Manager pages for analytics and personalization, the opt-in wizard is functionally irrelevant.

Configure system connections, Adobe IMS authentication, and Adobe I/O Runtime integrations via the respective Experience Manager cloud services.

6.5.7.0

Connectors

The Adobe JCR Connector for Microsoft® SharePoint 2010 and Microsoft® SharePoint 2013 is deprecated for Experience Manager 6.5.

N/A

Dynamic Tag Manager (DTM)

The integration with DTM is deprecated.

Switch to use Adobe Experience Platform Launch as a tag manager.

Adobe Target

With adding the ability for AEM to connect to Adobe Target service using the Adobe I/O based Adobe Target Standard API (Rest API) in AEM 6.5, the Target Classic API (XML) way is deprecated.

Reconfigure the integration to use the new API.

Adobe Target

Using the mbox.js based integration with Adobe Target in AEM is deprecated.

Switch to use at.js 1.x.

Commerce

CIF REST was provided in 2018 as a set of microservices to enable integrations between AEM and commerce engines. After Adobe acquired Adobe Commerce (formerly Magento) in mid 2018, Adobe decided to change its approach for two reasons. Commerce has its own set of Commerce APIs (REST and GraphQL) and it is not good practice to maintain two sets of APIs. Market trends indicated that customers were moving towards GraphQL, because it is a more efficient way of querying data. In 2019, Adobe has released the new Commerce Integration Framework using Commerce’s GraphQL APIs as the source of truth. Adobe does not plan to make any further investment in CIF REST. Customers are advised to use the replacement solution.

For AEM-Commerce integrations, switch to AEM CIF Archetype and AEM CIF Core Components. See AEM and Adobe Commerce integration using Commerce Integration Framework. Support for third-party (other than Commerce) integrations with the new approach is on Adobe’s roadmap.

Components (AEM Sites)

Adobe does not plan to make further enhancements to most of the Foundation Components stored in /libs/foundation/components. Look for the cq:deprecated and cq:deprecatedReason property in the component folder. AEM 6.5 has the Foundation Components included, and customers upgrading from earlier releases can keep using them as is. Further, the Foundation Components is supported even though deprecated.

Adobe recommends using the Core Components for future projects. Existing sites can remain as is or use the AEM Modernize Tools Suite to refactor the site to use Core Components.

Components (AEM Sites)

Design Importer Components /libs/wcm/designimporter/components have been marked as deprecated starting 6.5. Adobe does not plan to make further enhancements to that implementation of the design importer.

Adobe plans to provide an alternative implementation of the use case in future releases.

Foundation

Granite Offloading Framework. Adobe does not plan to make further enhancements to the offloading framework that was introduced in CQ 5.6.1 to externalize asset processing.

Adobe is working on a next-generation cloud-native offloading framework.

Developers

Hobbes.js. Adobe does not plan to make further enhancements to the hobbes.js user interface testing framework.

Adobe recommends that customers use Selenium automation.

Developers

jQuery UI client library. Adobe does not plan to further maintain and update the jQuery UI client library that is shipped as part of the distribution (Quickstart).

Adobe recommends customers that still require jQuery UI for their code to add it into their project code base.

Developers

jQuery Animation client library (granite.jquery.animation). Adobe does not plan to further maintain and update the jQuery Animation client library that is shipped as part of the distribution (Quickstart).

Adobe recommends customers that still require jQuery Animations for their code to add it into their project code base.

Developers

Handlebars client library. Adobe does not plan to further maintain and update the Handlebar client library that is shipped as part of the distribution (Quickstart).

Adobe recommends customers that still require Handlebars for their code to add it into their project code base.

Developers

Lawnchair client library. Adobe does not plan to further maintain and update the Lawnchair client library that is shipped as part of the distribution (Quickstart).

Adobe recommends customers that still require Lawnchair for their code to add it into their project code base.

Developers

Granite.Sling.js client library. Adobe does not plan to further enhance the Granite.Sling.js client library that is shipped as part of the distribution (Quickstart).

Adobe recommends customers that are relying on the capability of the library to refactor their code to no longer use it.

Developers

Using YUI to compress/minify JavaScript client libraries. Adobe does not plan to further update the YUI library. Up until AEM 6.4, YUI was default to minify JavaScript with the option to switch to Google Closure Compiler (GCC). Starting AEM 6.5, GCC is default.

Adobe recommends customers that upgrade to AEM 6.5 to switch to GCC for their implementation

Developers

Classic UI Dialog Editor in CRXDE Lite. Adobe does not plan to further enhance the Classic UI Dialog Editor that is shipped as part of the distribution (Quickstart)

No replacement is available.

Forms

AEM Forms integration with AEM Mobile is deprecated.

No Replacement is available.

Developers

Classic UI Dialog Editor in CRXDE Lite. Adobe does not plan to further enhance the Classic UI Dialog Editor that is shipped as part of the distribution (Quickstart)

No replacement is available.

Developers

Lodash/underscore client library. Adobe does not plan to further maintain and update the Lodash/underscore client library that is shipped as part of the distribution (Quickstart).

Adobe recommends customers that still require Lodash/underscore for their code to add it into their project code base.

Removed features removed-features

This section lists features and capabilities that have been removed from AEM 6.5. Prior releases had these capabilities marked as deprecated.

Area

Feature

Replacement

Version (SP)

Integration with Experience Cloud

You could synchronize your assets with Experience Cloud using a configuring via Adobe I/O. Adobe Experience Cloud was formerly called Adobe Experience Cloud.

If you have any queries, contact Adobe Customer Support.

Analytics Activity Map

The version of the Activity Map that is included within AEM.

Due to security changes within the Adobe Analytics API, it is no longer possible to use the version of Activity Map that is included within AEM. Use the ActivityMap plug-in provided by Adobe Analytics.

Integrations

ExactTarget integration has been removed from the default distribution (Quickstart) and it is no longer available.

No replacement.

Integrations

Salesforce Force API integration has been removed from the default distribution (Quickstart) and is now an extra package to install from Software Distribution.

The feature is still available.

Forms

Support for Adobe Central Migration Bridge service has been removed as Adobe Central product is no longer supported.

No replacement.

Forms

com.adobe.fd.df.fdinternal.model.ConfigurationInstance

No replacement.

Forms

com.adobe.fd.ccm.channels.print.fdinternal.api.service.PrintDataTransformer

No replacement

Forms

Single-hop upgrade from LiveCycle ES4 SP1 to AEM 6.5 Forms on JEE is not available

See available upgrade paths in AEM Forms upgrade documentation.

Forms

Removed UPD based clustering support from AEM Forms on JEE

You can use only TCP-based clustering in AEM Forms on JEE. If you upgrade a UDP multicast server from a previous version to AEM 5.5 Forms on JEE perform manual configurations to switch to TCP-based gemfire clustering. For detailed instructions, see Upgrade to AEM 6.5 forms on JEE

Developers

Firebug Lite has been removed from the default distribution (Quickstart)

Use the browser built-in developer consoles

Developers

Remove customJavaScriptPath support in HTML Client Library Manager.

No replacement

Assets

The assets offloading feature is removed in Adobe Experience Manager 6.5.

No replacement is available.

Cache

system/console/slingjsp is removed and is no longer available in AEM 6.5.

Classes and Slightly cache is stored under the Apache Sling Commons FileSystem ClassLoader bundle. You can check the bundle number in the AEM Web Console and remove the cache folder directly from the file system (crx-quickstart/launchpad/felix/bundle<ID>).

Screens

Removed activemq bundle support and its related configurations.

recommendation-more-help

19ffd973-7af2-44d0-84b5-d547b0dffee2