Adobe Experience Manager

How to start AEM in debug mode? by Rashidjorvee Abstract There are multiple approaches to start or tune AEM instance in debug mode. we will cover few of them in this tutorial. We coudl start AEM using the command pormt by using the below command line. java -jar aem63-author-p4502.jar -debug <port#> Another way to start tune AEM instance in debug mode is we could update the start.bat file and start AEM by clicking on the start.bat file in crx-quickstart folder. To do so we have to do the following. First we need to update the start file; go to \crx-quickstart\bin\start.bat and append this command "-debug -Xnoagent -Djava.compiler=NONE -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=<port#>" with line 25, default JVM options. Save the file Now double click on the start.bat file to start your AEM instance. @echo off :: This script configures the start information for this server. :: :: The following variables may be used to override the defaults. :: For one-time

Generate id for AEM components by Anirudh Sharma Abstract We all know that when we add an AEM component to a page, it creates the DOM structure on the pages based upon our HTL file. Sometimes we require id attribute to be set in our div for n number of reasons. If we put id attribute in the HTL file itself then it will become static and if in include that component multiple times on the page, the same id will be repeated for all instance; which is not a neat solution. Wouldn't it be nice if we have a mechanism to generate an id randomly and uniquely for each instance of the component on the page? In this post, we are going to do just that. Hence, without further ado, let's get started - Step #1 Create a component that will have the field for unique id. We are making this id editable as well to give more flexibility to the content authors. Below is the cq:dialog.xml file -

Workflows in AEM 04 - MetaDataMap by Abstract 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 example Let's see a code example to demonstrate this concept. Here we will be using two process steps. In the first, we will be passing data and in the second, we will be retrieving it. FirstProcessStep.java package org.redquark.demo.core.workflows; im

Bundle is NOT whitelisted in AEM by Rashidjorvee Abstract While using the loginAdministrative() method of SlingRepository class you might see an error "Bundle is not whitelisted". To get this method work we have to whitelist the bundle in OSGi configuration "Apache Sling Login Admin Whitelist" this helps us to defines which bundles can use SlingRepository.loginAdministrative(). Below is the code snippet of creating session using loginAdministartive method. @Reference private SlingRepository repository Session session = repository.loginAdministrative(null); Read Full Blog Bundle is NOT whitelisted in AEM Q&A Please use this thread to ask the related questions.

AEM Proxy Component Pattern and Component Versioning by Suryakand Abstract Most organization want to keep content and user experience flexible so that they can innovate and deliver new experiences/features faster. Flexibility allows organizations to reuse what has been built already and keep adding new features and functionalities on top of it. One of the key characteristics of flexibility is backward compatibility and non-breaking changes. This flexibility comes with a clear definition of a strategy for content creation and user experience. In this article we are going to look at 2 very simple but powerful component development strategies that organization (specifically technical teams) can adopt to win the flexibility game and stay ahead in competition of delivering rich user experience. Let’s start with a scenario/problem statement. Assume that a large banking organization has business in multiple countries. The organization is using AEM and MSM (Multi Site Manager) to manage

AEM Experience Manager(AEM): Content Sharing Approaches by Albinsblog Abstract In most cases, we need to share the CMS content with external systems to support the Omni channel's headless experiences or other use cases to support content sharing. In this post, let us see the options available to share the AEM content with external systems. GRAPH QL: The graph QL API shares the content fragments to enable the headless content experience with the external system. The structured data can be managed through Content Fragments in AEM and shared through Graph QL API to support the omnichannel experiences. The latest AEM 6.5 and AEM as a Clod Services versions support Graph QL API; the Graph QL API currently supports only exposing content fragments externally, not for the regular page content. Refer to the following URL for more details on using Graph QL to API to share content fragments with external systems — https://medium.com/tech-learnings/how-to-deliver-headless-content-through-graph

hello,I have created a content fragment model and when i click the json view i am getting this error.AEM version 6.5.12 nosample-contentwhile inspecting console errors areSame model is working in my local only difference I observe is my local is having sample content but above is not

