Adobe Experience Manager Sites

I see all my static templates while creating experience fragment. Checked the property cq:allowedTemplates on /content/experience-fragments, it contains /libs/cq/experience-fragments/components/experiencefragment/template/libs/settings/screens/experience-fragments/templates/experience-fragment-template-screens/conf/we-retail-screens/settings/wcm/templates/experience-fragment-screens-variation/conf/we-retail/settings/wcm/templates/experience-fragment(.*)? Only conf and libs templates should be shown while creating template as per the above config but I am seeing all the static template that resides inside /apps folder. Basically I would want to stop showing static templates that resides on /apps folder. Is there any other config to make this happen?

AEM - Installing Dispatcher by Adobe Docs Abstract Dispatcher versions are independent of AEM. You may have been redirected to this page if you followed a link to the Dispatcher documentation that is embedded in the documentation for a previous version of AEM. Use the Dispatcher Release Notes page to obtain the latest Dispatcher installation file for your operating system and web server. Dispatcher release numbers are independent of the Adobe Experience Manager release numbers and are compatible with Adobe Experience Manager 6.x, 5.x and Adobe CQ 5.x releases. The following file naming convention is used: dispatcher---. For example, the dispatcher-apache2.4-linux-x86_64-ssl-4.3.1.tar.gz file contains Dispatcher version 4.3.1 for an Apache 2.4 web server that runs on Linux i686 and is packaged using the tar format. Read Full Blog AEM - Installing Dispatcher Q&A Please use this thread to ask the related questions.

Understand Content Fragments and Experience Fragments by Adobe Docs Abstract Adobe Experience Manager's Content Fragments and Experience Fragments may seem similar on the surface, but each play key roles in different use cases. Learn how Content Fragments and Experience Fragments are similar, different, and when and how to use each. Content Fragments (CF) 1. Re-usable, presentation-agnostic content , composed of structured data elements (text, dates, references, etc.) 2. Content-centric | Defined by a structured, form-based, data model | Design and layout agnostic.| The channel owns the presentation of the Content Fragment’s content (layout and design) 3. Implemented as a dam:Asset | Defined by a Content Fragment Model Experience Fragments (XF) 1. A re-usable, composite of one or more AEM Components defining content and presentation that forms an experience which makes sense on its own 2. Presentation-centric| Defined by unstructured composition of AEM Components | Defines design an

SPA Editor Overview by Adobe Docs Abstract Single page applications (SPAs) can offer compelling experiences for website users. Developers want to be able to build sites using SPA frameworks and authors want to seamlessly edit content within AEM for a site built using such frameworks. The SPA Editor offers a comprehensive solution for supporting SPAs within AEM. This page gives an overview of how SPA support is structured in AEM, how the SPA Editor works, and how the SPA framework and AEM keep in synch. Introduction Sites built using common SPA frameworks such as React and Angular load their content via dynamic JSON and do not provide the HTML structure that is necessary for the AEM Page Editor to be able to place edit controls. To enable the editing of SPAs within AEM, a mapping between the JSON output of the SPA and the content model in the AEM repository is needed to save changes to the content. SPA support in AEM introduces a thin JS layer that interacts with the SPA JS code whe

AEM - HTL Use-API by Adobe Docs Abstract HTL encourages separation of concerns by not allowing business logic to mix with markup. Business logic can be implemented through the Use-API. The following table gives an overview of the advantages and disadvantages of each API. For page components, it is recommended to use a mixed model, where all model logic is located in Java, providing clear APIs that are agnostic to anything that happens in the view (i.e. within the components). AEM comes with great default models like the Page or the Resource API that should be able to cover most cases. All view logic that is specific to a component should be placed within that component as JavaScript, because it belongs to that component. Java Use-API 1. Faster | Can be inspected with a debugger | Easy to unit-test 2. Cannot be modified by front-end developers JavaScript Use-API 1. Can be modified by front-end developers| Is located within the component, keeping the view logic of a component close t

AEM Core Concepts by Adobe Docs Abstract Java Content Repository The Java Content Repository (JCR) standard, JSR 283 , specifies a vendor-independent and implementation-independent way to access content bi-directionally on a granular level within a content repository. Specification lead is held by Adobe Research (Switzerland) AG. The JCR API 2.0 package, javax.jcr.* is used for the direct access and manipulation of repository content. Experience Server (CRX) and Jackrabbit The Experience Server provides the Experience Services which AEM is built on, and which can be leveraged to build custom applications, and it embeds the Content Repository based on Jackrabbit. Apache Jackrabbit is an open source, fully conforming, implementation of the JCR API 2.0. Sling Request Processing Introduction to Sling AEM is built using Sling , a Web application framework based on REST principles that provides easy development of content-oriented applications. Sling uses a JCR repository, such as Apache

