Adobe Experience Manager Sites

What to Look for When Extending Magento With Custom Code or an Extension by bounteous Abstract One of the strengths of the Magento platform is its flexibility and scalability. Customization is common and can be accomplished a few different ways—through community-developed extensions from the Magento Marketplace, or by building your own custom modules. The Magento Marketplace allows you to add new features and themes easily, while a custom module approach might be needed to actualize a unique vision. Many merchants also pursue a hybrid approach, by customizing pre-built extensions to save time and money. Understanding the benefits of each approach empowers you to make the right decision when looking to extend the out-of-the-box capabilities of your store. Magento Installation There are several points to think about when considering adding a new extension or custom feature to a Magento installation. The upfront cost can potentially be dwarfed by maintenance and development efforts sol

Adobe Managed Services vs. Self-Hosting AEM - Pros & Cons by jetteroheller Abstract “Where should I host AEM? Should I keep it in our datacenter, or put it in the cloud, or perhaps at a dedicated hosting provider? And Adobe really is pushing me to use Adobe Managed Services to host my Experience Manager install. Are they any good?” Being the centerpiece of the most complicated pieces of marketing infrastructure in the world, Adobe Experience Manager can be a real challenge to architect, deploy, and integrate. Everyone’s got a solution to pitch to you. “Everyone should go to the Cloud!” “Run it in containers!” “Let Adobe manage it for you!” However, with these folks each proclaiming that their solution is a one-size-fits-all, it’s important to consider the most fundamental decision you’ll make in setting up Adobe Experience Manager: Do I buy a license from Adobe and then host AEM myself (either on-premise or in the cloud), or do I sign a contract with Adobe Managed Services and h

Rebuilding the Sling Launchpad in AEM by jetteroheller Abstract Sometimes, while running an AEM system, you’ll one into one of a whole host of error conditions which doesn’t seem to have any decent explanation. A few of them are: 1. On restarting AEM, some bundles come up in the “INSTALLED” state, but won’t start properly, automatically. 2. After a deployment, upgrade, service pack release or cumulative fix pack release, AEM fails to start properly on one server, yet it works on another seemingly-identical one. 3. Changing an OSGI configuration in the Felix console doesn’t take effect – you make the change in, say, /system/console/slinglog, but still don’t see the log you just configured. 4. Other random class-loading issues, where on some servers (deployed the same way) all of the bundles start, but on one server it refuses to start at all. If you’ve tried the usual suspects and still are left scratching your head, one go-to troubleshooting step I’ve taken (quite often in fact) is

Blue-Green Deployment on Adobe Experience Manager by jetteroheller Abstract How do you execute an AEM deployment with absolute minimal risk of disrupting your public website visitors, while also minimizing downtime or outage windows that you have to give to your content authors? Like most AEM Dev/Ops guys, I’ve probably spent more time obsessing over the best way to execute an AEM release than anything else in my AEM/CQ career. The blog post I first wrote for Rackspace, and that I’ve now continually been adding to, attempting to visualize the perfect AEM release process, is now up to over 4400 words. But now, I’ll add to that with this – an overview on doing blue-green deployment on AEM. Read Full Blog Blue-Green Deployment on Adobe Experience Manager Q&A Please use this thread to ask the related questions.

Hello All,we have an issue with translation project1.            We had submitted a project for translation and its received at the translation service provider2.            Translator process the page adding in translated content and marks the status a delivered at their portal.3.            We access the AEM project which fires the event handlers behind the scene to import the translated file as part of which the launch node should be updated with translated content.4.            The import does not happen and we see the below error which points to access permission.Has anyone come across such issue, its more likely a permission issue wherein AEM tries to update the project status with next stage and it fails to do so.  *ERROR* [10.68.15.84 [1486489033334] POST /content/projects/20170207/feb-07-test_de_/jcr:content/dashboard/gadgets/translationjob HTTP/1.1] com.adobe.cq.wcm.translation.impl.servlet.TranslationJobUpdateServlet Error while taking action javax.jcr.AccessDeniedException:

We have a component ( we are creating component using dialog.xml file ) . Component fields look in below format  General Category 1General Category 2......General Category 20Each category should have 15 Labels per each ( In screenshot added only 2 labels )General Category 1 -> Label1 ,Lable12 .....Labe115.......CRX structure look below format for the component fields  categorylabels               category1 -> label1,label2.....label15               category2 -> label1,label2.....label15                .......               category20 -> label1,label2...label15 After entering the data and submit on component , In UI data looks in the below formatThe values are showing continuously. We want to show data  in below format General Category1  Label1 = General Category1 labe

