Adobe Experience Manager 6.5 Latest Service Pack Release Notes aem-service-pack-release-notes

Release information release-information

Adobe Experience Manager 6.5
Service Pack release
Thursday, June 06, 2024
Download URL
Software Distribution

What is included in Experience Manager what-is-included-in-aem-6521

Experience Manager includes new features, key customer-requested enhancements, and bug fixes. It also includes performance, stability, and security improvements released since the initial availability of 6.5 in April 2019. Install this Service Pack on Experience Manager 6.5.

Key features and enhancements


Some of the key features and enhancements in this release include the following:

  • Support for Oauth Credentials: A new and easier to use credential for server-to-server authentication, replacing the existing Service Account (JWT) credential. (NPR-41994)

  • Rule Editor enhancements in AEM Forms:

    • Support for implementing nested conditions with When-then-else functionality.
    • Validate or reset panels and forms, including fields.
    • Support for modern JavaScript features such as let and arrow functions (ES10 support) within the Custom Functions.
  • AutoTag API for PDF Accessibility: AEM Forms on OSGi now support the new AutoTag API to enhance PDF for accessibility standards by adding tags: paragraphs, and lists. It makes PDFs more accessible for users with assistive technology.

  • 16-bit PNG support: PDF Generator’s ImageToPdf service now supports conversion of PNGs with 16-bit color depth.

  • Apply artifacts to individual text blocks in XDPs: Forms Designer now lets users configure settings on individual text blocks in XDP files. This ability lets you control the elements that are treated as artifacts in the resulting PDFs. These elements, such as headers and footers, are made accessible for assistive technologies. The key features include marking text blocks as artifacts, and embedding these settings in the XDP metadata. The Forms Output service applies these settings during PDF generation, ensuring proper PDF / UA tagging.

  • AEM Forms Designer is certified with GB18030:2022 standard: With the GB18030:2022 certification, now Forms Designer supports the Chinese Unicode character set that lets you input Chinese characters into all editable fields and dialog boxes.

  • Support for WebToPDF route in JEE Server: The PDF Generator service now supports the WebToPDF route for converting HTML files to PDF documents on JEE, in addition to the Webkit and WebCapture (Windows only) routes. While the WebToPDF route is already available on OSGi, it has now been extended to include in JEE as well. On both JEE and OSGi platforms, the PDF Generator service supports the following routes across different operating systems:

    • Windows: Webkit, WebCapture, WebToPDF
    • Linux: Webkit, WebToPDF



The following is the list of enhancements included in this release:

  • The IPTC tab now supports Alt Text and Extended Description text fields. (ASSETS-34918)

Accessibility fixes

The following is the list of accessibility fixes included in this release:

  • If the processing status of an asset is Failed or Metadata Failed, the captions and audio tracks UI does not work appropriately. (ASSETS-37281)
  • When you save an asset metadata and try to edit it, the language name does not display. (ASSETS-37281)

Fixed issues in Service Pack 21 fixed-issues

Sites sites-6521

Accessibility sites-accessibility-6521

  • The Saved Searches label is not persistent. The placeholder is being used as the only visual label for a text field. (SITES-3050)

Admin User Interface sites-adminui-6521

  • When you click Sites > Core Core Components > Properties > Permissions tab > Effective Permission, the Effective Permissions dialog box does not open in. (SITES-17378)

Content Fragments sites-contentfragments-6521

  • Fixed the double inclusion of the form elements. (SITES-21109)
  • When creating a Content Fragment, the Close button sometimes becomes unresponsive, causing the entire page to freeze and necessitating a page refresh to close the Content Fragment. As for the version creation issue, the system is creating a new version of a Content Fragment. This issue occurs even when the user has not made any changes, simply by interacting with the RTE or a text field. (SITES-21187)

Content Fragments - GraphQL API sites-graphql-api-6521

  • While upgrading Adobe Experience Manager from to, the path /libs/cq/graphql/sites/graphiql was getting deleted. (SITES-20098)

Experience Fragments sites-experiencefragments-6521

  • Rollout of Experience Fragments from masters/language to country/language does not update cross-references. (SITES-21172)
  • Templates not only specified in the cq:allowedTemplates, but templates that have allowedPaths configured at the template level, appear as options when creating a new Experience Fragment. (SITES-20855)

