|Product||Adobe Experience Manager 6.5|
|Type||Service Pack release|
|Date||Thursday, February 23, 2023|
|Download URL||Software Distribution|
Experience Manager 220.127.116.11 includes new features, key customer-requested enhancements, bug fixes, and performance, stability, and security improvements, that are released since the initial availability of 6.5 in April 2019. Install this service pack on Experience Manager 6.5.
A key improvement in Dynamic Media is the following:
New protocol DASH (Dynamic Adaptive Streaming over HTTP) support launched for adaptive bitrate streaming in Dynamic Media video delivery (with CMAF [Common Media Application Format] enabled).
See Enable DASH on your account.
dam:sizeproperty is not updated after XMP writeback, which results in incorrect information being returned from the
movebutton is disabled randomly while moving an asset from one point to another. (ASSETS-14889)
Escapekey is used on a keyboard. (CQ-4344077)
getManifestURIreturns null due to a JCR property being read as
Failed to fetch dataappears. (ASSETS-15617)
Headless Adaptive Forms enable your developers to create, publish, and manage interactive forms that can be accessed and interacted with through APIs, rather than through a traditional graphical user interface.
Adaptive Forms Core Components are a set of 24 open-source, BEM-compliant components that are built on the foundation of the Adobe Experience Manager WCM Core Components. These components are open-source and provide developers the ability to easily customize and extend these components to match the specific needs of their organization. Anyone with existing skills to customize WCM Core components can easily customize and style these components.
The Reader Extension service on OSGi now provides separate options to enable import and export usage rights on a PDF to import or export data in Adobe Acrobat Reader. (NPR-39909)
admin, while performing the
Prepare Adobe Experience Manager Server For DSC deploymentcheck on the AEM Forms JEE service pack it fails. (NPR-40062), (NPR-39387)
PDFAConformance isCompliant="false" compliance="PDF/A-1b" resultLevel="Summary" ignoreUnusedResources="true" allowCertificationSignatures="true"> <Violation count="6" key="PDFA_CS_001_NOT_DEVICE_INDEPENDENT" description="ColorSpace is not device independent. (NPR-39956)
Caused by: java.lang.NoSuchMethodError: com.adobe.xfa.form.FormModel.isXFABarcode(Lcom/adobe/xfa/Node;)Ljava/lang/Boolean.(NPR-39807)
cq-wcm-coreartifactory release does not have the POM. (SITES-10983)
MicrosoftTranslationServiceImpl, the query string parameter
Categoryis incorrect. (NPR-39828)
/libs/cq/gui/components/coral/common/form/tagfield) conflicts with timeline. (CQ-4350751)
/confleaves a lingering runtime model instance without an editable model. (CQ-4349365)
Adobe does not recommend that you remove or uninstall the Experience Manager 18.104.22.168 package. As such, before you install the pack, you should create a backup of the
crx-repository in case you need to roll it back.
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, then select Upload Package to upload the package. To know more, see Package Manager.
Select the package, then select 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 different methods that you can use to automatically install Experience Manager 22.214.171.124.
../crx-quickstart/installfolder when the server is available online. The package is automatically installed.
cmd=install&recursive=trueso that the nested packages are installed.
Experience Manager 126.96.36.199 does not support Bootstrap installation.
Validate the installation
To know the platforms that are certified to work with this release, see the technical requirements.
The product information page (
/system/console/productinfo) displays the updated version string
Adobe Experience Manager (188.8.131.52) 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.14 or later (Use Web Console:
For instructions to install the service pack on AEM Forms, see AEM Forms Service Pack installation instructions.
The UberJar for Experience Manager 184.108.40.206 is available in the Maven Central repository.
In Experience Manager 220.127.116.11, the UberJar version (18.104.22.168) remains the same as the previous release.
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.15</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 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.|
|Connectors||The Adobe JCR Connector for Microsoft® SharePoint 2010 and Microsoft® SharePoint 2013 is deprecated for Experience Manager 6.5.||N/A|
AEM Content Fragment with GraphQL Index Package 1.0.5
This package is needed for customers using GraphQL; this enables them to add the required index definition based on the features they actually use.
Please update your GraphQL queries that may have used a custom API name for your content model to using the default name of the content model instead.
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 126.96.36.199.
If you upgrade your Experience Manager instance from 6.5.0 - 6.5.4 to the latest service pack on Java™ 11, you see
RRD4JReporter exceptions in the
error.log file. To stop the exceptions, restart your instance of Experience Manager.
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 register 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 must add the following properties to the index definition node
/oak:index/damAssetLucene (no reindexing is required):
"tags": [ "visualSimilaritySearch" ] "refresh": true
In AEM Forms, POP3 protocol does not work with email endpoints for Microsoft® Office 365.
On JBoss® 7.1.4 platform, when user install AEM 188.8.131.52 service pack,
adobe-livecycle-jboss.ear deployment fails.
The following text documents list the OSGi bundles and Content Packages included in Experience Manager 184.108.40.206:
These websites are only available to customers. If you are a customer and need access, contact your Adobe account manager.