Using AEM 6.4 service pack 7 . We have a component ( we are creating component using dialog.xml file ) .Created new tab "Labels"  We have content structure  General Category 1General Category 2......General Category 20Each category should have 15 Labels per each ( In screenshot added only 2 labels )General Category 1 -> Label1 ,Lable12 .....Labe115.......Now we need CRX structure should look like below format  categorylabels               category1 -> label1,label2.....label15               category2 -> label1,label2.....label15                .......               category15 -> label1,label2...label15 These are the country specific labels (these values translated later) Example:If we retrieve Label    categorylabels/category1/label1 Suppose If we are in US page , thi

Re-usable Color Select in Touch UI Dialogs w/ ACS Common’s Generic Lists by sourcedcode Abstract While working on AEM component’s Touch UI dialogues, in particular, with colors, there are many cases where developers will need to configure the same color options over and over again. We catch ourselves repeating code, which becomes uneasy to maintain changes to the color options. What happens when there is a new color option? Going through many files include a new color option is not that efficient. In this article, we will be putting together a centralized configuration for color options that can be used by any Touch UI configuration throughout our AEM project utilizing the ACS Common’s Generic Lists. This tutorial will assume that you have your IDE opened, so you can copy and paste code to test. What is ACS Commons Generic Lists? Generic Lists are a feature allowing easy creation and management of lists of title/value pairs. This configuration can be used as a data source for Touch

Creating Custom Workflow Step by aem.design Abstract When writing custom workflow services, you may find yourself not seeing your service being recognised by the Process Step. You will first encounter this when you don’t see your service appear in the process list on the dialog. And once you verify the data source that feeds that dropdown at http://localhost:4502/libs/cq/workflow/content/console/process.json you will wonder why. You may also see errors like this Could not find service for service reference {YOUR WORKFLOW STEP CLASS PATH} with label {no label} that could just tell you your class is missing property process.label. Now that you know, you add this property to your class and your class appear in the list, here is an example of how to add it: @Component( immediate = true, service = WorkflowProcess.class, property = { "process.label=Content Fragment Page Generator" } ) Also while debugging this, you may find some other errors polluting your docker logs. The activate metho

I wrote part 4 of my "Integration testing with AEM" series, which covers how easy it can be to validate your dispatcher setting, for example to check if the initial redirect is working correctly or if the "infinity" selector is correctly blocked for JSON requests. https://cqdump.wordpress.com/2021/01/18/writing-integration-tests-for-aem-part-4/

Deploying a Project to AEM as a Cloud Service Using Cloud Manager and GitHub Desktop by Adobe Tech Blog Abstract Cloud Manager is an important part of AEM as a Cloud Service. It allows you to build, test and deploy applications to both the Author and Publish Services. The user interface enables you to easily access and manage the cloud environment and CI/CD pipeline for Experience Manager applications. Using the user interface, you can configure and kick off the CI/CD pipeline. In addition, a through code scan is executed to ensure that only high quality applications pass through to the production environment. In this blog post, you will explore how to deploy a project in an external GIT to AEM as a Cloud Service using GitHub desktop which avoids having to use the command line for GIT. Prerequisites 1. A provisioned AEM Cloud Program 2. Access to the Cloud Manager Git Repository 3. GitHub Desktop Clone the WKND Site from the Adobe Git 1. Launch GitHub Desktop. 2. Go to File > Cl

Writing integration tests for AEM (part 4) by Jörg Hoh Abstract In the last post I mentioned that the URL provided to our integration tests allows us to test our dispatcher rules as well, a kind of “unit testing” the dispatcher setup. That’s what we do now. As a first step we need to create a new RequestValidationClient, because we need to customize the underlying HTTP client, so it does not automatically follow HTTP redirects; otherwise it would be impossible for us to test redirects. And while we are on it, we want to customize the user-agent header as well, so it’s easier to spot the requests we do during the ingration tests. The way to customize the underlying HTTP client is documented, but a bit clumsy. But besides that this RequestValidationClient is not different from the SlingClient it’s derived from. Maybe we change that later. The actual integration tests are in PublishRedirectsIT. Here I use this RequestValidationClient to perform unauthenticated requests (as end-users ty

Refactoring Complex AEM Components and Pursuing Better Code Practices with AEM Authoring Toolkit, Part I by exadel.com Abstract Have you ever had a “Swiss Army Knife” component in your AEM project? Something that has many modes of behavior and many settings and is enmeshed in the current business logic? We bet you have, because we have dealt with this kind of component several times. A Swiss Army Knife can be anything, like a component that exposes individual products in a catalog in which product expositions differ from each other. It can also be a view of data that comes from different sources, each of which has a unique set up. Maybe your Swiss Army Knife is a component that has to support different adjustable layouts (like “show me these tiles as a grid, or a carousel, or a mosaic”) while working with the same data source. No one builds a Swiss Army Knife from scratch (that would pretty clearly be against AEM best coding practices). Your component will start with a pretty compact

AEM Cloud Service - Validate asset file extensions while uploading to AEM in browser by Sreekanth Choudry Nalabotu Abstract Goal The following steps explain adding a client side script to validate the file types while uploading to AEM using browser.. Solution 1) Create a project eaem-cs-validate-assets using archetype - https://github.com/adobe/aem-project-archetype mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=24 -D aemVersion=cloud -D appTitle="Experience AEM Validate Assets on Upload" -D appId="eaem-cs-validate-assets" -D groupId="apps.experienceaem.assets" -D frontendModule=none -D includeExamples=n -D includeDispatcherConfig=n 2) Create node /apps/eaem-cs-validate-assets/clientlibs/supported-file-types of type cq:ClientLibraryFolder, add String[] property categories with value [dam.gui.coral.fileupload], String[] property dependencies with value eaem.lodash. 3) Create file (nt:file) /apps/eaem-cs-va

