Adobe Experience Manager Sites

AEM Akamai Cache flush Agent by aem.design Abstract After the first hit to the page in aem and HTML response received for first time from publish instance will get cached on Akamai level. Subsequent request to the same page will be served from the cached content in Akamai rather than hitting dispatcher / publisher. Anytime did you struggled to get the latest HTML from publisher instead of Akamai cache? Well we did!!! What we have donePermalink We have worked on AEM replication agent for flushing Akamai cache whenever page gets published. So, after author change a page content and publish it our Akamai cache flush agent will pick that page and request to akamai for clearing cache. So that user of that page will get the latest content instead of cached old content from Akamai. It is all automated, we don’t need to clear the Akamai cache when new product goes live to prod. We don’t ask DevOps to clear Akamai cache so customers will see latest page. Lets save their 1-2 mins time wh

Front-End Adventures in AEM: Part III by Benjamin Solum Abstract In Parts I and II, I wrote about Clientlibs and then how they’re composed. In Part III, I want to get back to the markup and talk in-depth about AEM’s HTML Template Language or “HTL”, which is often referred to as Sightly. I’ll also be referring to HTL as Sightly for the rest of the series to avoid confusion with “HTML”. This part includes tips on working within Sightly, common Front-End gotchas working with Sightly, and loading our Clientlibs within our templates. As a reminder, this article series is broken into several parts as seen below. Feel free to jump around to the parts that seem interesting to you and please feel free to ask any questions you have about the material covered. *note* — This article series is written with AEM 6.4 and 6.5 in mind but the concepts should apply to future versions and even some older (6.2) Touch UI versions. *note* — Adobe is notorious for moving their documentation around and their

How To Reuse Editable Template With Multiple Sites — Adobe Experience Manager(AEM)? by Albin Issac Abstract Editable templates have been introduced in AEM 6.2, which allows the authors to create and edit templates. Template authors can create and configure templates from the Templates console in the AEM without the help of the development team. Template authors can define the policies, structure, and initial content for the templates that will be shared by all the pages created based on this template. Editable Templates allow the template-authors to configure the client libraries required to style the websites created based on this template — base/common client libraries are included through page rendering component but site-specific client libraries through template policy configuration. Read Full Blog How To Reuse Editable Template With Multiple Sites — Adobe Experience Manager(AEM)? Q&A Please use this thread to ask the related questions.

All You Need To Know About AEM Sites Architect Exam (AD0-E117)Preparation by Hemalatha Chockalingam Abstract Hello everyone, Since I got many requests regarding the preparation strategy that I followed to crack Adobe AEM Sites Architect Exam and there is no recent article on the same due to the new exam pattern, thought of writing this article which will give you insights on the AD0-E117 Exam and spotlight on ample Adobe Learning resources available to prep up ourselves towards this goal. The kickoff point to start your exam preparation for Adobe AD0-E117 AEM Sites Architect starts with the Official Exam Guide from Adobe. It clearly states that this exam covers AEM 6.4, 6.5, and AEM as a Cloud Service. I gave more focus to AEM 6.5, upgrading to AEM 6.5 and AEM as a Cloud Service topics. Before exploring the study materials it is important to have hands-on latest features with AEM (Editable templates, Content & Experience Fragments etc.) and a minimum 3–5 years of Project Impleme

Adobe I/O-Powered AEMaaCS Assets Export Implemented in Real-Time or Batch Mode by Kelvin Xu Abstract AEMaaCS Assets offers a cloud-native digital assets management solution, which is scalable, reliable, and hassle-free. It’s never been a better time for enterprises to adopt such a solution as their centralized DAM system. To share or distribute assets (or their renditions), AEMaaCS provides multiple ways such as asset link share, asset selector, brand portal, etc. But still, there are common use cases where assets (or renditions) just need to be exported to external cloud storage like Azure blob store, S3 bucket, SFTP, etc. (for other systems to further consume) or directly into 3rd party systems like Marketo, Adobe Campaign, PIM, etc. as long as they provide secured asset ingestion endpoints. Traditionally in AEM 6.x, this usually can be accomplished by “publishing” assets into downstream systems (within a workflow or something) via a custom replication agent. This won’t work in AEM