Hi, I have a requirement , where my job consumer would start a Sling job, I have to wait till that finishes so that the necessary files are present in the correct state (This is a prewritten job) . then the consumer can move forward with it other functions.How can I do so? What will be the correct way to approach this?The correct flow is ratherwe get an api call, we move that api call to a consumer, wait for the sling job to create the files, then process the initial api call. 

I've tried by going to /apps/dam/gui/coral/components/commons/fileupload/clientlibs/fileupload/js/fileupload.js but the issue is it gets applied to all assets in general. But I want to add separate rules for PDF, and separate one for images.Tried in the following manner: 

Hello Community.First time here 🙂We have a requirement in which we need to clear dispatcher cache without publishing the page. We tried flush service options but it is not working for us. Looking for solution options to achieve this.Thank you

 In assets UI we have added few custom columns in list view. when we select on any article and then click on export metadata it will export those columns of that article into csv. so we are not able to get the custom columns added into csv.Here are the list of columns in list view.  Here are the list of columns in the exported csv So, its showing only few columns in the exported csv. we want all the custom columns to be added into that csv and also remove unwanted columns while exporting.

Hi,I am facing the problem below.I have a workflow to publish a content on a specific node when it is updated.On the other hand, I have an action on my bundle that has to be executed when this content is activated.I am following this tutorial below. but my class is not been called when workflow is completed. I realized that this class is using some deprecated method.Adobe CQ Help | Creating Replication Event Handlers for Adobe Experience Manager Has someone implemented this on AEM6.4? If so, is there a most current tutorial?My class does not have errors, but does is not working as well.I appreciate any help.Thanks in advance.

AEM Security Best Practices: Awakening to the Need for Better CybersecurityAdobe Experience Manager takes security seriously since Adobe, at large,  is more than aware just how much is at stake. The average cost of a data breach amounts to $4.24 million according to a 2021 IBM report. AEM security best practices are woven into AEM software so that teams can prevent, quickly detect, and eliminate even the slightest deviations.In this article, you’ll learn what contributes to the overall Adobe AEM security, determine what cyber threats any CMS such as AEM can face, and uncover Adobe security best practices.  Placing emphasis on AEM security best practicesAdobe Experience Manager has established partnerships with software development companies, leading researchers, and security research institutions to keep up with the latest vulnerabilities and cyber threats. To put a few on your radar, Adobe collaborates with:Information Systems Security Association (ISSA)Open Web Application

Running junit in the latest Eclipse (Eclipse IDE for Enterprise Java and Web Developers, version 2022-03 (4.23.0)) fails to adaptTo resource, instead it returns null.Same test in the same workspace just in older Eclispe (Eclipse IDE for Enterprise Java Developers, 2019-03 (4.11.0)) executes test with no problem. final SmallCarousel actual = ctx.request().adaptTo(SmallCarousel.class);"actual" ends up to be null after execution of this line... When debugging in older Eclipse I could see that MockAdapterManagerImpl.getAdapter returns factory for SmallCarousel in a call to, final Map<String, List<AdapterFactoryDescriptor>> factories = getAdapterFactories(adaptable.getClass()); Same Map in new Eclipse doesn't contain factory for SmallCarousel. Thanks

Personalization using AEM Experience Fragments and Adobe Target by Adobe Abstract With the ability to export AEM Experience Fragments into Adobe Target as HTML offers, you can combine the ease-of-use and power of AEM with powerful Automated Intelligence (AI) and Machine Learning (ML) capabilities in Target to test and personalize experiences at scale. AEM brings together all of your content and assets in a central location to fuel your personalization strategy. AEM lets you easily create content for desktops, tablets, and mobile devices in one location without writing code. There is no need to create pages for every device—AEM automatically adjusts each experience using your content. Target lets you deliver personalized experiences at scale based on a combination of rules-based and AI-driven machine learning approaches that incorporate behavioral, contextual, and offline variables. With Target, you can easily set up and run A/B and Multivariate (MVT) activities to determine the best

