Adobe Experience Manager Guides

I'm trying to install Adobe Experience Manager 6.5 on Windows Server 2022 on command with the following command C:\AEM\Author>java -jar AEM_6.5_Quickstart.jar -r author -p4502However the installation keeps getting stuck on "Press CTRL -C to shutdown the Quickstart Server:Loading quickstart properties: defaultLoading quickstart properties: instanceLow-memory action set to forkUsing 64bit VM settings, min.heap=1024MB, min permgen=256MB, default fork arguments=[-Xmx1024m, -XX:MaxPermSize=256m]The JVM reports a heap size of 2048 MB, meets our expectation of 1024 MB +/- 20Setting properties from filename 'C:/AEM/Author/AEM_6.5_Quickstart.jar'Setting 'sling.run.modes' to 'author' from command line.Verbose option not active, closing stdin and redirecting stdout and stderrRedirecting stdout to C:\AEM\Author\crx-quickstart\logs\stdout.logRedirecting stderr to C:\AEM\Author\crx-quickstart\logs\stderr.logPress CTRL-C to shutdown the Quickstart server...Java version installed is 21.0.9.Any idea

We need to update the DITA-OT that is included with AEM Guides to get a newer version of FOP. I have managed to migrate our custom PDF plugins to the new OT (4.3.4), but the AEM Sites output is not working. The files are processed properly by the DITA-OT, but are not getting handed over to Guides to create the site. I notice differences in the log output when publishing with different DITA-OT versions. I need a few hints on how to get the job-helper.xsl working in the newer DITA-OT. Working DITA-OT:copy-flag-check:copy-flag:[job-helper] Processing /opt/aem/launcher/profiles/ditamaps/ditamap15676432144876924428/temp/temp20251105141348914/.job.xml to /opt/aem/launcher/profiles/ditamaps/ditamap15676432144876924428/temp/temp20251105141348914/flagimage.list[job-helper] Loading stylesheet /opt/aem/launcher/profiles/ditaot--3922c171-076c-7dd5-4b4b-9b4f895be1bd/DITA-OT/plugins/org.dita.base/xsl/job-helper.xsl New DITA-OT:copy-flag-check: copy-flag: Thanks,-Huntley

I have created a custom property and added it to the file properties (Metadata Schema Form Editor)The custom property list was added to /libs/fmdita/config/metadataListThis made the list available in the Map Console > Advanced > File Properties dropdown.I selected each of the property from the dropdown and generated an output.However, this selection does not seem to have any impact on the metadata that is available in the output. The list is simply not picked up! Can you help me understand the behaviour? And also, help me with the any configuration that needs to be set to get the custom metadata tags propagated to the output? 

 When clicking the 3 dots in the repository I have the option to download the topic as a PDF. Where are the settings for this option and where in the DAM does the generated PDF get saved? 

I want to use conkeyref to add values for elements in the prolog, for eample, prodname or category. I have created the required keys and bound it to the map/topic. I am able to add the conkeyref in the content of the topic, say within a <p> tag, but not with the Prolog. The key list is displayed, but upon selection of a key, the Update button in the dialog box is displayed. So, I used the source mode, and added the conkeyref. It picks up as conkeyref within the prodname or category is DITA valid.  In short, here is the observed behavior:The Attributes panel in Web Editor does not allow updating conkeyref on elements inside <prolog>.Even using “Insert → Reuse Content” or moving the conkeyref to a dedicated attribute on <prodinfo> does not enable the Update button in this context.Is there a configuration that I am missing? OR is this an out-of-the-box behavior in AEM Guides. There’s no configuration to get the conkeyref working for Prolog from t

I have created a subject schema; here is the sample code:  <subjectScheme><title>Subject Schema Definition</title><!-- 1) Permissions (for prolog@view) --><subjectdef keys="permissions"><subjectdef keys="perm_internalonly"><topicmeta><navtitle>InternalOnly</navtitle><shortdesc>Only visible to internal staff</shortdesc></topicmeta></subjectdef><subjectdef keys="perm_lix_experiment"><topicmeta><navtitle>LIX_experiment</navtitle><shortdesc>Experimental LIX audience</shortdesc></topicmeta></subjectdef><subjectdef keys="perm_lix_control"><topicmeta><navtitle>LIX_control</navtitle><shortdesc>Control group for LIX experiments</shortdesc></topicmeta></subjectdef></subjectdef><enumerationdef><!-- bind to prolog@view --><elementdef name="prolog"></elementdef><attributedef name="view

I need to be able to assess the different types of risk associated with our documentation. Think things like Business Risk, Reputational Risk, Compliance Risk, Operational Risk, Country Risk, etc. Currently we have several risk-related attributes that are used to calculate a risk rating.  What would be the best way to solve for this in Guides? I was thinking using tags for all of the dita objects (topics, maps, etc.) could cover the requirement of what type of risk, but I also need to be able to calculate a risk rating based on that data. Is using tags even the right approach? How could we use Guides for calculations like this? Thank you for your help.