Today I published the followup on my topic "cluster ware coding for AEM", with the focus on what to change when you migrate your existing AEM application (in most cases without an explicit support for clustering) to AEM as a Cloud Service.And the best: It doesn't hurt if you follow these recommendations while you are still on AEM 6.4/6.5. It doesn't have any drawbacks or performance impacts. Part 1: General recommendations & scheduled jobs: https://cqdump.wordpress.com/2020/08/14/cluster-aware-coding-in-aem/Part 2: Long running sessions and clustering: https://cqdump.wordpress.com/2020/08/24/long-running-sessions-and-clustering/

Hello everyone, Meet our new talented Adobe Experience League MVPs from AEM Community. Congratulations and a big thank you for your contributions to the Adobe Experience Manager Community.     @chitramadan   @nupur_jain @shashi_mulugu  @vijayalakshmi_s  @arpitvarshney  @vaibhavi_j    Your profiles are now LIVE on MVP showcase page

Day 14 - AEM Workflows (Part III) by Red Quark Abstract Howdy fellow devs 👋! In the previous two posts, we learned about basics of AEM workflows and examples of Process and Participant steps. In this post, we will cover few other concepts that a programmer usually deals with. MetaData Map Sometimes we are faced with a situation where we need to pass data from one workflow step to the another. AEM’s workflow API provides an easy way to achieve this using MetaDataMap. Please note that only primitive data types like Integer, String etc. can be passed from one step to the another. If you have a requirement to pass non-primitive data then use the byte[] array. Caution: If the data to be passed is too large, refrain passing InputStream. Instead, a better approach is to save the data in a JCR node in the step and retrieve it from the JCR node in a later step. A MetaDataMap is the data structure which acts as a value map and allows users to set and get data among the steps. Code

Colorful Multifields in AEM by AEM Solutions Abstract Multifield is one of the most interesting and useful AEM feature, but when when we create nested multifield it becomes difficult for authors to segregate between parent and child fields and causes unnecessary confusion. We can add custom classes at dialog level to make multifields more readable. Steps to follow : 1. Create clientlibs folder at the component level and add css file. 2. Add the required classes in headerDialog.css. Add class for parent block .group{ background-color: antiquewhite } Add class for child block .item{ background-color: aliceblue } 3. Add group class at the multifield field. 4. Add item class at the child multifield field. 5. After adding multi fields in dialog we will get proper segregation. Hope this helps!! Happy Coding 🙏 Read Full Blog Colorful Multifields in AEM Q&A Please use this thread to ask the related questions.

Hi,we are developing - with AEM 6.3 - some custom Sightly authoring components, which integrate some vue.js code. When adding content under a parsys (foundation/components/parsys/new) and parsys/new, the markup is decorated (?) with <cq> elements.  So if we add a content item (in our case a 'card') by dragging it into the parsys, in preview mode we then end up with markup similar to the outline below.  I can see how the first 2 divs are drawn: there is the authored content and the markup rendered by new.jsp under parsys.jsp. What then adds the following 2 <cq> sibling elements?  I want to know so that I can figure out how to hide them in preview mode where a <cq data-config="..."> value somehow ends up with invalid json values (paths with missing forward slashes seems to be the symptom (possibly due to vue.js processing)) which then breaks the javascript run from /libs/cq/gui/components/authoring/editors/clientlibs/core.js.<!-- snippets --><div class="card se

Hi All, We have functionality where we have button to download pdf file, one click of the button, it sends request to back-end service and receive PDF steam and download pdf. Now the issue, is, When we try to download it from IE browser, .pdf extension is not getting added to the downloaded file where as the file is downloaded with .pdf extension from other browsers like Chrome, Firefox and Edge. Any inputs why it behaves differently on IE browser? Is something we have to allow at dispatcher level? Please advise.  Thanks In AdvanceSiva 

Hi, I am just exploring on Jcr Package Manager. I tried methods listPackages() and listPackages(WorkspaceFilter). The non-parameterised method listPackages() works fine but listPackages(WorkspaceFilter) is always returning empty list. PFB the code snippets i have tried and share your thoughts. Thanks in advance !! Approach 1DefaultWorkspaceFilter workspaceFilter = new DefaultWorkspaceFilter();String[] packageFilters = new String[] {PAGE1_PATH, PAGE2_PATH};for (PathFilterSet packageFilter : packageFilters) {workspaceFilter.add(packageFilter);}List<JcrPackage> pkgs = jcrPackageManager.listPackages(workspaceFilter); // This returns [] Approach 2JcrPackage jcrPackage = jcrPackageManager.create(rootNode, pkgName);JcrPackageDefinition jcrPackageDefinition = jcrPackageManager.create(rootNode, pkgName);DefaultWorkspaceFilter workspaceFilter = new DefaultWorkspaceFilter();String[] packageFilters = new String[] {PAGE1_PATH, PAGE2_PATH};for (PathFilte