Possible OSGi Bundle States in AEM by Joey Smith Abstract OSGi is one of the core technologies that Adobe Experience Manager (AEM) is built on. While it is certainly well-documented, a lot of developers have never taken the time to understand the ins and outs of what lies “under the hood” of OSGi for your AEM environment. You don’t have to be an expert in OSGi to be an expert AEM developer or systems engineer. That said, there are times when it can be helpful to understand specific aspects of OSGi. I like to think of it as the difference between knowing how to change your own oil and knowing how to rebuild your own engine; having that deeper degree of understanding can be a powerful tool when things aren’t working how you would normally expect them to. One of the common things you will come across as a developer is the need to understand the state of a bundle. These states describe specific phases of the bundle as it progresses in AEM. Below are the six states that a bundle can h

Extending Page Properties in AEM by Mayur Satav Abstract It is always one of the prime requirements for the projects to extend page properties. It helps to manage metadata and many other functionalities associated with the page.In this blog we will see how to extend page properties. Step1: Open CrxDe and go to your project package. Then select the page component node. You will see sling:resourceSuperType property copy the path associated with that property. This property points to the v2 version of the core page component. Extending Page Properties in AEM By Mayur Satav Step 2: Now paste that core page component path in the node search bar and do not forget to add /apps/ before /core/. Otherwise, it will not navigate you to that component. The complete path should look like this. /apps/core/wcm/components/page/v2/page You can refer below image for clarity. Extending Page Properties in AEM Now if you click on the page component node you will see the sling:resourceSuperType property

AEM Author, Publish & Dispatcher by Sankham MarTech Channel Abstract Video: https://youtu.be/aMMLqryokEo What is AEM Author, Publish & Dispatcher is explained in this video. Also how to debug any issue which we might get in Production instance is also explained. AEM Tutorial PlayList: https://www.youtube.com/playlist?list... 00:00 - Introduction 00:43 - Code Build Process 04:24 - Author to Publish Flow 06:48 - Replication Agents 10:54 - Page Render Flow 15:01 - Apache Rewrite Rules 16:26 - AEM Dispatcher 21:24 - AEM Issue Debugging 14:36 - Page & Templates Summary Read Full Blog AEM Author, Publish & Dispatcher Q&A Please use this thread to ask the related questions.

AEM and Magento Integration Using Commerce Integration Framework(CIF) — Local Setup (Part1) by Albin Issac Abstract The AEM and Magento are integrated using the Commerce Integration Framework (CIF); the CIF framework enables AEM to access magneto commerce instances through GraphQL API. In this post series, let us see how to set up local Magento and AEM platforms and enable the CIF framework in AEM to integrate with Magento to build the storefront in AEM. Let us start with setting up a local Magento instance. I am going to use XAMPP on windows to enable the Magento servers. Install Elastic search: The latest Magento version requires Elasticsearch or OpenSearch for indexing but not support MySQL indexing. Installed elastic search 7.17.3, https://artifacts.elastic.co/downloads/elasticsearch/elasticsearch-7.17.3-windows-x86_64.zip Download and Install XAMPP: As a first step, download and install the XAMPP server, including Apache, PHP, MySQL, and PHP admin. Read Full Blog AEM and

How to Implement Experience Targeting in AEM using ContextHub? by Albin Issac Abstract Content personalization in short means delivering the right content to the right person in real-time. Simple experience targeting scenario, user1 requesting the content through Firefox receives Experience A and user2 requesting the content through Chrome receives Experience B. The experience can be decided based on different rules e.g gender, age location, etc, here we are seeing the simple scenario. The targeting engine is the mechanism that drives the logic for targeted content. You can use either AEM or Adobe Target as the targeting engine, AEM provides a built-in targeting engine that processes page requests and determines the content to display. AEM as a targeting engine only supports Experience Targeting but Adobe Target should be used for A/B testing. In this post, let us see how to use the AEM targeting engine to enable the experience targeting for a web page. Setup ContextHub: ContextHu

