|Products||Adobe Experience Manager 6.5|
|Type||Service Pack Release|
|Date||February 24, 2022|
|Download URL||Software Distribution|
Adobe Experience Manager 126.96.36.199 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 188.8.131.52 are:
After configuring a connection between remote DAM and Sites deployments, the assets on remote DAM are made available on the Sites deployment. You can now perform the update, delete, rename, and move operations on the remote DAM assets or folders. The updates, with some delay, are available automatically on the Sites deployment (NPR-37816).
Push-rollouts of a live copy source to multiple live copies is now possible by default, without requiring a blueprint configuration (CQ-4259951).
The status of in-progress async operations is now shown in the user interface to help prevent users from accidentally triggering multiple async operations on the same path (NPR-37611).
Support for IMS-based authentication is provided for Analytics 2.0 APIs (CQ-4285474, NPR-37803, NPR-37701, NPR-37702, NPR-37703).
API support for JSON offer type experience fragment (NPR-37796).
Offer request is now provided for Delete offer (Experience Fragment API) in IMS (NPR-37668).
The built-in repository (Apache Jackrabbit Oak) still remains at 1.22.9.
The following is the list of fixes provided in Experience Manager 184.108.40.206 release.
The following issues are fixed in Sites:
Page Subtree Activation Checkunder Configuration
Page Manager Factoryneeds to be enabled (NPR-37936).
The following issues are fixed in Assets:
When adding an asset or folder (containing
single quote in the name) in Connected Assets, the reference path fails and results as an exception (NPR-37712).
When adding watermark to an asset, the watermark is always displayed in black color irrespective of the color defined by the user (NPR-37720).
When using Connected Assets, a non-admin user is able to search for an asset even when the non-admin users are restricted to access the DAM repository (NPR-37644).
When updating asset metadata using bulk edit, the changes applied to the dropdown fields are not saved and reset to the default values (NPR-37345).
Deleting a folder in taking too long which impacts the overall performance (NPR-37107).
When applying rules in metadata schema, the user is not able to view the complete value for the dropdown
Field Value and
Field Choices if the value is larger than the text box (CQ-4338074).
After upgrading to version 220.127.116.11, the asset properties page reflects an unnecessary HTML rendering message (CQ-4336994).
Sorting the assets in
List View does not work effectively (CQ-4335298).
When sharing assets using share link, the assets are downloaded in separate folders (CQ-4335000).
When verifying the Experience Manager
Inbox settings, the
Out of office tabs reflect untranslated content (CQ-4334858).
The following fixes are related to cascading metadata in asset properties.
The following issues are fixed in Dynamic Media:
renditionsin the folder name are not synced in
tiffformat, the preset is created but the format changes to
Progressive JPEG Scanvalue in Image Preset Editor, the dropdown value always resets to
mxfvideos on the asset properties page (CQ-4335499).
companyRootare different (CQ-4339896).
When a text component in an adaptive form contains a table, pasting content into the component results in erasing the table in the editor (NPR-38078).
A form displays a toolbar only when you open a saved form (NPR-38060).
The undo operation does not work correctly for the rule editor (NPR-37973).
getAemFormContainer returns a null pointer after installing AEM Forms 18.104.22.168 (NPR-37881).
Accessibility - The screen reader announces the long description of a text box as soon as the tab focus shifts to the field instead of announcing only when you click the field (NPR-37855).
When you enable the Allow Rich Text property for a text box, there are issues with the maximum allowed character length (NPR-37825).
CSS issues when you copy any component in an adaptive form (NPR-37812).
While generating the adaptive forms translation the generated XLIFF file does not contain the same sequence of texts as in the Adaptive Form. In some cases it is needed to see the context of the texts. This is not possible if the sequence in XLIFF is alphabetic. (NPR-37435).
When an adaptive form is translated, the HTML tags are part of the translation. If a user makes a mistake and the tags are not valid, the whole text is not shown in the document of record. (NPR-37499)
When an adaptive form is created and finalized in base language and translation is done by an external team and imported. If there even a small change of text like addition or missing dot (.) is done in the for the base language, the complete translation goes missing for all other languages. (NPR-37189)
Form Data Model
Assembler does not embed fonts, as expected (NPR-38056).
Unable to convert PDF to PDFA using workbench (NPR-37879).
Issues with office documents while using the PDF Generator service after upgrading from AEM 22.214.171.124 Forms to AEM 126.96.36.199 Forms (NPR-37758).
Multithreaded PDF Generator service deadlocks after a random amount of time for AEM 188.8.131.52 Forms (NPR-38053).
In the AEM Workbench version 184.108.40.20610518.1.338459, when you use a email startpoint and edit the username and password, the configurations are not saved (NPR-37967, CQ-4336081).
Saving logs result in high CPU utilization that requires a server restart (NPR-37868).
Gemfire.log does not get created in the
temp\adobejb_server1\Caching folder after installing AEM Forms-6.5.0-0038 (CQ-4340237).
The following error displays after executing the
ConfigurationManager.sh command (CQ-4338323):
[root@localhost bin]# ./ConfigurationManager.sh bash: ./ConfigurationManagerCLI.sh: /bin/sh^M: bad interpreter: No such file or directory
AEM 6.5 Forms on RHEL8 does not support JBOSS EAP 7.3 and MySQL8 (CQ-4331770).
Issues while storing UTF-8 special characters as part of a workflow on AEM 220.127.116.11 Forms publish instance (NPR-37673).
Issue while creating variable of ArrayList type and JSON subtype (NPR-37600).
Issues with XPath/Dot Notation browser with Set Variable step in Workflow in AEM 18.104.22.168 Forms and AEM 22.214.171.124 Forms (CQ-4336582).
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 126.96.36.199 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 (when the instance was updated from an earlier version). Adobe 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 issue occurs in Safari browser but can intermittently occur on any browser.
There are two ways to automatically install Experience Manager 188.8.131.52 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 184.108.40.206 does not support Bootstrap installation.
Validate the installation
The product information page (
/system/console/productinfo) displays the updated version string
Adobe Experience Manager (220.127.116.11) 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.
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 18.104.22.168 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.12</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 22.214.171.124. Features are marked deprecated initially and later removed in a future release. An alternate option is 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 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 via Adobe IMS and Adobe I/O and 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 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 using Content Fragments and GraphQL then it is recommended that you install the following packages on top of 126.96.36.199:
AEM 6.5.12 Sites HotFix-NPR-38144 (this replaces SP12, but can be installed on top of SP12)
As Microsoft Windows Server 2019 does not support MySQL 5.7 and JBoss EAP 7.1, Microsoft Windows Server 2019 does not support turnkey installations for AEM Forms 188.8.131.52.
If you are upgrading your Experience Manager instance from 6.5 to 184.108.40.206 version, you can view
RRD4JReporter exceptions in the
error.log file. To resolve the issue, restart the instance.
If you install Experience Manager 6.5 Service Pack 10 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:
Users can rename a folder in a hierarchy in Assets and publish a nested folder to Brand Portal. However, the title of the folder is not updated in Brand Portal until the root folder is republished.
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.
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.
When trying to move/delete/publish either Content Fragments or Sites/Pages, there is an issue when Content Fragment references are fetched, as the background query fails; i.e. the functionality does not work.
To ensure correct operation, you need to add the following properties to the index definition node
/oak:index/damAssetLucene (no re-indexing is required) :
"tags": [ "visualSimilaritySearch" ] "refresh": true
The following text documents list the OSGi bundles and Content Packages included in Experience Manager 220.127.116.11:
These websites are only available to customers. If you are a customer and need access, contact your Adobe account manager.