Hi,We have developed two interactive XDP which have some pre-population and binding of data and they are generated in interactive PDF. Whenever we deploy the XDP in our ETE environment everything is perfect and works fine. We have developed a rest API which generate the PDF and bind values from front end. The problem is whenever we deploy the XDP in QA environment and try to consume and bind dynamic values to XDP and generate the same PDF documents consuming the same rest API we get failure in generating the documents. I check the error logs of AEM instance and I am getting below. Please can somebody help me out here as we are not able to find what is the root cause of this failure specific to QA Environment.09.07.2019 16:53:13.307 *ERROR* [10.52.160.35 [1562683992994] POST /content/AemFormsSamples/renderpdfform.html HTTP/1.1] com.adobe.fd.readerextensions.service.impl.ReaderExtensionsServiceImpl AEM-REX-001-008: Unable to apply the requested usage rights to the given document.java.lan

Hey guys, Recently I have started seeing that, AEM author starts throwing JS error and doesnt load any component. Starts happening after a few deployments. Needs a restart to bring it back to normal. Screenshot attached. Anyone else facing this issue?

Taking Query Optimizations to the Next Level with Iceberg by Gautam P. Kowshik and Xabriel J. Collazo Mojica Abstract This blog is the third post of a series on Apache Iceberg at Adobe. In the first blog we gave an overview of the Adobe Experience Platform architecture. We showed how data flows through the Adobe Experience Platform, how the data’s schema is laid out, and also some of the unique challenges that it poses. We also discussed the basics of Apache Iceberg and what makes it a viable solution for our platform. Iceberg today is our de-facto data format for all datasets in our data lake. We covered issues with ingestion throughput in the previous blog in this series. We will now focus on achieving read performance using Apache Iceberg and compare how Iceberg performed in the initial prototype vs. how it does today and walk through the optimizations we did to make it work for AEP. Here are some of the challenges we faced, from a read perspective, before Iceberg: 1. Consistency

Pablo Calvo Completes AEM Sites Business Practitioner Certification by Peter Nash Abstract There’s always lots of good stuff happening at Hoodoo Digital. We are pleased to announce that Pablo Calvo has completed the Adobe Certified Expert exam for the Adobe Experience Manager Sites Business Practitioner. This exam certifies that he “has proven knowledge and experience to help clients optimize the value of their Adobe solution.” Adobe provides an exam guide that outlines the things that an Architect should be proficient with in order to pass the exam. The minimally-qualified AEM Business Practitioner should be able to perform the following tasks without any assistance: 1. Understand the capabilities provided by out-of-the-box components available in AEM (what can and cannot be done), and when customer development is needed 2. Use the AEM Content Management Systems (CMS) 3. Use AEM to manage Digital Assets 4. Use Experience Fragments 5. Understand and participate in workflows 6. Analyze

Unit Testing JCR Resource Resolver Mappings by Juan Ayala Abstract Recently, I had a task to shorten URLs and remove the HTML extension in AEM. On top of that, I had to add a context root to the URLs so that these mappings would happen. 1. /content/myapp/en_US.html -> /mycontext/ 2. /content/myapp/en_US/homepage.html -> /mycontext/homepage/ 3. /content/myapp/es_ES.html -> /mycontext/es_ES/ 4. /content/myapp/es_ES/homepage.html -> /mycontext/es_ES/homepage/ Shorting URLs in AEM consists of two things: 1. The dispatcher will receive requests for short extension-less URLs and must rewrite them before passing them through to the publishers. 2. The links within the HTML markup rendered by AEM must be rewritten to their short extension-less versions. Setting up Apache is straight forward. You need to inspect the incoming request and translate it to its long version before sending it on to AEM. What I had trouble with was configuring the Sling mappings to rewrite URLs. There ar