MSM - Live Copies sites-msm-live-copies-6521

  • Overlaying the Page component to add tabs in page properties. One of them is page configuration and has a property to add an Experience Fragment URL. The link configured in the page properties for the Experience Fragment does not change for any language copies created for that page. The configured link should change with the language copy URL. (SITES-19580)

Page Editor sites-pageeditor-6521

  • The edit mode applies a gray background inconsistently, which fails to comply with the WCAG (Web Content Accessibility Guidelines) color contrast standards. (SITES-20060)

Assets assets-6521

  • If an asset is published to Brand Portal, the publishing status remains inconsistent. (ASSETS-36807)
  • Assets are not deleted when you delete them from an instance using an API call. (ASSETS-35131)
  • When you try to import metadata, a question mark (?) replaces the insertion of characters in any language other than English. (ASSETS-35091)
  • When dc:title property is used with data type string, the assets content tree is not working appropriately after the installation of Service Pack 6.5.19. (ASSETS-34684)
  • An error is shown if there is any special character in the name of an asset. (ASSETS-33248)

Dynamic Media assets-dm-6521

  • In AEM 6.5.18, it does not show all the hotspots added to an asset when you edit the hotspots. However, all the hotspots work in a published asset, but you cannot edit them later if you needed to. (ASSETS-33609)

  • The latest EPS files that get uploaded are not generating thumbnails after reprocessing. (ASSETS-32617)

  • In Tools > Assets > Dynamic Media Publish Setup > Request Attributes tab, the inputs Width(px) and Height(px) look different in Spanish, Italian, and Portuguese. They are not aligned with each other for these locations. (ASSETS-31896)

  • Effective May 01, 2024, Adobe Dynamic Media ended support for the following:

    • SSL (Secure Socket Layer) 2.0

    • SSL 3.0

    • TLS (Transport Layer Security) 1.0 and 1.1

    • The following weak ciphers in TLS 1.2:

      • TLS_RSA_WITH_AES_256_GCM_SHA384
      • TLS_RSA_WITH_AES_256_CBC_SHA256
      • TLS_RSA_WITH_AES_128_GCM_SHA256
      • TLS_RSA_WITH_AES_128_CBC_SHA256

Forms forms-6521

