Deprecated and Removed Features

You are reading the AEM 6.2 version of Deprecated and Removed Features.
This documentation is also available for the following versions:  AEM 6.1 

Adobe constantly evaluates capabilities in the product and over time plans to replace capabilities with more powerful versions, or decides to re-implemented selected parts to be better prepared for future expectations or extensions.

Backwards compatibility is key when replacing capabilities, to make sure our customers investment in our technology is safe.

The general rule is: Capabilities are 1st announced to be deprecated, and the earliest removed in the following release. That gives customers at least one release cycle to adapt their implementation to the new version of the capability, before it might get removed.

Changes Relevant for Customers that Update

Following list are changes that have direct impact after update to AEM 6.2. They are changed behaviors that might requires changes in the project implementation.

Area Feature
Change
Platform CRX2 Repository Customers with 5.x and 6.0 using CRX2 repository will have to upgrade to the Apache Jackrabbit Oak based implementation of JCR. The update process to 6.2 detects CRX2 configurations and updates them to the Oak based repository.
Platform Sling The default configuration in org.apache.sling.engine.impl.SlingMainServlet for Number of Calls per Request is 1000. Prior releases had 1500 set. (DOC-7626)
UI Saved Searches The format to persist saved searches was modified with AEM 6.2. Depending on search form configuration, already existing saved searches created with 6.1 might not be able to provide results. (CQ-80741)
UI Custom Search Facets & Configuration

During in-place update - the search facet configurations stored in (apps/cq/gui/content/facets) is moved to a new location (/conf/global/settings/cq/search/facets).

Customers that created custom search facets components might have to refactor their code. (DOC-7431, CQ-79523)

Sites /content/campaign Structure
With the introduction of the 'Area' feature. The default content structure has been extended. The in-place update process has a step to adapt the structure during the update. 
Sites Adobe Target Integration Starting 6.2, the locations on the pages that have targeted content have a new ID format (previous it was a path - now an UUID). Existing activities and locations can runs as is.
Assets Dynamic Media DM is now enabled via runmode and no longer uses the Dynamic Media flag (/etc/dam/dynamicmediaconfig). Please see documentation.
Assets Dynamic Media Dynamic Media replication agent requires new replication URL, username and password. Please contact support for updated cloud credentials.
Communities SocialUtils methods The deprecated SocialUtils package has been refactored into several packages and will be removed in 6.3.  See SocialUtils Refactoring for details.

Deprecated Features

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

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

Area Feature Replacement
Personalization
  • Client Context UI in Page Editor (Classic UI)
  • Client Context Configuration (Classic UI)
  • Client Context component
  • Segment Engine (logic loading the segment.js, resolving segments and loading offers)
  • Segment Engine UI (Classic UI)
  • Client Context Stores
  • Client-side Rules
The 'ContextHub' is replacing the 'Client Context'. Starting 6.2, Adobe will stop investments in the 'Client Context' capabilities. The 'ContextHub' has feature parity with AEM 6.2 and is the recommended replacement. Adobe recommends customers to plan to reconfigure their sites to switch to the 'ContextHub' at their convenience. 
Personalization Teaser component The 'Teaser' component is replaced with the 'Target' component and the implicit targeting mode in the authoring UI.
Personalization Adobe Target Global MBox component Is no longer needed - as the updated mbox.js includes the logic
UI

Copy Editor and Manuscripts Admin (Classic UI)

Adobe recommends customers to start using the new Content Fragment Editor, that also supports the Markdown syntax.
UI
Notification (JCR Observation Listener UI) under /libs/wcm/core/content/inbox.html Adobe will no longer invest in this capability
Marketing Cloud Integrations

Audience Manager Integration via Cloud Services

  • Built-in Page Tagging of AAM JS
  • Client-side Rules via synced AAM segments

Adobe recommends to leverage the next generation integration that leverages the User ID service:

  • Page Tagging via DTM (works since 6.0)
  • Client-side Rules: Replaced by server-side integration between Adobe Target and AAM.
APIs ImpressionsEntry and ImpressionsPathBuilder Used by deprecated ImpressionsImporter which has been replaced by ReportImporter
APIs SAINTService and SAINTTransformer Replacement with new API (ClassificationsService/ClassificationsTransformer)
APIs CQ Statistics. This is the servlet tracking page impressions that are shown in the Classic Site Admin.
Recommendation is to use the integrated Adobe Analytics for measuring content efficiency. Please contact your Adobe account manage to find out if you are eligible for Adobe Analytics Essentials.
APIs & Components CQ Account Management

AEM 6.2 ships with new account management components and APIs (Reset PW, Account Request and Update). The older versions are now deprecated. We recommend customers to revisit their usage of the actions and switch to the new versions.