AEM WCM Components - Angular Core implementation by @61380/aem-core-components-angular-base Abstract This module provides a Angular implementation for the AEM core components. This enables you to use the core components: -In the AEM SPA editor with Angular -Or in any other Angular context, provided you have the input needed to instantiate the components. Current supported / exported components: 1. Page Authoring 2. Button (V1) 3. Download (V1) 4. Image (V2) 5. List (V2) 6. Separator (V1) 7. Teaser (V1) 8. Text (V2) 9. Title (V2) Layout 1. BreadCrumb (V2) 2. Language Navigation (V1) 3. Navigation (V1) Abstraction 1. AbstractCoreComponent 2. CoreComponentModel (interface) Containers For the containers (Accordion,Tabs,Carousel,Container) we do not provide any implementation in this project. It does not make sense to provide it for web-components as you can leverage the normal Core Components implementation such as a Tab Container, and drag your web components in there. Instead we pro

AEM WCM Components - Spa editor - Angular Core implementation by @61380/aem-core-components-angular-spa Abstract This module provides a Angular implementation for the containers in the AEM core components. This only works with the AEM SPA editor. Current supported / exported components: 1. Containers 2. Accordion (V1) 3. Carousel (V1) 4. Container (V1) 5. Tabs (V1) Abstraction 1. AbstractCoreContainerComponent Usage You can choose to import the entire library at once OR import components individually. The latter is useful if you want to only enable a few components and you want to save your javascript footprint. Also, if you want to load all core components, but you want to lazyload them with angular suspense, you will need to import them individually. Read Full Blog AEM WCM Components - Spa editor - Angular Core implementation Q&A Please use this thread to ask the related questions.

Nested Multi-Field by Kiran Vedantam Abstract In AEM, Nested Multi-Field is every developer’s nightmare🤦‍♂. In this blog we will discuss how to easily access the nested multi-filed values from the dialog and show them in HTL. Below, I would add the code of each module which follows all the latest coding techniques [like R7 annotations, HTL etc.] and will explain them it in detail. You can simply re-use the code in your requirement. Lets begin the show..😎✌ Dialog: The dialog is a nested multi-field dialog. There are two multi-fields here: FirstMF & SecoundMF. Read Full Blog Nested Multi-Field Q&A Please use this thread to ask the related questions.

Hi Community   We want to send a big thank you to everyone who participated in the AEM community in 2020 and helped others with their problems. Each year, Experience Cloud Community honors the member who goes above and beyond in service and provides incredible support to others with the Community Member of the Year award.   Recognizing the efforts in a public manner, here we announce  @vanegi [Internal Adobe Member] and @arunpatidar  [External Adobe Member] the Community member of the year 2020.   Arun Patidar Statistics: Avg. Time spent: 15 mins 47 sec His Activates in AEM community can be seen here: https://experienceleaguecommunities.adobe.com/t5/user/viewprofilepage/user-id/6786635 He is a top community member for the last 3 quarters He is also MVP of our community What Arun says about the community: "AEM Community is always helpful to interact with new people and learn from their experience and contribu

Unit Testing JCR Resource Resolver Mappings by Perficient Abstract Recently, I had a task to shorten URLs and remove the HTML extension in AEM. On top of that, I had to add a context root to the URLs so that these mappings would happen. 1. /content/myapp/en_US.html -> /mycontext/ 2. /content/myapp/en_US/homepage.html -> /mycontext/homepage/ 3. /content/myapp/es_ES.html -> /mycontext/es_ES/ 4. /content/myapp/es_ES/homepage.html -> /mycontext/es_ES/homepage/ Shorting URLs in AEM consists of two things: 1. The dispatcher will receive requests for short extension-less URLs and must rewrite them before passing them through to the publishers. 2. The links within the HTML markup rendered by AEM must be rewritten to their short extension-less versions. Setting up Apache is straight forward. You need to inspect the incoming request and translate it to its long version before sending it on to AEM. What I had trouble with was configuring the Sling mappings to rewrite URLs. There ar

Sing Models - an ongoing debate by Divanshu Goyal Abstract Sling models are been there for long years when we talk about Adobe Experience Manager, but undoubtedly it had always been the developer's dilemma. Whether to use them all the time or it should be utilized only for utmost need? We always talk around the model while accessing values from JCR and we always have our opinion that when we can directly use ${properties. title} to access it. Why use the sling model for that? Even for the simple component, is it not an overhead? Can't we use HTL to express the logical implementation for the component rendering? To answer these questions following points you may agree with, It's been a time since everyone now knows the coined term "content-as-a-service" which means exposing the content as a JSON so that anything that is built on top of the CMS can consume the content without exposing any separate endpoint. Taking this point into consideration if we don't have a sling model, we may