When I work on the watermark processing test in the following codes: Document mergedDoc = mock(Document.class);Document mockOutDoc = mock(Document.class);Document ddxDocMock = mock(Document.class); based on the following pom.xml: <!-- Testing --><dependency> <groupId>org.junit.jupiter</groupId> <artifactId>junit-jupiter</artifactId> <version>5.10.0</version> <scope>test</scope></dependency><dependency> <groupId>org.junit.platform</groupId> <artifactId>junit-platform-commons</artifactId> <version>1.10.0</version> <scope>test</scope></dependency><dependency> <groupId>org.junit.platform</groupId> <artifactId>junit-platform-launcher</artifactId> <scope>test</scope></dependency><dependency> <groupId>org.mockito</groupId> <artifactId>mockito-co

The last time I looked, the only instructions I found just said to download the ZIP file from the CRXDE, make changes, and reupload the ZIP file. There were no instructions on how to pick an output option from within the list of outputs, not how to copy the output files into a folder (similar to how the Native PDF Publishing does it) so that you can make incremental changes to the default outputs until you got to what you wanted, etc. For example, I am going to need to generate a tri-pane Windows help file eventually. I know the DITA-OT has such an output because we used it in SDL. Do any instructions exist to help me implement such an output within AEM Guides? And whatever happened to that default ePub output that never worked? It is still listed in the Output Presets in the Folder Profiles, but seems to have disappeared from the selectable default outputs.