Hello,I have a field on Content fragment to add files. What returns to me is the file path. But, I should display the file name. Should I create an API for this, or there is already an API, where I can send the path so I can get the file and its name? Thanks!

GraphQL Modeling Basics by Adobe Abstract Learn how to define and use Content Fragments in Adobe Experience Manager (AEM) for use with GraphQL. In this video you will: Learn how to create and define a Content Fragment Model Learn about the various data types and validations used to build out the Content Fragment Model Understand how the Content Fragment Model drives the GraphQL API Read Full Blog GraphQL Modeling Basics Q&A Please use this thread to ask the related questions.

Bringing AEM Back to Life with JConsole by Daniel Klco Abstract One of the most frustrating experiences in AEM development is "bricking" an instance. This happens when you do something that renders the instance unusable due to no longer being able to login or access the repository when it's running. Most of the times when this has happened to me when I've been messing with the authentication portions of AEM. Most, recently while working on the com.adobe.granite.auth.oauth bundle. This bundle is the basis for a number of AEM authentication features including Adobe IMS. I checked the logs and saw a nastygram: 15.09.2021 14:52:34.780 *WARN* [127.0.0.1 [1631731954777] GET /libs/granite/core/content/login.html HTTP/1.1] com.adobe.granite.metrics.knownerrors.impl.ErrorLoggingComponentFilter Exception in component: category=CUSTOMER_CODE, resourceType=granite/core/components/login, exceptionType=org.apache.sling.api.scripting.ScriptEvaluationException, errorId=CUSTOMER, resource=/libs/gr

Introduction to Experience Fragments by Pedromonjo Abstract If you come from the Adobe Experience Manager (AEM) world, I do not think this post is for you; you already know what I am going to explain. However, if you are working with other Adobe solutions or are just starting to learn AEM, I hope to give you an initial overview of what Experience Fragments (XF) are. Content Fragments To avoid confusion, I want to start with what XFs are not. If you have also heard the AEM concept of Content Fragments, you may be thinking that there is a connection between the two. After all, both have the word “fragments” in the name. While there are many differences between the two, to me, the main one is: Content Fragments are presentation-agnostic pieces of content; you need to format them according to the media to be shown to the final user. Experience Fragments are made of content and presentation to create an experience; you use them as they come. If this still does not give you enough informa

Architecting a Better Ecommerce Experience with Adobe Experience Manager’s Commerce Integration Framework by Adobetech Abstract The Commerce Integration Framework (CIF) is a powerful Adobe Experience Manager extension for building integrated and seamless content and e-commerce experiences for customers at every stage of their journey with your brand. In this second blog in our CIF series, we take a deeper dive into the framework architecture and integrations to help you use Adobe Experience Manager with your commerce solution. In this second installment of our Adobe Experience Manager Content and Commerce series, we’ll describe the functional building blocks of the Commerce Integration Framework (CIF) — a powerful extension for building integrated and seamless content and e-commerce experiences for customers at every stage of their journey with your brand. We’ll introduce you to the architecture and design principles of CIF and some of the integration options you have for using Adobe

AEM - Core Components Introduction by Adobe Docs Abstract In Adobe Experience Manager, components are the structural elements that constitute the content of the pages being authored. Components have always been a fundamental element of the AEM experience, making page creation simple but powerful for the author and the development of components flexible and extensible for the developer. The Core Components are a set of standardized Web Content Management (WCM) components for AEM to speed up development time and reduce maintenance cost of your websites. Features Production-Ready The Core Components are 28 robust components that are well tested, widely used, and that perform well. Cloud-Ready Whether on AEM as a Cloud Service, on Adobe Managed Services, or on-premise, they just work. Versatile The components represent generic concepts with which the authors can assemble nearly any layout. Configurable Template-level content policies define which features the page authors are allowed to

Top 6 AEM Best Practices for Delivering the Ultimate User Experience by exadel Abstract The Exadel Marketing Technology team has delivered a wide variety of projects using AEM. Despite the wide range of projects, we have identified some common areas of AEM on which effective project management and execution rests. These are: AEM architecture and design, AEM performance issues and scalability, AEM maintenance and support, AEM security, AEM customer experience and content strategy, and automation. Obviously, there is no easy fix for issues in any of these crucial areas, so improving the foundation of your AEM strategy may take time. AEM best practices for critical areas | AEM architecture and design Choosing the right storage architecture for your Adobe Experience Manager (AEM) deployment will help your system’s performance and reliability. The basic rule is that TarMK is designed for performance, while MongoMK is used for scalability. Develop a SOLID architecture. Compliance with SOLI