Bounteous Harnesses the Power of Digital Asset Management for Commerce by Connecting Magento Commerce and Adobe Experience Manager Assets by bounteous Abstract Chicago—August 20, 2020—Bounteous, a leading insights-driven digital experience agency, today announced the creation of the Bounteous Connector for Magento Commerce and Adobe Experience Manager Assets. Working with Adobe, Bounteous built the connector to streamline processes and build a unified workflow allowing customers additional resources and time to focus on revenue-driving initiatives. Developed by Bounteous in collaboration with Adobe, the connector provides a seamless workflow between Magento Commerce stores and Adobe Experience Manager Assets giving Magento Commerce merchants advanced digital asset management capabilities. It provides a way to accelerate the process by synchronizing product images to Experience Manager Assets and substituting image rendering used by the Commerce Cloud Integration Framework connector o

Connecting Magento Commerce and Adobe Experience Manager to Enhance Enterprise Digital Asset Management by bounteous Abstract Optimize and streamline product media asset management with the Bounteous Connector for Magento Commerce and Adobe Experience Manager Assets. By replacing Magento Commerce’s native files storage with Adobe Experience Manager (AEM) Assets experience the marketing power and simplicity of the industry’s leading Digital Asset Management (DAM) system without having to leave the Magento Commerce interface. Magento Commerce is a fantastic platform for enabling merchants to manage large inventories of complex products, process thousands of orders, and accommodate customers of all interests with ease. AEM allows marketers to quickly find and edit the assets they need, confirm that they have the right versions, and easily share them across teams and channels. Using AEM Assets with Magento Commerce speeds content creation for commerce by providing seamless workflows for

Get to know the Adobe Experience Manager Dispatcher by Bruce Lefebvre Abstract Are you familiar with the concept of a re-fetching Dispatcher flush? Do you understand the implications of setting up an ignoreUrlParams allow list, vs. a block list? Have you ever gone live with a site that had a statfileslevel configuration set to 0? The Dispatcher is a critical component of a secure, stable, fault-tolerant and lightning fast AEM implementation. Unfortunately, it is often an afterthought, and its large array of configurations can be overwhelming and easily misunderstood. Our team would like to change this. As technical folks ourselves, we learn best when we’re able to experiment with new tech in a safe (read: not production) environment. This is why we’ve created the AEM 6.5 Dispatcher Experiments open source repository on GitHub: 👉 https://github.com/adobe/aem-dispatcher-experiments The goal of this repository is simple: demonstrate the impact of the Dispatcher and its config

WHY ADOBE EXPERIENCE MANAGER IS THE MODERN BRAND’S BEST ASSET by Ziffity Abstract Marketing has changed dramatically over the past five years. In the early days of ecommerce, competing by price and product selection was enough to win a customer’s loyalty. But with a plethora of choices, customers are demanding more. Specifically, they want personalized experiences wherever and whenever they interact with your brand. There’s data to back this up. According to the 2020 Gladly Customer Expectations Report, 79% of consumers say “personalized service” is more important to them than “personalized marketing” (read: retargeting). What’s worse, only 36% of consumers say brands make them feel like unique individuals. Most importantly, 84% of consumers say they’ll go out of their way to shop with a brand that provides them with great experiences. So how do you go about creating unique and enthralling customer experiences? Here are five questions the Ziffity teams are asked frequently. I can b

AEM VS OTHER CMSES – 6 FACTORS THAT MAKE AEM MORE PREFERABLE FOR ENTERPRISE-GRADE ECOMMERCE BRANDS by Ziffity Abstract Today’s tech-savvy customers reach you through various means, yet the core message of engagement needs to remain authentic & consistent, no matter what the channel is. Your website acts as the heart and soul of your organization. By leveraging a reliable CMS, you can manage content in a more accessible way to render on any channel, put your competitors behind, and pave the way for fantastic customer experience ascendancy. In this blog post, let us peek through the factors that make Adobe Experience Manager (AEM) the preferred CMS among enterprise users. Before probing into the details, let’s have a quick recall about Adobe Experience Manager (AEM) and its modules. WHAT IS ADOBE EXPERIENCE MANAGER (AEM)? AEM is a Content Management System (CMS) which allows effortless and dynamic digital asset management with document management solutions, engagement options, com

 Abstract:We might encounter several issues while writing Test class. This post explains theMost common issues with example scenario.Ways of creating Test content and ResourceResolverTypes of AemContext from io.wcm framework.Blog Content :https://myaemlearnings.blogspot.com/2020/08/unit-testing-in-aem-debugging-issues-in.html