Is it expected behavior that if we insert an image from outside the UUID Guides repository (from the AEM/Marketing side of the repository) and apply a condition to that image, that the PDF generation fails? If we do not apply the condition, PDF generation (Native PDF Publishing) works fine. The PDF generation only fails if we apply a condition to the image. (We're trying to consolidate duplicate images between AEM and AEM Guides.) Thanks. AEM 6.5.21 (on-prem installation (21 Dec 2024)AEM Guides v4.6 (UUID, on-prem installation (21 Dec 2024)

I have two question I'm hoping someone can help, thank you in advance. 1. How do I request to update to the latest license version. We are running version 6.5.22 ( will upgrade to 6.5.23) but the product displays 6.2.0. We need to have 6.5.23. Please see attached screen shot. 2. How to I request entitlement to open a ticket for future support.

Hello,I have set up a folder profile that contains a Snippets library, custom CSS, and some custom templates. However, I am the only user who can see them while working in Guides in the folder where the profile is configured. My permissions are high-level admin. Other users can access the folder, but they don't see any of these items that I configured on the folder profile.I did add their group as an Admin user on the Folder Profile as suggested in this help topic - https://experienceleaguecommunities.adobe.com/t5/experience-manager-guides/permission-for-folder-profiles-in-xml-documentation/m-p/419170 This did not change their ability to see the custom content.The users are able to create new files from the custom templates from the Assets UI for the same folder, but not from Guides editor. The Snippets catalog is empty for them.I think there is a permission that I need to enable for this group. Does anyone know what it is?Thanks,Robin

I am facing some blockers with the following implementation :-> Once I start the Review Task and assign the topic to be reviewed by a designated reviewer, the reviewer should also have an option to reject the task (in that case an email will be triggered to the author who has initiated the workflow that the item has been rejected by the reviewer along with the comments that the reviewer has put in).Customizing the toolbar in the inbox section is not possible in AEMaaCS is what I have come across - so I am looking into some insights as to how we can modify the ReviewDITAMAP workflow to accordingly have our requirement fit in?OR another idea that came across my mind was to somehow capture the comments section when the reviewer hits complete. Maybe if a comment like Rejected is put in I want to capture that and accordingly send a notification/email to the initiator stating that the workflow has been completed and when he/she opens the notification the comments should show up with "Reje

We have an AEM page (product.html) that is quite heavy due to a large number of authored components. As a result, only part of the components load during authoring, which affects usability.To work around this, we increased the request size in the main Sling servlet from the default value of 1000 to 2000. This resolved the component loading issue during authoring but its not performance oriented . This page also takes significantly longer to load via the dispatcher URL. we to make it better .I’m looking for best practices or architectural approaches to make the authoring experience smoother and more user-friendly, while also ensuring optimal performance on the dispatcher. Any suggestions to address both concerns would be greatly appreciated.

I am trying to send over a topic for review to the designated users and I can successfully do that. But the issue is once the reviewer has highlighted any text or may have added comments, it is not visible to me. What exactly am I missing?Also, I would like the reviewer to change the document state to "reviewed"/"approved"/"rejected" (based on the options available) - how to do that? 

When I run the following Junit testing code: import com.adobe.aemfd.docmanager.Document;import org.junit.jupiter.api.BeforeEach;import org.junit.jupiter.api.Test;import org.w3c.dom.Element;import javax.xml.parsers.DocumentBuilder;import javax.xml.parsers.DocumentBuilderFactory;import java.io.ByteArrayInputStream;import java.io.InputStream;import java.nio.charset.StandardCharsets;import static org.junit.jupiter.api.Assertions.*;class TableOfContentTest { private Document pdfDoc; private ProcessInputXML processInputXML; private TableOfContent tableOfContent; @BeforeEach void setUp() throws Exception { // Load valid PDF content from a file or resource InputStream pdfInputStream = getClass().getResourceAsStream("/logo.pdf"); // Ensure this file exists in resources pdfDoc = new Document(pdfInputStream); // Initialize the ProcessInputXML object org.w3c.dom.Document inputXML = DocumentBuilderFactory.newInstance().newDocumentBuilder().newD

@divrajsingh could you assist me with the following requirement? I want to align the published content with our organization’s branding guidelines, this includes applying custom CSS, fonts, colors, logos, and possibly modifying the layout or templates used during the publishing process. 

What is the latest aem-service-pkg-6.5 version and where can we update. We are using aem-service-pkg-6.5.21.

Hello AEM Guides Community,I’m new to AEM Guides and working on creating an aggregated document that includes multiple languages in a single PDF output. My main document contains a front page (cover) and then multiple languages each with it's own translated TOC.I want the PDF to show:The front page first,Then for each language submap, a Table of Contents for just that submap,Followed by the actual content of that language submap.What is the recommended way to structure the map and customize the native PDF template to achieve this aggregated, multilingual document with per-submap TOCs?Are there best practices or example templates you can share?Thanks so much for your help!

When searching in AEM Guides (on-prem, v4.6, UUID) for a specific file name GUID, the result returns every instance that GUID is conref-ed to in addition to the master file we are searching for. Is there a way to separate the search results into a list of file names/titles using the search phrase AND then into a list of files where the search phrase appears within the content? For example, when searching within our repository for file name GUID-B2A00D10-2503-48FA-928C-8D84F08CBA0F, 400+ results appear because this was one of our master files that many other topics conref to. The existing filters do not allow for a separation of file name/GUID vs content within a file. Is that possibly a future feature? Can the filters be customized? (I saw an answer from 7/2/25 that mentioned filters may be customizable in version 5.1 or whatever the Q3 2025 release is going to be.)

I'm working on a JavaScript project in VS Code using the AEM Guides Extension framework. In the codebase, there's frequent usage of tcx, but VS Code keeps showing errors like "tcx is not defined" and doesn't provide any IntelliSense for it.How can I configure my project so that:VS Code recognizes tcx as a global object (or however it's defined in the framework)?IntelliSense works properly for tcx and its properties/methods?Any tips on setting up type definitions or project configuration to fix this would be greatly appreciated! 

We are not seeing any way to enter notes about new versions of images in the repository. Is there no way to track version changes to images and other non-DITA assets?

AEM Guide when users select a element in the current open DITA file below a breadcrumb shows the path of the selected elementmy question how can i get the xpath of the selected element  or even better how to get the active (selected) element in the tcx.activeEditor.xmlDocI need to know which xml element is selected in the editor and bind that to the element in the tcx.activeEditor.xmlDocBo, BJ Dita

We are using Guides Version: 5.0.0.211 in AEM 6.5 with service pack 21. We want to add some custom filters in the guides editor. We followed these two documents.https://experienceleague.adobe.com/en/docs/experience-manager-guides/using/install-guide/on-prem-ig/web-editor-configs/conf-custom-file-filtershttps://experienceleague.adobe.com/en/docs/experience-manager-guides/using/knowledge-base/expert-session/metadata-define-manage-utilize-may2024We added filters in the Folder Profile ui_config.json file. First, added the filters in the "browseFilters" section, and it's not coming in the editor. Then added filters in "repositoryFilters" section. Now the filters are appearing in the Advanced Filter popup like below However, when applying these custom filters, the search results are not coming based on that. When inspecting the network call on clicking Apply, in the request payload, only the OOTB filters are going and not our custom filters. Also, we notice something called wi

DITA Specializations in Native PDF Publishing (Topics Disappear in PDF) We have one DITA specialization that appears to be properly configured in AEM Guides. I can insert it and use it in the XML Editor in topics and concepts. In previous AEM Guides versions, this specialization appeared in PDF outputs, but that may have been using FMPS before Native PDF Publishing was released. I don't recall if I ever tested it in the earlier versions of Native PDF Publishing. We abandoned this specialization because there was no easy way to format it for the AEM Sites output. However, we'd like to return to using this specialization (which is based on the PARML element) since DITA is designed for easy customization and future releases will make it easier to format the AEM Sites outputs. The specialization appears in the default DITA-OT PDF output. It is unformatted (expected behavior) because there is no easy to way format the DITA-OT files, but it does appear. Currently (AEM Gui