Sling model is only back-end business logic provider to AEM components.Adaptable are just a way to get respective sling object reference. For example if you need slingRequest object in sling model then make your sling model adaptable to HttpSlingServletRequest.You can not get a value from sling model in a servlet or in any other class.When you need a reference of an OSGI service, you have only one way, that is @ OSGiService annotation.You can export only JSON data thru sling model exporter.You can not extend one sling model into another sling model.Sling model can to be created outside of the designated package in AEM.One Interface can not be a Sling Model, whenever you need to create a Sling Model you will have to write a pure POJO concrete implemented java class.You can only read properties of a node thru sling model, you can not change a node property thru sling model.Constructor injection..! Nothing like that in sling model.More details can be found on below URLhttps://aemhelp

Content Type Title Feature Video  [Asset Essentials and Workfront] Configuring the Integration - Technical Video  Feature Video  [Asset Essentials] Managing Assets Essentials - Feature Video  Feature Video  [Asset Essentials] Creating Content using Assets Essentials - Feature Video  Feature Video  [Asset Essentials] Collaboration in Assets Essentials - Feature Video  Feature Video  [Asset Essentials] Creative Cloud and Assets Essentials - Feature Video  Feature Video  [Asset Essentials] Provisioning Assets Essentials - Feature Video  Feature Video  [Asset Essentials] Getting started with Assets Essentials - Feature Video  Feature Video  [Assets Essentials and Workfront] Sending Documents and Linking Assets - Feature Video  Feature Video  [Asset Essentials and Workfront] Maintaining Version History - Feature Video  Technical Video  [Asset Essentials and Workfront] Mappin

Sling model – Retrieving properties of child resources by Kiran Abstract In AEM, we fetch the values of multiple properties via java code and display them in HTL. Common Way of fetching the properties: Resource resource = resourceResolver.getResource(request.getParameter("resourcePath")); //Adapting the resource to a node resource.adaptTo(Node.class).getProperties(); //Adapting the resource to an asset resource.adaptTo(Asset.class).getMetadata(); //Adapting the resource to valuemap resource.adaptTo(ValueMap.class).get("propertyName", String.class); There are many other adapters available that we can adapt a resource with. You can check them here. Fetching the property values of a sub-resources becomes complex here. So, lets discuss a simpler way to resolve this problem. Create a new sling model: Let’s create a new model with the properties that we need from the child nodes. In the below example, the resource is an asset. @Model(adaptables = Resource.class, defaultInjectionStrate

I am using AEM 6.5.Existing behavior:I see that, en.model.json call is being mage on load which fetches all child pages and it's contents and subsequent navigation does not make model.json calls as everything is fetched in one shot.What I want to achieve?I want to fetch only the content of the current page and not the whole hierarchy. Is there any way to customize/configure this behavior. I want to have lazy load mechanism and fetch only the current page. And when page navigation links are clicked, I want to fire another model.json call and load the data and render the new content.Please help.

Designing your AEM Cloud Service Website with Core Components by one-inside Abstract Adobe brings a set of reusable and production-ready components for its content management system, AEM. Their name: The Adobe Core Components. Their purpose: Speeding up development time. But how do you take advantage of these Core Components to deliver a website fast? What is the best design approach, and how should the team members work together? If your company is using AEM or AEM Cloud Service and you are looking to fast-track the design process while following the best practices of AEM’s styling system, you came to the right place. Today, we are going to explain how to avoid a long design phase, and too much back and forth. AEM Styling process in a nutshell Let’s go through the styling process with Adobe Experience Manager. The process suits a new project with AEM Cloud Service. However, you could follow a similar design approach while working with an on-premise version of AEM. Indeed, t