AEM 6550 - Move Render Condition for Assets with References by Sreekanth Choudry Nalabotu Abstract A sample render condition to show Move action bar button in Asset console only if one (or some) of the assets in a folder have references (say they are part of a Dynamic Media Image Set) 1) Overlay /libs/dam/gui/content/assets/jcr:content/actions/selection/moveasset/granite:rendercondition into /apps/dam/gui/content/assets/jcr:content/actions/selection/moveasset/granite:rendercondition 2) Set /apps/dam/gui/content/assets/jcr:content/actions/selection/moveasset/granite:rendercondition@sling:resourceType to /apps/eaem-move-references-rendercondition 3) Create the Render condition /apps/eaem-move-references-rendercondition/eaem-move-references-rendercondition.jsp with following code <%@page session="false" import="com.adobe.granite.ui.components.ComponentHelper, com.adobe.granite.ui.components.Config, org.apache.sling.api.resource.Resource, org.apache.sling.api.resource.ValueMap, com

Unit testing in AEM - Debugging issues in Test class by AEM Learnings Abstract This post is for illustrating the possible errors/exception we get while writing Test class. Also highlights the possible ways of creating Test content and the ResourceResolverType available for creating AemContext (from io.wcm framework) Test content : Most important aspect of Unit Testing is creating Test content which in AEM sense is to provide a means of repository at the time of code build phase to test our Java code (written interacting with repo) For creating the same, we already saw that there are 3 possible APIs - Content Loader, Content Builder and Resource Builder available. Most often we use Content Loader making use of JSON file at class path and loading it to dummy content path. Below are the sample snippet making use of other two APIs. Content Builder : private final AemContext aemContext = new AemContext(ResourceResolverType.JCR_MOCK); ContentBuilder contentBuilder = aemContext.create(); W

How Adobe Experience Platform Predictive Audiences improves Personalized Experiences by Adobe Tech Blog - Jaemi Bremner Abstract Predictive Audiences was born out of a Garage Week project by the authors of this blog. Once a year, for one week, Adobe grants engineers complete freedom to work on an idea that interests them. Some of the most innovative ideas across Adobe’s Digital Experience business unit were born out of Garage Week projects, such as ours. When we started, we knew that our customers were spending a lot of time manually creating segments to deliver relevant experiences for the personas they had in mind. We also acknowledged that in many cases, they had a very small window to engage with their users and offer them a meaningful personalized experience, since many anonymous third-party cookies have a lifespan of just one session. We aimed to help our customers by leveraging Machine Learning and creating a system that would allow them to offer effective on-click personaliz

Integrate AEM & Target for Personalization with Project App Builder by Adobe Tech Blog - Santosh Mishra Abstract Every organization whether big or small understands the importance of personalizing the digital experience of their customers. According to Monetate, “Personalization Marketers see an average increase of 20% in sales when using personalized experiences” and “59% of customers say that personalization influences their shopping decision”. These are just some of the many statistics that you’ll find that show the great amount of value personalization efforts have for organisations. There is a lot that goes into creating personalized experiences for users but these experiences can only be effective if they’re leveraged appropriately. Two such solutions that help you create and optimize personalized customer experiences are Adobe Experience Manager (AEM) and Adobe Target (AT). The integration between these two solutions allows marketers to serve relevant experiences acr

AEM 6550 - Modify the Filename on Upload Before Executing DAM Update Asset Workflow by Sreekanth Choudry Nalabotu Abstract Adjust the filename on upload (organization standards?), before executing DAM Update Asset workflow. The sample in this post adds a filter executing prior to com.day.cq.dam.core.impl.servlet.CreateAssetServlet, intercepting the file upload stream Code in this post was not production harnessed, make sure you test (and improve it) for large files, small files, binaries, text files etc.. Add a filter eg. apps.experienceaem.assets.EAEMChangeFileNameFilter intercepting the file name stream and adjust the name (here it replaces spaces with hyphens) package apps.experienceaem.assets; import org.apache.commons.io.IOUtils; import org.apache.commons.lang3.ArrayUtils; import org.apache.commons.lang3.StringUtils; import org.osgi.service.component.annotations.Component; import org.osgi.framework.Constants; import org.apache.sling.api.SlingHttpServletRequest; import org.apa

Why a good business consultant can save you more money than a good AEM architect by Jörg Hoh Abstract In the years working in the consulting business for Adobe I joined many projects. Some only temporary to support on some special issues, others in a broader context; but always it was with a focus on the technology, on implementation, architecture and infrastructure. And with this background, I always tried to help my customers and projects and use the AEM (or CQ5) technology in the right way; to spend their money wisely and cost-effective. But: according to my own standards I often failed to do so. Not because I did not know the product. Not because the customer was not listening to me. And not because I was not able to give advice. But because I was not sitting at the right table when some important decisions were made. Because I was sitting with infrastructure teams to build a hardware sizing. I was working with customers architects to understand the constraints under which we ha