|Products||Adobe Experience Manager 6.5|
|Type||Service Pack Release|
|Date||March 11, 2021|
|Download URL||Software Distribution|
Adobe Experience Manager 18.104.22.168 includes new features, key customer-requested enhancements, and performance, stability, and security improvements, that are released since the availability of 6.5 release in April 2019. The service pack is installed on Adobe Experience Manager 6.5.
The key features and enhancements introduced in Adobe Experience Manager 22.214.171.124 are:
When using Connected Assets functionality, you can now view a list of all the Sites pages that use the asset. These references to an asset are available in an asset’s Properties page. This allows administrators, marketers, and librarians a complete view of assets usage, allowing for better tracking, management, and brand consistency.
When deleting an asset that is referenced in a web page, Experience Manager displays a warning. You can force delete a referenced asset or check and modify the references that are displayed in the Properties page of the asset. Clicking the references opens the local and remote Sites pages.
Sorting the Live Copy pages available for rollout using the Name, Last modified date, and Last rollout date properties.
The built-in repository (Apache Jackrabbit Oak) is updated to 1.22.6.
For a complete list of features and enhancements introduced in Experience Manager 126.96.36.199, see what is new in Adobe Experience Manager 6.5 Service Pack 8.
The following is the list of fixes provided in Experience Manager 188.8.131.52 release.
org.apache.felix.scr.impl.ComponentRegistrytimer. As a result, Experience Manager stops responding for an indefinite time (GRANITE-33125,FELIX-6252).
Adobe Experience Manager 184.108.40.206 Assets fixes the following issues and provides the following enhancements.
OutOfMemoryErrorerror as smart tagging functionality creates large
scene7FileStatusmetadata value does not update as expected (CQ-4308269).
Unable to create a custom tag for all products in Commerce (CQ-4310682).
Product asset reference update causes replication threads to be in the wait state until the ProductAssetListener thread completes its commits to the JCR (NPR-35269).
When you use a Coral Tab View component with no tabs and then trigger a Foundation validator, the following error occurs (NPR-35636):
Uncaught TypeError: Cannot set property 'invalid' of undefined at enable (foundation.js:10703) at foundation.js:10710
SCD forward replication fails for Delete events for nodes that include a comma in the name (NPR-35191).
After you upgrade to AEM 6.5.7, the builds start failing. The reason is, an old version or no jackson-core is embedded in the uber-jar (GRANITE-33006).
When you switch from Card view to List view for documents in a folder in the Assets console, sorting does not work appropriately (NPR-35842).
When you hyperlink text in a text component, the search feature does not display appropriate results (NPR-35849).
When a value is not provided to a hidden field that is marked required, it blocks you from saving a component (NPR-35219).
On adding a page structure to a community group, the Group title in the breadcrumb is changed to the title of the first Page (NPR-35803).
Unlike moderators, a standard community member is not able to access and edit any draft post (NPR-35339).
Broken access control and denial of service with
DSRPReindexServlet which brings the communities site down until the indexing is complete (NPR-35591).
Removing All Users from the Administrators field does not actually remove them from the back-end (NPR-35592, NPR-35611).
The Compose Message component does not return any result when the entered text is a partial-match (NPR-35666).
You may notice some performance impact and slowness, when attempting to add tags to a new blog by selecting Add Tags. To improve performance, install cqTagLucene-0.0.1.zip hotfix.
Experience Manager Forms releases the add-on packages one week after the scheduled Experience Manager Service Pack release date.
When you insert a table with a repeatable row to a repeatable panel that has multiple instances in an adaptive form, the table always gets added to the first instance of the panel (NPR-35635).
When the tab focus reaches the CAPTCHA component again after successfully verifying it once in an adaptive form, Experience Manager Forms displays the
Provide Captcha phrase to proceed error message (NPR-35539).
When you submit a translated form, the submission messages display in English and do not translate to the appropriate language (NPR-35808).
When you include a hide condition in the attached XDP or document fragments, the Interactive Communication fails to load (NPR-35745).
When you are editing a letter, the modules with conditions take a longer time to load (NPR-35325).
When you select an asset from the left navigation pane that is not included in a letter and then select the next asset, the blue highlight is not removed from the previously selected asset (NPR-35851).
When you edit text fields in a letter, Experience Manager Forms displays the
Text Edit Failed error message (CQ-4313770).
When you try to open an adaptive form on an Experience Manager Forms mobile application for iOS, the application stops to respond (CQ-4314825).
The To-do tab in the HTML workspace displays HTML characters (NPR-35298).
When you generate an XML document using the Output Service, the
OutputServiceException error occurs for some of the XML files (CQ-4311341, CQ-4313893).
When you apply superscript property to the first character of the bullet, the bullet size gets smaller (CQ-4306476).
The PDF forms generated using the Output Service do not include borders (CQ-4312564).
For information on security updates, see Experience Manager security bulletins page.
Setup requirements and more information
Adobe does not recommend removing or uninstalling the Adobe Experience Manager 220.127.116.11 package.
To install the service pack on an Adobe Experience Manager 6.5 instance, follow these steps:
Restart the instance before installation if the instance is in update mode (and this is the case when the instance was updated from an earlier version). Adobe also recommends a restart if the current uptime for an instance is high.
Before installing, take a snapshot or a fresh backup of your Experience Manager instance.
Download the service pack from Software Distribution.
Open Package Manager and click Upload Package to upload the package. To know more, see Package Manager.
Select the package and click Install.
To update the S3 connector, stop the instance after installation of the Service Pack, replace the existing connector with a new binary file provided in the install folder, and restart the instance. See Amazon S3 Data Store.
Dialog on Package Manager UI sometimes exits during the installation of the service pack. Adobe recommends that you wait for error logs to stabilize before accessing the deployment. Wait for the specific logs related to the uninstall of the updater bundle before being assured that the installations is successful. Typically, this happens on Safari but can intermittently happen on any browser.
There are two ways to automatically install Adobe Experience Manager 18.104.22.168 on a working instance:
A. Place the package into
../crx-quickstart/install folder when the server is available online. The package is automatically installed.
B. Use the HTTP API from Package Manager. Use
cmd=install&recursive=true so that the nested packages are installed.
Adobe Experience Manager 22.214.171.124 does not support Bootstrap installation.
The product information page (
/system/console/productinfo) displays the updated version string
Adobe Experience Manager (126.96.36.199) under Installed Products.
All OSGi bundles are either ACTIVE or FRAGMENT in the OSGi Console (Use Web Console:
The OSGi bundle
org.apache.jackrabbit.oak-core is version 1.22.3 or later (Use Web Console:
To know the platforms certified to work with this release, see the technical requirements.
Skip if you are not using Experience Manager Forms. Fixes in Experience Manager Forms are delivered through a separate add-on package a week after the scheduled Experience Manager Service Pack release.
AEM 188.8.131.52 includes a new version of AEM Forms Compatibility Package. If you are using an older version of AEM Forms Compatibility Package and updating to AEM 184.108.40.206, install the latest version of the package post installation of Forms Add-On Package.
Skip if you are not using AEM Forms on JEE. Fixes in Adobe Experience Manager Forms on JEE are delivered through a separate installer.
For information about installing the cumulative installer for Experience Manager Forms on JEE and post-deployment configuration, see the release notes.
After installing the cumulative installer for Experience Manager Forms on JEE, install the latest Forms add-on package, delete the Forms add-on package from the
crx-repository\install folder, and restart the server.
The UberJar for Experience Manager 220.127.116.11 is available in the Maven Central repository.
To use UberJar in a Maven project, see how to use UberJar and include the following dependency in your project POM:
<dependency> <groupId>com.adobe.aem</groupId> <artifactId>uber-jar</artifactId> <version>6.5.8</version> <scope>provided</scope> </dependency>
UberJar and the other related artifacts are available on Maven Central Repository instead of Adobe Public Maven repository (
repo.adobe.com). The main UberJar file is renamed to
uber-jar-<version>.jar. So, there is no
apis as the value, for the
Below is a list of features and capabilities that are marked as deprecated with Experience Manager 18.104.22.168. Features are marked deprecated initially and later removed in a future release. An alternate option is usually provided.
Review if you use a feature or a capability in a deployment. Also, plan to change the implementation to use an alternate option.
|Integrations||The AEM Cloud Services Opt-In screen is deprecated. With the Experience Manager and Adobe Target integration updated in Experience Manager 6.5 to support the Adobe Target Standard API, which uses authentication via Adobe IMS and I/O, and the growing role of Adobe Launch for instrumenting Experience Manager pages for analytics and personalization, the Opt-In wizard has become functionally irrelevant.||Configure system connections, Adobe IMS authentication, and Adobe I/O integrations via the respective Experience Manager cloud services.|
|Connectors||The Adobe JCR Connector for Microsoft SharePoint 2010 and Microsoft SharePoint 2013 is deprecated for Experience Manager 6.5.||N/A|
If you are upgrading your Experience Manager instance from 6.5 to 22.214.171.124 version, you can view
RRD4JReporter exceptions in the
error.log file. Restart the instance to resolve the issue.
If you install Experience Manager 6.5 Service Pack 5 or a previous service pack on Experience Manager 6.5, the runtime copy of your assets custom workflow model (created in
/var/workflow/models/dam) is deleted.
To retrieve your runtime copy, Adobe recommends to synchronize the design-time copy of the custom workflow model with its runtime copy using the HTTP API:
Contact Adobe Customer Care if you encounter issues when editing and creating cascading rules in Folder Metadata Schema Forms Editor and Metadata Schema Forms Editor using Define Rule dialog. The rules that are already created and saved are working as expected.
If a folder in the hierarchy is renamed in Experience Manager Assets and the nested folder containing an asset is published to Brand Portal, the title of the folder is not updated in Brand Portal until the root folder is published again.
When a user selects to configure a field for the first time in an adaptive form, the option to save a configuration does not display in Properties Browser. Selecting to configure some other field of the adaptive form in the same editor resolves the issue.
If Connected assets configuration wizard returns a 404 error message after installation, manually reinstall the
cq-remotedam-client-ui-components packages using the Package Manager.
The following errors and warning messages may display during installation of Experience Manager 6.5.x.x:
com.adobe.granite.maintenance.impl.TaskScheduler: No maintenance windows found at granite/operations/maintenance.
com.adobe.granite.maintenance.impl.TaskScheduler- No maintenance windows found at granite/operations/maintenance.
com.adobe.cq.social.cq-social-jcr-provider bundle com.adobe.cq.social.cq-social-jcr-provider:1.3.5 (395)[com.adobe.cq.social.provider.jcr.impl.SpiSocialJcrResourceProviderImpl(2302)]: Timeout waiting for reg change to complete unregistered.
The following text documents list the OSGi bundles and Content Packages included in Experience Manager 126.96.36.199:
These websites are only available to customers. If you are a customer and need access, contact your Adobe account manager.