Adaptive Forms forms-6520

  • When an Adaptive Form is submitted from an Adobe Experience Manager Publish instance to an Adobe Experience Manager Workflow, the workflow fails to save the attachments. (FORMS-14209)

  • When a user clicks Print to PDF on AEM Forms Service Pack 15 ( on OSGi, the Client-side validation fails, it is evident by the error messages shown in the Developer Tools Console window. (FORMS-14029)

  • When a user submits a form on AEM 6.5 Forms Service Pack 17 (, or Service Pack 18 (, Service Pack 19 (, the translation of “Thank-You” messages does not function correctly. However, the messages are correctly translated in the dictionary. (FORMS-13846)

  • When a user previews a form having a Date-Picker component, the date-picker field misaligns with the other form fields. (FORMS-13763)

  • When a user on the environment AEM Forms Service Pack 19 ( calls the API to format numbers, the formatted numbers are not aligned with the respective Locales. As a result, the currency signs are not displayed correctly. The issue persists regardless of the Locale parameter set to “de_DE” or “en_US.” (FORMS-13759)

  • When a user on the environment AEM Forms Service Pack 19 ( converts 16-bit PNGs to PDFs using Img2Pdf PDFG service, it fails and is unable to “Use Acrobat Image conversion” service. (FORMS-13754)

  • On AEM Forms Service Pack 19 (, when a user uploads an existing JobOptions file in the Services / PDF Generator / Adobe PDF Settings section of the adminui of AEM forms JEE, the upload fails. It also shows the following error message (FORMS-13597):
    "An error has occurred while processing your request. Please use the breadcrumb links to navigate to another page."

  • When a user migrates from AEM Forms Service Pack 15 ( to AEM Forms Service Pack ( or AEM Forms Service Pack (, the FD key duplicates, which cause the forms not to translate correctly. (FORMS-13461)

  • When a user puts dispatchers in front of the authors supported by the deployment topology on AMS, the Assign Task submission hangs or fails. (FORMS-8010)

  • Accessibility Related Fixes:

    • Icons on the “formsanddocuments” page are now accessible as per the ANDI standard. (FORMS-13094)
    • Users can access the tool bar by way of the keyboard to save or edit content on the edit page, the tool bar is enhanced as per the ANDI standard. (FORMS-13102)
    • “Required or Mandatory” form fields are accessible as per the ANDI standard. (FORMS-13097)
  • When a user tries to view a form on the page load, it fails to render. (FORMS-13594)

  • The date input field component does not function correctly on Microsoft Edge in Internet Explorer compatibility mode. (FORMS-13170)

  • Stalled email Notification with attachment failed to be sent when the fix for additional steps to use email with attachments is performed on the server. (FORMS-14227)

  • On AEM Forms Workspace on Service Pack 18 (, When a user comments on any uploaded document, it causes the document file to corrupt. (FORMS-13735)

  • On AEM Forms Service Pack 18 (, or Service Pack 19 (, or Service Pack 20 (, when a user tries to search for an Adaptive Form from the side panel, the search fails. (FORMS-14117)

  • When a user edits a form created in German and translated into English, it results in inconsistent language displays between the ‘Preview’ and ‘Edit’ modes. This causes RadioButton and Checkbox components to display in English during ‘Edit’ mode while correctly appearing in German during ‘Preview’ mode. (FORMS-13910)

  • Process purge process tool fails with the error NoClassDefFoundError: org/omg/CORBA/UserException. (FORMS-13751)

  • When a user tries to embed an Adaptive Form (AF) inside a webpage, either external or on AEM Sites, using an embed container, the Adaptive Form guide container introduces an ARIA LABEL. The label has the role=“main” for the embedded form. According to ARIA guidelines, there should only be one role=“main” per page. Therefore, when a user adds another role=“main” for their page’s main content, it is flagged as an accessibility issue. (FORMS-13538)

  • On AEM Forms Service Pack 19 (, when using the drop-down in an Adaptive Form, the drop-downs with placeholder text retain the value of id="emptyValue". As such, if a form has multiple drop-down components, each has id="emptyValue" that is not correct as per the ARIA guidelines. (FORMS-13370).

  • When a user reloads an Interactive Communication after the data is submitted through XML, a blank space between the text block occurs in the generated PDF. (FORMS-13481)

  • Missing IPH for “Prepare for DSC Deployment step” screen while running ConfigurationManager. (FORMS-10699)

  • When a user adds a new dictionary to translate a form with existing dictionaries, the old translations become invalidated. The following issues arise: (FORMS-13576)

    • Some fields fail to populate the translated data.
    • Some fields are not translated into the new language, even though the data is successfully saved to the dictionary.

Forms Designer forms-desgner-6521

  • When a user adds a new table to an existing form using AEM Forms Designer on the environment AEM Forms Service Pack 19 (, it crashes. (LC-3921978)

  • When a user renders an Adaptive Form on Linux® environment, an extra space between the field components occurs. (LC-3921957)

  • When a user converts an XTG file to PostScript format using the Output Service, it fails with the error: (AEM_OUT_001_003:Unexpected Exception: PAExecute Failure: XFA_RENDER_FAILURE). (LC-3921720)

    To resolve the issue:
    Check if the data contains special characters like Zero Width Space (0x200b). If yes, then use the flag by adding the tag <behaviorOverride>patch-LC3921720:1</behaviorOverride> in the XCI file as given in custom_xfa.xci file.

  • When using AEM Forms Service Pack 18 ( within a Linux® environment, XMLFM crashes on CPUs not supporting AVX / AVX2 instruction featuring AMD® processors. (LC-3921718)

  • When a user creates a PDF from XDP using the Forms Output service, the user is not able to configure “settings” on “individual text blocks” in the XDP to control what is “artifacted.” (LC-3921954)

Foundation foundation-6521

Apache Felix foundation-apachefelix-6521

  • Upgrade issue with AEM 6.5 Service Pack 19 (SP19) in which the Application server context-root path is missing for unauthorized requests to Apache Felix following the installation of SP19. Update to Apache Felix Web Management Console 4.9.8. (NPR-41933)

Campaign foundation-campaign-6521

  • AEM 6.5 Service Pack 15 is producing continuous error logs with significant entries. The following issues were reported:

    • 404 INFO error for missing resource at path /libs/granite/ui/content/shell/start.html
    • Error log entry for an uncaught SlingException due to NullPointerException at

    Error logs should not be filled with frequent and voluminous error entries, and the AEM instance should function without issues related to missing resources or exceptions. (CQ-4357064)

Cloud Services foundation-cloudservices-6521

  • Remove Google Guava from AEM Cloud Services. (CQ-4356436)

Granite foundation-granite-6521

  • You cannot select Delete or Modify without Browse permission in the Configuration browser. (GRANITE-51002)

Integrations foundation-integrations-6521

  • Regarding cq-target-integration, need to remove non-test usage of Google Guava. (CQ-4357101)
  • Replacement of Service Account (JSON Web Token or JWT) credentials with OAuth2 Server-to-Server credentials (also known as Service Principals). (NPR-41994)
  • Create Audience request fails with IMS (Identity Management System) configuration. (NPR-41888)
  • When a customer attempts to view the Payload page, the content does not display properly due to a malformed URL; a 404 error is displayed. A missing question mark symbol in the URL, before the query parameters, caused the error. This issue requires the customer to insert the question mark symbol to view the Payload page correctly. (NPR-41957)
  • Remove code and dependency of Adobe Search&Promote from AEM 6.5, which reached end of life on September 2022 as per notice. (NPR-41855)

Localization foundation-localization-6521

  • In the Templates editor, the text string No video available. is not localized. (SITES-13190)
  • String after activating or deactivating a user are not localized in Tools > Security > Users > any_user_name > Activate > OK, and select any_user_name > Deactivate > OK. (NPR-41737)

Oak foundation-oak-6521

  • Performance regression fix - Avoid range queries in like conditions. (OAK-9481)
  • The new Oak version is 1.22.20.

Platform foundation-platform-6521

  • The Unclosed resource resolver error is being experienced for The MessageGatewayService class, which is out-of-the-box, was being used without a resource resolver. The issue occurred on any page with a form submission button that sends an email using this class. (NPR-41853)
  • In the About Adobe Experience Manager dialog box, the copyright year is still 2023. (CQ-4356349)

Translation foundation-translation-6521

  • An issue with AEM 6.5.19 out-of-the-box translation status not updating as expected for a launch. After importing a translated file into a translation job associated with an AEM launch, the status was supposed to be Approved. Instead, the status became Ready for Review, which is not the expected behavior. (NPR-41756)
  • When creating multiple configurations and going to the Translation Cloud Services configurations, not all elements are displayed in the UI. Only the first 40 elements / folder are displayed; lazy loading is triggered but not adding more content. (NPR-41829)
  • Garbled characters occur if there is Japanese on the Permissions page in the Touch user interface. (NPR-41794)
  • AEM 6.5.14 and 6.5.9 do not send an emoji for translation. (CQ-4357000)

User interface foundation-ui-6521

  • In Tools > Security > Users > <user_name> > Profiles, in the Edit User Settings dialog box, clicking Cancel does not exit the dialog box. (NPR-41793)
  • The Granite pathfield component at /libs/granite/ui/components/coral/foundation/form/pathfield fails to enable the Select button when an asset is selected. After the path field is popped up, and the user selects the asset checkbox, the Select button is not enabled; it does not change from gray to blue. (NPR-41970)
  • An issue exists with the Content Fragment Model (CFM) reference field within AEM. Despite the CFM reference field being set as mandatory, the system allows users to click Save to save content with non-CFM values in certain scenarios. The Save button should be dimmed (unavailable). (NPR-41894)
  • The standard Coral user interface dialog boxes that use the successresponse action must trigger a Success Response after the action. But in AEM 6.5 Service Pack 19, the reload action is not invoked and no message is displayed. (NPR-41797)
  • AEM Notifications links are not working in AEM 6.5 Service Pack 18. When upgrading to Service Pack 18, the AEM Notifications links are not working when selecting the messages by way of the notifications button. (NPR-41792)

Workflow foundation-workflow-6521

  • In AEM 6.5.18, repeated errors in removing from user metadata cache during purge. (NPR-41762)

Install Experience Manager install

  • Experience Manager requires Experience Manager 6.5. See upgrade documentation for detailed instructions.
  • The Service Pack download is available on Adobe Software Distribution.
  • On a deployment with MongoDB and multiple instances, install Experience Manager on one of the Author instances using the Package Manager.
Adobe does not recommend that you remove or uninstall the Experience Manager package. As such, before you install the pack, you should create a backup of the crx-repository in case you must roll it back.

Install the Service Pack on Experience Manager 6.5 install-service-pack

  1. 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.

  2. Before installing, take a snapshot or a fresh backup of your Experience Manager instance.

  3. Download the Service Sack from Software Distribution.

  4. Open Package Manager, then select Upload Package to upload the package. To know more, see Package Manager.

  5. Select the package, then select Install.

  6. 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 installation is successful. Typically, this issue occurs in the Safari browser but can intermittently occur in any browser.

Automatic installation

There are two different methods that you can use to install Experience Manager

  • Place the package into ../crx-quickstart/install folder when the server is available online. The package is automatically installed.
  • Use the HTTP API from Package Manager. Use cmd=install&recursive=true so that the nested packages are installed.
Experience Manager does not support Bootstrap installation.

Validate the installation

To know the platforms that are certified to work with this release, see the technical requirements.

  1. The product information page (/system/console/productinfo) displays the updated version string Adobe Experience Manager ( under Installed Products.

  2. All OSGi bundles are either ACTIVE or FRAGMENT in the OSGi Console (Use Web Console: /system/console/bundles).

  3. The OSGi bundle org.apache.jackrabbit.oak-core is version 1.22.20 or later (Use Web Console: /system/console/bundles).

Install Service Pack for Experience Manager Forms install-aem-forms-add-on-package

For instructions to install the Service Pack on Experience Manager Forms, see Experience Manager Forms Service Pack installation instructions.

The Adaptive Forms feature, available in AEM 6.5 QuickStart, is designed for exploration and evaluation purposes only. For production use, it is essential to obtain a valid license for AEM Forms, as Adaptive Forms functionality requires proper licensing.

Install GraphQL Index Package for Experience Manager Content Fragments install-aem-graphql-index-add-on-package

Customers using GraphQL must install the Experience Manager Content Fragment with GraphQL Index Package 1.1.1.

Doing so lets you add the required index definition based on the features they actually use.

Failure to install this package may result in slow or failed GraphQL queries.

Only install this package once per instance; it does not need to be reinstalled with every Service Pack.

UberJar uber-jar

The UberJar for Experience Manager 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:

UberJar and the other related artifacts are available on Maven Central Repository instead of Adobe Public Maven repository ( The main UberJar file is renamed to uber-jar-<version>.jar. So, there is no classifier, with apis as the value, for the dependency tag.

Deprecated and removed features removed-deprecated-features

See Deprecated and removed features.

Known issues known-issues

  • Related to Oak
    From Service Pack 13 and above, the following error log has begun to appear which affects the persistence cache:

    code language-shell
    org.h2.mvstore.MVStoreException: The write format 1 is smaller than the supported format 2 [2.0.202/5]
    at org.h2.mvstore.DataUtils.newMVStoreException(
        at org.h2.mvstore.MVStore.getUnsupportedWriteFormatException(
        at org.h2.mvstore.MVStore.readStoreHeader(
        at org.h2.mvstore.MVStore.<init>(
        at org.h2.mvstore.MVStore$
        at org.h2.mvstore.db.Store.<init>(


    code language-shell
    org.h2.mvstore.MVStoreException: The write format 1 is smaller than the supported format 2 [2.1.214/5].

    To resolve this exception, do the following:

    1. Delete the following two folders from crx-quickstart/repository/

      • cache
      • diff-cache
    2. Install the Service Pack, or restart Experience Manager as a Cloud Service.
      New folders of cache and diff-cache are automatically created and you no longer experience an exception related to mvstore in the error.log.

  • Update your GraphQL queries that may have used a custom API name for your content model to use the default name of the content model instead.

  • A GraphQL query may use the damAssetLucene index instead of the fragments index. This action might result in GraphQL queries that fail, or take a long time to run.

    To correct the problem, damAssetLucene has to be configured to include the following two properties under /indexRules/dam:Asset/properties:

    • contentFragment

      • jcr:primaryType="nt:unstructured"
      • name="jcr:content/contentFragment"
      • propertyIndex="{Boolean}true"
      • type="Boolean"
    • model

      • jcr:primaryType="nt:unstructured"
      • name="jcr:content/data/cq:model"
      • ordered="{Boolean}true"
      • propertyIndex="{Boolean}true"
      • type="String"

    After the index definition is changed, a reindexing is required (reindex = true).

    After these steps, the GraphQL queries should perform faster.

  • When trying to move, delete, or publish either Content Fragments, Sites, or Pages, there is an issue when Content Fragment references are fetched. The background query fails. That is, 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):

    code language-xml
    "tags": [
    "refresh": true
  • 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.

  • The following errors and warning messages may be displayed during installation of Experience Manager 6.5.x.x:

    • "When the Adobe Target integration is configured in Experience Manager using the Target Standard API (IMS authentication), then exporting Experience Fragments to Target results in wrong offer types getting created. Instead of type “Experience Fragment”/source “Adobe Experience Manager,” Target creates several offers with type “HTML”/source “Adobe Target Classic.”
    • com.adobe.granite.maintenance.impl.TaskScheduler: No maintenance windows found at granite/operations/maintenance.
    • Adaptive Form server-side validation fails when aggregate functions such as SUM, MAX, and MIN are used (CQ-4274424).
    • com.adobe.granite.maintenance.impl.TaskScheduler : No maintenance windows found at granite/operations/maintenance.
    • The hotspot in a Dynamic Media interactive image is not visible when previewing the asset through the Shoppable Banner viewer.
    • bundle (395)[] : Timeout waiting for register change to complete unregistered.
  • Starting with AEM 6.5.15, the Rhino JavaScript Engine provided by the org.apache.servicemix.bundles.rhino bundle has a new hoisting behavior. Scripts that use the strict mode (use strict;) have to declare their correct variables. Otherwise, they do not get run, and end up throwing a runtime error.

  • Installing tagging related out-of-the-box content by way of an official update package resets the languages property of the /content/cq:tags node to default. This action is true for Service Packs, Security Service Packs, Extended Feature Packs, Cumulative Feature Packs, patches, and so on. Therefore, it is necessary to add it from the properties before installation.

Known issue for AEM Sites known-issues-aem-sites-6521

Known issues for AEM Forms known-issues-aem-forms-6521

  • After installing AEM Forms JEE Service Pack 21 (, if you find duplicate entries of Geode jars (geode-*-1.15.1.jar and geode-*- under the <AEM_Forms_Installation>/lib/caching/lib folder (FORMS-14926), perform the following steps to resolve the issue:

    1. Stop the locators, if they are running.
    2. Stop the AEM Server.
    3. Go to the <AEM_Forms_Installation>/lib/caching/lib.
    4. Remove all the Geode patch files except geode-*- Confirm that only the Geode jars with version are present.
    5. Open the command prompt in administrator mode.
    6. Install the Geode patch using the geode-*- file.
  • If a user tries to preview a draft letter with saved XML data, it gets stuck in Loading state for some specific letters. (FORMS-14521)
    To resolve the issue, perform the following steps:

    1. Download the hotfix from the Software Distribution portal.
    2. Upload and install the package (.zip) using the CRX Package Manager.
  • After upgrading to AEM Forms Service Pack, the PaperCapture service fails to perform OCR (Optical Character Recognition) operations on PDFs. The service does not generate output in the form of a PDF or a log file. To resolve the issue, see the troubleshooting article. (CQDOC-21680)

OSGi bundles and content packages included osgi-bundles-and-content-packages-included

The following text documents list the OSGi bundles and Content Packages included in this Experience Manager 6.5 Service Pack release:

Restricted websites restricted-sites

These websites are only available to customers. If you are a customer and need access, contact your Adobe account manager.