Updating your Content Fragments for optimized GraphQL Filtering; Authentication for Remote AEM GraphQL Queries on Content Fragments; AEM GraphQL API with Content Fragments - Sample Content and Queries; Hybrid and SPA AEM Development. A pre-compiled AEM package is available for easy installation on local environments using CRX Package Manager: aem-guides-wknd. Do NOT attempt to set the AEM_PROXY_HOST via Cloud. js initializes and exports the AEM Headless Client used to communicate with AEM; src/api/usePersistedQueries. The Origin header must not be passed to AEM publish via the Dispatcher: Check the clientheaders. The AEM GraphQL API allows you to update the default cache-control parameters to your queries in order to improve performance. This file causes the SDK and runtime to validate and. AEM dispatcher: Filters, ignoreUrlParams, virtualhosts, rewrites by Aanchal Sikka Overview In this extensive blog post, we'll delve into the topics of filters, ignoreUrlParams, virtual hosts, and rewrites, providing a detailed examination of their best practices and simplifying their operational me. supports headless CMS scenarios where external client applications render experiences using content managed in AEM. Select main from the Git Branch select box. This feature is core to the AEM Dispatcher caching strategy. GraphQL Query Best Practices (Dispatcher and CDN) The Persisted Queries are the recommended method to be used on publish instances as: they are cached; they are managed centrally by AEM as a Cloud Service; NOTE. Repository Browser supports a read-only view of the resources and properties of AEM on Production, Stage, and Development, as well as Author, Publish, and Preview. If you require a single result: ; use the model name; eg city . Managing AEM hosts. The following AEM documentation includes everything from essential guides for those new to the content management system (CMS) to videos, tutorials, and further learning resources to get the most out of AEM 6. 5 version, I have installed grpahqli-0. The AEM Headless quick setup gets you hands-on with AEM Headless using content from the WKND Site sample project, and a React App that consumes the content over AEM Headless GraphQL APIs. Browse the following tutorials based on the technology used. Dispatcher filters. AEM hosts;. js application run from the command line to update asset metadata on AEM as a Cloud Service using Assets HTTP API. It provides a more efficient, powerful, and flexible alternative to traditional REST. Learn to use the Experience Manager desktop app to connect repositories and desktop applications to provide faster access to resources and streamlined workflows. The GraphiQL tool also enables users to persist or save queries to be used by client applications in a production setting. and thus make the content more reusable… In this design pattern, the SPA application is completely separated from AEM, and content from AEM is consumed through headless GraphQL APIs as needed. The default cache-control values are:. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL Explorer. Review existing models and create a model. 5 | Persistent query updated with Graphql Introspection query. aem. Content Fragment Models determine the schema for GraphQL queries in AEM. Leverage your professional network, and get hired. security. This project contains the AEM CIF Venia reference site. Developer. Further Reference. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. I added two demo classes to my project and reinstall bundle. for. May 2020 - Present3 years 4 months. With the ability to extract metadata from files uploaded to Experience Manager Assets, metadata management integrates. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. In the String box of the Add String dialog box, type the English string. Second, for fan out to work, edges in the graph must be bidirectional. The content in AEM is managed through Content Framnents and exposed through GraphQL API as a JSON. When configuring CORS on AEM Publish, ensure: The Origin HTTP request header cannot be sent to AEM Publish service, by removing the Origin header (if previously added) from the. Click on the "Flush" button to clear the cache. In this chapter, you explore how AEM’s GraphQL APIs can drive the experience in an external application. IO, and gRPC, we revisited the GraphQL client and built a development environment that is both simple and powerful. The AEM GraphQL API is a customized version based on the standard GraphQL API specification, specially configured to allow you to perform (complex) queries on your Content Fragments. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL Explorer. For GraphQL queries with AEM, there are a few extensions: If you require a single result: use the model name; for example, city; If you expect a list of results: add List to the model name; for example, cityList Usually, it relies on invalidation techniques that ensure that any content changed in AEM is properly updated in the Dispatcher. ( 258ec3b Oct 31, 2023 68 commits . Open the model in editor. It needs to be provided as an OSGi factory configuration; sling. The way it works is you insert these placeholders in the model where you want tab breaks to occur in the Content Fragment. Adobe Experience Manager as a Cloud Service uses AEM Publish Dispatcher filters to ensure only requests that should reach AEM do reach AEM. TIP. 3 - Explore the AEM GraphQL API; 4 - Persisted GraphQL Queries; 5 - Client Application Integration; Headless First Tutorial. Ensure you adjust them to align to the requirements of your project. In this example, we’re restricting the content type to only images. Use the adventures-all query. This isn't so much a field as it is more of a cosmetic enhancement. It is exposed at /api/assets and is implemented as REST API. Documentation AEM AEM Tutorials AEM Headless Tutorial Dispatcher filters for AEM GraphQL. Experience implementing WCM/CMS for. The. 5. Ensure you adjust them to align to the requirements of your project. felix. Some of the key principles of Apache Sling is it’s web application framework, which is designed for content-oriented application development, which provides RESTful web API to JCR based application. Previous page. Experience deploying self-contained JavaScript applications in AEM. Ensure that the version of Dispatcher Tools is provided via the AEM SDK version matching the AEM as a Cloud Service version. The AEM Commerce Add-On and CIF Core Components connect to the commerce GraphQL endpoint via the AEM server and directly via the browser. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). A project template for AEM-based applications. GraphQL queries and their JSON responses can be cached if targeted as GET. 3766. Adobe Experience Manager as a Cloud Service uses AEM Publish Dispatcher filters to ensure only requests that should reach AEM do reach AEM. Tap the ellipsis next to the environment in the Environments section, and select Developer Console. The AEM Headless Client for JavaScript is used to execute the GraphQL persisted queries that power the app. apache. Use the BundleContext to register the MBean as an OSGi service. Migrate from AEM 6. Experience LeagueDispatcher; AEM; Usually, Dispatcher is the next server that might serve the document from a cache and influence the response headers returned to the CDN server. Created for: Beginner. Learn to use the delegation pattern for extending Sling Models. Content Fragments in AEM provide structured content management. It appears that the GraphQL endpoint is blocked on the dispatcher. The zip file is an AEM package that can be installed directly. Integrate AEM Forms as a Cloud Service with Adobe Sign; Integrate AEM Forms as a Cloud Service with DocuSign; Integrate Adaptive Forms to. publish /(s) based on the protocol used— this will enable the forward mapping (resolve) — map the incoming URL to the content path (forward mapping. Retrieving an Access Token. We’re excited to announce that Postman’s new GraphQL client is in open beta! Applying our learnings from building support for WebSockets, Socket. Dispatcher filters. Using a REST API introduce challenges: Large number of requests for fetching one object at a time Often “over-delivering” content, meaning the application receives more than it needs To overcome these challenges GraphQL provides a query-based API allowing clients to query AEM for only the content it needs, and to receive using a single API. For Prisma, we need @prisma/client, @nexus/schema and nexus-plugin-prisma as a regular dependencies and @prisma/cli as a dev dependency. getAdventures(. GraphiQL is included in all environments of AEM (but will only be accessible/visible when you configure your endpoints). The React App in this repository is used as part of the tutorial. Topics: GraphQL API View more on this topic. In such cases there is the danger that multiple copies of the same JS library may be included in the final HTML output. In addition to pure AEM-managed content CIF, a page can. Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL Explorer. 5. Recommendation. AEM Publish service requires an AEM Dispatcher configuration to be added to the AEM Publish’s Dispatcher configuration. In previous releases, a package was needed to install the GraphiQL IDE. Overview; Single-page app; Web Component; Mobile; Server-to-server; Configurations. An end-to-end tutorial illustrating how to build-out and expose content using AEM’s GraphQL APIs and consumed by an external app, in a headless CMS scenario. An. APOLLO CLIENT. Hence, AEM uses GraphQL to exchange commerce data with Adobe Commerce and with any commerce engine via I/O Runtime. If you require a basic introduction to creating Content Fragment Models, please see the appropriate chapter in the basic tutorial. The use of React is largely unimportant, and the consuming external application could be written in any framework. Add an update script that helps to update the dispatcher configuratio… by @froesef in #966; CQ-4347346 Removing npx dependency from package. The project can be used in two variants: AEM as a. AEM code & content package (all, ui. Learn how and when to leverage AEM Author and Publish environments when using AEM’s GraphQL APIs. security. Unzip the downloaded aem-sdk-xxx. The following are examples of possible approaches for constructing URLs for AEM GraphQL API and image requests, for several popular headless frameworks and platforms. By default all requests are denied, and patterns for allowed URLs must be explicitly added. Learn how to create GraphQL queries to return content from Adobe Experience Manager (AEM) and how to use the GraphiQL tool to quickly test, refine, and debug queries. With Adobe Experience Manager (AEM), you can use Content Fragments, together with the AEM GraphQL API (a customized implementation, based on standard GraphQL), to headlessly deliver structured content for use in your applications. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. Configuration Browsers — Enable Content Fragment Model/GraphQL. A modern content delivery API is key for efficiency and performance of Javascript-based frontend applications. Caching AEM pages or fragments in the AEM Dispatcher is a best practice for any AEM project. Tap the Technical Accounts tab. Create the folder ~/aem-sdk/publish. Project Configurations; GraphQL endpoints;. The default cache-control values are:. This is your 24 hour, developer access token to the AEM as a Cloud Service environment. Additional AEM Guides. Clients can send an HTTP GET request with the query name to execute it. The GraphiQL tool also enables users to persist or save queries to be used by client applications in a production setting. If your modeling requirements require further restriction, there are some other options available. To share with the community, we talked to the AEM support team and found that it was an issue with 6. 1. The GraphiQL tool also enables users to persist or save queries to be used by client applications in a production setting. Double-click the aem-author-p4502. (FilterHandler. To address this problem I have implemented a custom solution. It becomes more difficult to store your assets,. The sample React app has three main parts: The src/api folder contains files used to make GraphQL queries to AEM. Unpack the Dispatcher Tools into ~/aem-sdk/dispatcher. Get started with Adobe Experience Manager (AEM) and GraphQL. Deploying an AEM Headless application requires attention to how AEM URLs are constructed to ensure the correct AEM host/domain is. AEM’s GraphQL APIs for Content Fragments. It appears that the GraphQL endpoint is blocked on the dispatcher. Additionally, enable the GraphQL endpoint configurations that can be consumed by external applications to fetch headless content. 4. As a AEM BackEnd Developer, I have experience in. Example applications are a great way to explore the headless capabilities of Adobe Experience Manager (AEM). Further Reference. Adobe Experience Manager as a Cloud Service’s Cross-Origin Resource Sharing (CORS) facilitates non-AEM web properties to make browser-based client-side calls to AEM’s GraphQL APIs, and other AEM Headless resources. 0+ version supports GraphQL API to expose the Content Fragment to enable the headless content experience. Related Documentation. GraphQL_SImple. AEM Publish does not use an OSGi configuration. Tutorials by framework. Enable AEM Dispatcher caching. The Single-line text field is another data type of Content. After completing this video, you should be able to create AEM project using Archetypes. Build a React JS app using GraphQL in a pure headless scenario. GraphQL API. Managing Content. file. Search for “GraphiQL” (be sure to include the i in GraphiQL ). Next, explore the power of AEM’s GraphQL API using the built-in GraphiQL IDE. Schemas on publish are the most critical as they provide the foundation for live delivery of Content Fragment. See full list on experienceleague. References to other content, such as images or other Content Fragments can be dynamically inserted in-line within the flow of the text. Using the GraphiQL IDE. See GraphQL. Using a REST API introduce challenges: Enable AEM Dispatcher caching. 4 web server that runs on Linux i686 and is packaged using the tar. . AEM as Cloud Service is shipped with a built-in CDN. The CIF Add-On provides a GraphQL proxy servlet at /api/graphql which can optionally be used for local development. Explore AEM's GraphQL APIs using the built-in GrapiQL IDE. An aspiring Adobe AEM and Open Source developer with a passion for web development and a strong foundation in software development technologies. Unpack the Dispatcher Tools into ~/aem-sdk/dispatcher. Persisted queries are more performant than client-defined GraphQL queries, as persisted queries are executed using HTTP GET, which is cache-able at the CDN and AEM Dispatcher tiers. For creating one please follow the steps below: Go to Tools → Assets → Content fragments models (If you don’t have Content Fragments Models here then that means your instance is not cloud sdk. To act on the change, we need a GraphQL server that supports introspection. Dispatcher cache files are updated unexpectedly | AEM; Unable to view dictionary element in UI (user and system) VLT RCP content synchronization fail; AEM: Collecting status information for troubleshooting in Web Console; Request queue becomes unpublished; Customer unable to delete records from custom schema; How to download. It is a module for different web servers, such as Microsoft IIS or Apache – the latter being the one more commonly used. Documentation AEM AEM Tutorials AEM Headless Tutorial Dispatcher filters for AEM GraphQL. AEM Publish service requires an AEM Dispatcher configuration to be added to the AEM Publish’s Dispatcher configuration. Aem dispatcher – tips & tricks. Customers using CORS requests, might need to review and update their CORS configuration in the Dispatcher. The response of a GET request can be cached at the dispatcher and CDN layers, ultimately improving the performance of the requesting client application. Tap the ellipsis next to the environment in the Environments section, and select Developer Console. GraphQL_SImple. A simple React app is used to query and display Team and Person content exposed by AEM’s GraphQL APIs. The response of a GET request can be cached at the Dispatcher and Content Delivery Network (CDN) layers, ultimately improving the performance. This feature is being gradually rolled out to customers in early September. Brands have a lot of flexibility with Adobe’s CIF for AEM. Recommendation. It is best practice and highly recommended to use persisted queries when working with the AEM GraphQL API. To address this problem I have implemented a custom solution. They can also be used together with Multi-Site Management to. PSD files with a color space other than CMYK, RGB, Grayscale, or Bitmap are not supported. View the source code on GitHub. json. CDN logging, which as its name indicates, performs logging at the CDN. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. react project directory. Developer Console is accessed per AEM as a Cloud Service. properties file beneath the /publish directory. Documentation AEM AEM Tutorials AEM Headless Tutorial Dispatcher filters for AEM GraphQL. Dispatcher changes not reflected in INT environment “AH01620: Could not open password file” in logs after configuring Basic Auth in AEM dispatcher; When are browsers counted in Analytics? Fine-Grained Priorities on Recommendations Activity; Recommendation is filtering criteria while creating activity Check out these additional journeys for more information on how AEM’s powerful features work together. Register now! SOLVEDThe Dispatcher is Adobe Experience Manager’s caching and/or load-balancing tool that helps realize a fast and dynamic Web authoring environment. AEM Publish does not use an OSGi configuration. The content returned can then be used by your applications. One could export an AEM page in JSON format via a REST call, however there are many fields in the JSON that the Spring Boot app does not use. apache. Upload and install the package (zip file) downloaded in the previous step. Persisted queries are more performant than client-defined GraphQL queries, as persisted queries are executed using HTTP GET, which is cache-able at the CDN and AEM Dispatcher tiers. Using GraphQL on the other hand does NOT have the extra unwanted data. Not sure what the reason could be but this is happening even with untouched old persistent queries as well. 2. An end-to-end tutorial illustrating how to build-out and expose content using AEM Headless. 5 with Service Pack 16 or 17, when in the List view of sites with the “Workflow” column enabled, you cannot sort the list based on the items in that column. Overview; Single-page app; Web Component; Mobile; Server-to-server; Configurations. Adobe Experience Manager as a Cloud Service uses AEM Publish Dispatcher filters to ensure only requests that. To do this, set the JSP session flag to True: <%@ page session="true"%>. In addition to pure AEM-managed content CIF, a page can. Click OK. It is best practice and highly recommended to use persisted queries when working with the AEM GraphQL API. Create Content Fragments based on the. Use the adventures-all query. Designed for flexibility, GraphQL delivers the exact content requested and nothing more. Explicit configurationWith Adobe Experience Manager (AEM) as a Cloud Service, Content Fragments lets you design, create, curate, and publish page-independent content. The GraphQL API of AEM provide a powerful query language to expose data of Content Fragments to downstream applications. An end-to-end tutorial illustrating advanced concepts of Adobe Experience Manager (AEM) GraphQL APIs. A “Hello World” Text component displays, as this was automatically added when generating the project from the AEM Project archetype. Before you begin your own SPA. In this example, we’re restricting the content type to only images. d/filters":{"items":[{"name":"default_filters. Code. Run the following command to build and deploy the entire project to AEM: $ mvn clean install -PautoInstallSinglePackage. supports headless CMS scenarios where external client applications render experiences using content managed in AEM. For GraphQL queries with AEM there are a few extensions: If you require a single result: use the model name; for example, city; If you expect a list of results: add List to the model name; for example, cityList The GraphiQL Explorer tool enables developers to create, and test queries against content on the current AEM environment. With CIF, AEM integrates seamlessly with Adobe Commerce, making it the easiest solution for creating. This document is part of a multi-part tutorial. NOTE. Disadvantages: You need to learn how to set up GraphQL. Dispatcher filters. The ability to customize a single API query allows you to retrieve and deliver the specific content that you want/need to render (as the. Updating your Content Fragments for optimized GraphQL Filtering; Authentication for Remote AEM GraphQL Queries on Content Fragments; AEM GraphQL API with Content Fragments - Sample Content and Queries; Hybrid and SPA AEM Development. Solved: Hello, I am trying to install and use Graph QL in AEM 6. The configuration file contains a series of single-valued or multi-valued properties that control the behavior of Dispatcher: Adobe Experience Manager as a Cloud Service’s Cross-Origin Resource Sharing (CORS) facilitates non-AEM web properties to make browser-based client-side calls to AEM’s GraphQL APIs, and other AEM Headless resources. The basic operation of queries with GraphQL for AEM adhere to the standard GraphQL specification. x. doFilter. In the previous chapter, you have explored some advanced GraphQL queries to gather data for the WKND app. The content in AEM is managed through Content Framnents and exposed through GraphQL API as a JSON. How does cache invalidation for AEM Dispatcher work with AEM and commerce?This end-to-end tutorial continues the basic tutorial that covered the fundamentals of Adobe Experience Manager (AEM) Headless and GraphQL. AEM Publish service requires an AEM Dispatcher configuration to be added to the AEM Publish’s Dispatcher configuration. GraphQL Query Editor{#sites-graphql-query-editor-6519} ; GraphQL Editor user interface does not let you scroll through all the persisted queries when there is a high number of queries (for example, more than 25). TIP. {"payload":{"allShortcutsEnabled":false,"fileTree":{"dispatcher/src/conf. apache. This configuration tells the Dispatcher to fetch this URL from it’s AEM instance it fronts every 300 seconds to fetch the list of items we want to allow through. If a caching issue is suspected, you should republish the pages in question and ensure that a virtual host is available that matches the ServerAlias localhost, which is required for Dispatcher cache invalidation. doFilter. Except the Downstream Caching section, it doesn’t discuss caching of objects on end-user clients such as browsers, although many of the underlying concepts are similar. 1. Documentation AEM AEM Tutorials AEM Headless Tutorial Dispatcher filters for AEM GraphQL. Copy the Quickstart JAR file to ~/aem-sdk/publish and rename it to aem-publish-p4503. js application is invoked from the command line. The developer performs most of the technical configurations to enable Content Architect and Content Authors to produce headless content. Dispatcher cache files are updated unexpectedly | AEM; Unable to view dictionary element in UI (user and system) VLT RCP content synchronization fail; AEM: Collecting status information for troubleshooting in Web Console; Request queue becomes unpublished; Customer unable to delete records from custom schema; How to download. Author and Publish Architecture. Content Fragments. Populates the React Edible components with AEM’s content. The OSGI configuration outlined in this document is sufficient for: Single-origin resource sharing on AEM Publish. Using this path you (or your app) can: access the GraphQL schema, send your. 5. Created for: Intermediate. GraphQL in Adobe Experience Manager (AEM) is a query language and runtime APIs that allows to request exactly the data which we need. extensions must be set to [GQLschema]Documentation AEM AEM Tutorials AEM Headless Tutorial Dispatcher filters for AEM GraphQL. 0. AEM provides a Translation Integration Framework for headless content, allowing Content Fragments and supporting assets to be easily translated for use across locales. The GraphiQL tool also enables users to persist or save queries to be used by client applications in a production setting. Ensure that the version of Dispatcher Tools is provided via the AEM SDK version matching the AEM as a Cloud Service version. Abstract. Submit Search. It has the aim of storing (or “caching”) as much of the static website content as possible and accessing. Unpack the Dispatcher Tools into ~/aem-sdk/dispatcher. ) ) the iOS application’s views invoke to get adventure data. at org. Learn how Experience Manager as a Cloud Service works and what the software can do for you. This is a core feature of the AEM Dispatcher caching strategy. apache. Learn how to configure AEM Publish Dispatcher filters for use with AEM GraphQL. impl. Persisted queries are more performant than client-defined GraphQL queries, as persisted queries are executed using HTTP GET, which is cache-able at the CDN and AEM Dispatcher tiers. The GraphiQL tool also enables users to persist or save queries to be used by client applications in a production setting. Imagine a standalone Spring boot application (outside AEM) needs to display content. Persisted queries also in effect, define an API, and decouple the need for the developer to understand the details of each Content Fragment Model. The GraphQL API in AEM allows you to expose Content Fragment data to downstream applications. Elasticsearch. In the Comment box, type a translation hint for the translator if necessary. Usually, it relies on invalidation techniques that ensure that any content changed in AEM is properly updated in the Dispatcher. Developer. With AEM as a Cloud Service, your teams can focus on innovating instead of planning for product upgrades. NOTE. An end-to-end tutorial illustrating how to build-out and expose content using AEM’s GraphQL APIs and consumed by an external app, in a headless CMS scenario. Solved: GraphQL API in AEM 6. Adobe Experience Manager as a Cloud Service uses AEM Publish Dispatcher filters to ensure only requests that should reach AEM do reach AEM. To get the data stored in CFs, I have a GET request in my JS for the graphql persisted query. AEM GraphQL API requests. For example, a URL such as:Learn how to configure AEM Publish Dispatcher filters for use with AEM GraphQL. Dispatcher filters. TIP. Each publisher is coupled to a single Apache instance equipped with the AEM dispatcher module for a materialized view of the content, serving as the origin for the Adobe-managed CDN. Instructor-led training View all learning options. Experience LeagueManage metadata of your digital assets. GraphQL. This variable is used by AEM to connect to your commerce system. It is available for Apache and IIS both. When configuring CORS on AEM Publish, ensure: The Origin HTTP request header cannot be sent to AEM Publish service, by removing the Origin header (if previously added) from the. Provides a link to the Global Navigation. In this pattern, the front-end developer has full control over the app but Content authors. Bundle start failed. Nov 7, 2022. We are using AEM 6. Learn about the various data types used to build out the Content Fragment Model. Developer. AEM GraphQL API requests. json by @rismehta in #974; Update dispatcher configuration to dispatcher version 2. For server-to-server authentication, you can use Service Credentials of AEM (Access tokens). Currently t he GraphQL feature is enabled by default only on the AEM SDK from 2021-02-04 or newer on AEM as Cloud Service. To determine the correct approach for managing build dependent configurations, reference the AEM Headless app’s framework (for example, React, iOS, Android™, and so on) documentation, as the approach varies by framework. The basic operation of queries with GraphQL for AEM adhere to the standard GraphQL specification. The links in these attributes are run through the AEM Link Externalizer publishLink() to recreate the URL as if it was on a published instance, and as such, publicly available. AEM Dispatcher configurations in generic and AEMaaCS changes like. I have a bundle project and it works fine in the AEM. The WKND reference site is used for demo and training purposes and having a pre-built, fully. Tap on the download button in the top-left corner to download the JSON file containing accessToken value, and save the JSON file to a safe location on your development machine. The configured AEM service’s host/domain is then used to construct the AEM GraphQL API URLs and Image URLs. Sling uses a Java Content Repository, such as Apache Jackrabbit, or in the case of AEM, the CRX Content Repository as its data store. They allow you to prepare content ready for use in multiple locations/over multiple channels, ideal for headless delivery. The auto-generated AEM page must have its type changed to Remote SPA page , rather than a SPA page . TTL for the client (for example, a browser) 7200 seconds is the default (s-maxage=7200) TTL for the Dispatcher and CDN; also known as shared caches. Strong business development professional currently working in Rightpoint Pvt Ltd. sh out docker. Once headless content has been translated,. This article describes how to work with large results in AEM Headless to ensure the best performance for your application. The content resides in AEM.