Hello All,     We have a requirement, when we upload a pdf(say abc.pdf) to /content/dam/media/ folder, then some custom workflow we developed, creates a structure under /content/dam/media as follows./content/dam/media/<random-unique-name>/1.0/<random-unique-name.pdf>But the moment we drop any asset to /content/dam/* folder, DAM update Asset Workflow triggers and start creating renditions for /content/dam/media/abc.pdf, but by the time it completes, asset is moved to /content/dam/media/<random-unique-name>/1.0/<random-unique-name.pdf> by custom workflow,  So DAM Update Asset workflow is throwing below exceptions.30.08.2018 06:33:23.429 *ERROR* [JobHandler: /etc/workflow/instances/server0/2018-08-29_1/update_asset_118:/content/dam/media/abc.pdf/jcr:content/renditions/original] com.day.cq.dam.core.impl.RenditionMakerImpl Error while generating renditions for asset /content/dam/media/abc.pdfjavax.jcr.InvalidItemStateException: OakState0001: Unresolved conflicts in /

【目的】アセットの「プロパティ」を開き、「参照」を選択するとアセットの参照元のページ(ローカル参照)を一覧できます。AEM外部でこの情報を使用したい場合などには、JSON形式でエクスポートして使用することができます。 【環境】AEM as a Cloud Service、AEM 6.5 【対応方法】次のURL[1]にアクセスするとJSON形式で結果が取得できます。出力結果に含まれるpathの値から参照元のコンテンツパスが確認できます。 [1] http://localhost:4502/bin/wcm/references.json?path=<対象のアセットへのパス>  使用例:http://localhost:4502/bin/wcm/references.json?path=/content/dam/wknd/en/activities/hiking/equipment_6.jpg  JSON出力例: {    pages:         [            {                srcPath: "/content/dam/wknd/en/activities/hiking/equipment_6.jpg",                srcTitle: "equipment_6.jpg",                path: "/content/wknd/language-masters/en/adventures/riverside-camping-australia",   &nbs

【問題/事象】サイトコンソール(http://localhost:4502/sites.html)では見えないページが、CRXDE Liteではリポジトリにノードとして存在し、そのノードにdeletedプロパティとdeletedByプロパティがついていることがあります。本記事では、この事象について原因と対応方法を説明します。 【環境】AEM as a Cloud Service、AEM 6.5 【対応方法】管理者ユーザーのインボックスでRequest for Deletionワークフローの通知を探し、Deactivates the pageステップとRequest for Deletionステップをそれぞれ完了にします。 【原因】公開権限のないユーザーがページを削除すると、そのページはサイトコンソールで非表示になり、Request for Deletionワークフローが始まります。次の流れのとおり、ワークフローが完了するまでページのノードはリポジトリに残っています。　1. 公開権限のないユーザーがページを削除　2. そのページはサイトコンソールで非表示になる (ページのdeletedプロパティとdeletedByプロパティが付与される)　3. Request for Deletionワークフローが始まる　4. 管理者ユーザーのインボックスにワークフロー通知が届く　5. 管理者ユーザーがワークフローステップを完了にする　6. 実際にページのノードが削除される ＜留意事項＞・上記は以下記事の抄訳/翻訳となります。KB記事タイトル(英語). The page to be deleted is hidden but remains in the repository , April 22, 2022, https://experienceleague.adobe.com/docs/experience-cloud-kcs/kbarticles/KA-19240.html, (参照 2022-04-25).・本記事にいただいたコメントへの返信はお約束できません。あらかじめご了承ください。

Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.6:npm (npm dependency build) on project wcax-core.ui.apps: Failed to run task: 'npm run build' failed. org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1] 1.I had installed the latest version of Node JS but getting the above error on maven build.Could anyone please help me resolve this issue.

I am trying to set the OAuth 2.0 flow for server to server communication. I am able to do the steps outlined here https://medium.com/tech-learnings/how-to-manage-the-protected-aem-resources-through-oauth-2-0-851ce4c7a5ef up until the point of getting the token back form AEM. Using the token on the next request always gives a 404 response. I have tested the manual flow to authorize the user and the JWT method as well with the same results. User is part of administrators group (just while I'm testing) so permissions are good and the scope has all permissions for /content/dam.