APIs Asynchronous JavaScript API provided by com.adobe.granite.sightly.js.content Use the synchronous JavaScript API provided by org.apache.sling.scripting.javascript
APIs Sling's JCR Resource API Most of Sling's JCR Resource API was already set as deprecated, with 6.2 it gets fully deprecated. Use Sling's Resource API instead.
APIs Sling Background Servlets Use Sling Jobs mechanism instead
Communities SocialUtils methods The deprecated SocialUtils package has been refactored into several packages and will be removed in 6.3.  See SocialUtils Refactoring for details.

Removed Features

This section lists features and capabilities that have been removed from AEM 6.2.

Area Feature Replacement
Platform UI Removed Coral 1.0 resources. They were introduced with 5.6 and used in the Touch-optimized UI They are no longer needed. The AEM UI uses newer Coral UI versions. Customers that customized the Touch-optimized UI with 5.6.x might have to refactor the customization based on the Coral UI version used in 6.2.
Platform UI Removed Shell 1.0 components. They were introduced with 5.6 and used in the Touch-optimized UI.
They are no longer needed. The AEM UI uses newer Shell versions. Customers that customized the Touch-optimized UI with 5.6.x might have to refactor the customization based on the Shell version used in 6.2.
Platform Security Removed Pin Authentication Handler that was deprecated with 5.6
 
Platform Tools Removed Content zipper/loader (/crx/loader/index.jsp and /crx/zipper/index.jsp)  
Platform Tools Removed One-Click-Setup for AWS from Quickstart  
Developer Tools Removed CRXDE Support Servlets. They were used by the discontinued  Eclipse-based CRXDE IDE. Recommendation is to used the new Eclipse plug-ins shipped with 6.0 that also work with 5.6.x.
Components
Removed MVT component. A simple multi-image component that measures clickthroughs.   Recommendation is to use the integrated Adobe Target for measuring content efficiency. Please contact your Adobe account manage to find out if you are eligible for Adobe Target Essentials.
Components Removed Design Importer components first shipped in 5.6.0. In 5.6.1, an improved Design Importer was implemented that replaced the one from 5.6.0
E-Mail Provider Support Removed E-Mail Provider Integration with Silverpop The integration was moved into an optional to install package available on PackageShare
Samples Removed the Geometrixx Mobile Sites  
APIs
Removed Account* classes from the Adobe Target and Analytics integration that were deprecated with 5.6.1  
APIs Removed FormsManagerServiceImpl from the Sites Forms components that was deprecated with 6.1  
APIs
Removed com.day.cq.commons.jcr.AbstractRepositoryService Class that was deprecated with 5.6  
APIs
Removed com.day.cq.jobs.core Package  
APIs Removed cq-activitystreams that was deprecated with 6.0 Starting 6.0, Adobe provides the capabilities with a new Activity Streams API as part of the Platform (Granite). Customer that use this API should refactor their code to leverage the new version.
E-Mail Integration Removed CQ activities generation in Newsletter module  
E-Mail Integration Removed Newsletter API methods for E-mail tracking of opens/bounces (not deliverable) send by AEM SMTP service that were deprecated with 6.1  
Communities CQ Activity Streams Conversion to new platform (Granite) API, available in 6.0, should now be complete.  The old CQ API is no longer available.
Communities Social Networks  (Facebook & Twitter) components Components, deprecated in 6.1 and now removed, are :
  • Facebook Activity Feed
  • Facebook Comments
  • Facebook Facepile
  • Facebook Like Button
  • Facebook Send Button
  • Twitter Follow Button
  • Twitter Search
  • Twitter Share Button
Communities JSP Blog components Blog components (in the Blog component category), which supported author-side blogging, are no longer available. The new publish-side Blog feature should be used instead.
Communities UGC Report components UGC Reports is removed. Use the Communities Reports console, instead.
Communities Unified Moderation Integrating with Adobe Social for the purpose of Unified Moderation is no longer supported. The improved replacement solution is Moderating Community Content for UGC stored in ASRP.

Pre-announcement for Next Release

This section is used to pre-announce changes in future release, that are not deprecated, but will impact customers. These are provided for planning purpose.

Area
Feature
Annoucement
Operating System support
HP-UX
With the 2017 release, Adobe will remove support for HP-UX
Operating System support Oracle Solaris With the 2017 release, Adobe will remove support for Oracle Solaris 10 - V5.10
Operating System support Microsoft Windows With the 2017 release, Adboe will remove support for Windows Server 2012 - V6.2
App Server Support
IBM WebSphere With the 2017 release, Adobe will remove support for IBM WebSphere 8.5
Java Language
Java VM The 2017 release of AEM will be the last version that supports Java 7. After that - Java 8 is the minium Jave VM supported
Dispatcher Web Server
Oracle iPlanet By the end of 2017, Adobe will remove support for Oracle iPlanet Web Server 7

Any questions?

Have a question about this or any other AEM topic? Ask our Community.
Learn more about AEM topics on our help hub.
Was this helpful?

By submitting your feedback, you accept the Adobe Terms of Use.

Thank you for submitting your feedback.