AEM - Table of Content Component by Adobe Abstract Component that renders a table of content to help navigating the page content. The implementation of this feature is tracked by issue #1816. For discussing this spec, please use the discussion thread #1822. User Story As an author, I want to insert a table of content to my page, so that visitors can easily navigate to the titles that are within the page. Requirements Lists all H1-H6 elements that are rendered on the page, regardless of which component renders them (core title or teaser components, custom components, RTE, etc). Lists also those titles that are coming from the page template or from (nested) experience fragments. Links to the corresponding component on the page by using the id attribute that is set on the closest parent from the title element. Creates a nested list of the titles found on the page, rendering them either with UL/LI or OL/LI elements. Authoring capabilities: Capability to choose how to render the list (u

Call for feedback about the Table of Content component by Adobe Abstract Hi all, Adobe is going to pick up the development of a Table of Content component in the next days. The specs for that component have been published recently on the following wiki page: https://github.com/adobe/aem-core-wcm-components/wiki/Table-of-Content-Component If you have interest in such a component, please review the specs and provide us with feedback in this thread. The implementation will happen on the issue #1816. Read Full Blog Call for feedback about the Table of Content component Q&A Please use this thread to ask the related questions.

Adobe Named A Leader in Aragon Research Report on Workflow and Content Automation by Adobe Abstract Today, I’m proud to announce that Adobe is a leader yet again — this time in the 2018 Aragon Research Tech Spectrum for Workflow and Content Automation (WCA). We believe this recognition reflects the innovation and commitment from our combined Adobe Experience Cloud and Adobe Document Cloud teams. Aragon Research cited strong product capabilities, go-to-market execution, strategic vision, and integration between both Adobe Experience Manager Forms and Adobe Sign as some of the reasons for our leadership position. Adobe’s leadership in WCA comes on the heels of our impressive position as a named Leader in both the 2018 Aspire Leaderboard for Customer Communications Management and in Gartner’s Magic Quadrant for Web Content Management report, we’re back with another huge win. About workflow and content automation If you’re not familiar with the WCA category, it’s basically the process o

Adobe Announces Payment Services for Adobe Commerce by Adobe Abstract SAN JOSE, Calif.--(BUSINESS WIRE)-- Adobe (Nasdaq: ADBE) today announced the upcoming availability of Payment Services for Adobe Commerce, the industry’s leading end-to-end commerce application for B2B, D2C and hybrid use cases. By integrating Payment Services to their digital storefronts, Adobe merchants of all sizes will soon have access to a robust, secure, and integrated payment solution that can easily be managed from their Adobe Commerce Admin, instead of having to do the work of integrating with third-party payment providers. Payment Services for Adobe Commerce will be powered by the PayPal Commerce Platform and available to Adobe merchants by the end of the year. “In today’s fast-moving digital economy, organizations demand flexibility and extensibility in their commerce platform to sustain business growth and deliver seamless experiences for their customers,” said Amit Ahuja, vice president, Adobe Experien

Prioritize Search Results based on Boost in Lucene Index by Vijayalakshmi Abstract In Lucene Index, we have a property named boost of type Double which will help assign weightage to desired properties (that are part of fulltext/contains query) Properties with high boost value will be displayed earlier in the search results. Recently we had a query in the Community related to this subject to prioritize search term in URL to be first in the search results than the one found in properties like title/description. In AEM, URL/path to the resource is simply the node names. Node names are declared as property within the indexRules using special case identifier as :nodename and is already available OOTB in cqPageLucene(/oak:index/cqPageLucene) Prerequisite for fulltext/contains query : We should make sure that we have two other properties named nodeScopeIndex and analyzed set to true (Both are of type "Boolean") For Prioritizing : Set boost with higher value for desired property. In this ca

Our events team would love your feedback on attending our past events including Summit and MAX. Please take a few minutes out of your day to complete the below survey by Thursday, September 30. Your feedback is crucial in helping us to continue to reimagine the events and experiences we create for our customers. Thank you.   https://www.surveymonkey.com/r/DDSR9LJ

Hello everyone,  Can anyone from internal technical team let us know when Adobe public repo (https://repo.adobe.com/nexus/content/repositories/public) will he up for normal usage.  Thanks and regards, Shailesh 

Use this thread to ask any questions related to the Managing creative workflows using Workfront and Assets Essentials course on Experience League. Experts are monitoring this thread to ensure your questions are answered.