Product Communities

RTCDP is gearing up. Here is quick recap with links to access the webinars and rebuild your marketing strategy.   1. The Future of Data Management and The Changing Environment:  As market forces bring change to our digital landscape, businesses need to adapt to a new reality regarding data governance, identity resolution, and how to engage prospects and pseudonymous visitors with meaningful content. Checkout the webinar for same at link   2. A Tale of Two Perceptions: Brands vs. Consumers; Research is always enlightened with data backed to it. As marketers tire of the clutter of information dedicated to the topic, the results of this study will add a unique perspective – the consumer point of view. We will unveil the research results of this thought-provoking topic, uncovering whether brands and consumers are truly aligned in their perception of the looming disruption requiring the evolution of identity management. Checkout the webinar and detailed white paper of data a

If you have a zeal to solve problems, craft solutions, and are an expert on #AdobeExperienceManager with proficiency in core java concepts, We'd love to talk to you.Currently, open for #Bangalore and #Noida locations (INDIA).   Feel free to drop in your profiles using the link below:      Technical Product Consultant-AEM (myworkdayjobs.com)(Add source-Adobe.com)    

Hi All, I am trying to migrate the content from AEM6.0 (Oak 1.0.22) to AEM 6.5 (Oak 1.10.2). Here's what I did,install a fresh copy of AEM 6.5 (/apps/aem65/crx-quickstart/repository)get a copy of the current repository in version 6.0 (/apps/aem60/crx-quickstart/repository)Run the commandjava -Xmx4096m -jar crx2oak-1.8.10-all-in-one.jar segment-old:/apps/aem60/crx-quickstart/repository /apps/aem65/crx-quickstart/repository --datastore=/apps/aem65/crx-quickstart/repository/datastore > ~cms/aem-migration.txt &It was successful. The size is down from 62G to 54G, probably because of the different formats. Now trying to start up AEM 6.5 java -server -Xms1024m -Xmx2048m -XX:MetaspaceSize=512m -XX:MaxMetaspaceSize=2048m -Djavax.net.ssl.trustStore=/apps/aem65/crx-quickstart/ssl/trusted.keystore -Djava.awt.headless=true -Xverify:none -noverify -Dsling.run.modes=author,crx3,crx3tar -jar crx-quickstart/app/cq-quickstart-6.5.0-standalone-quickstart.jar start -c crx-quickstart

CCMS: Supercharge long-form content for personalized and consistent experiencesAdobe has partnered with Forrester to evaluate content creation, management, and delivery challenges faced by organizations and found that traditional content management systems do not meet their business needs. That is why organizations are increasingly adopting a structured content management approach via a component content management system (CCMS) to address these strategic and operational gaps.This thought leadership study explores how a CCMS can offer significant benefits, lower content-related risks and provide organizations an edge in driving higher content ROI through more effective content management. Download the study here.

Advantages of AEM Assets as a Cloud Service by James Talbot Abstract Adobe Experience Manager Assets as a Cloud Service offers a cloud-native solution to manage large scale assets and handle Dynamic Media operations. In this blog post, we will look at the advantages of AEM Assets as a Cloud Service, and how Asset Microservices plays a unique role and greatly helps with performance and speed. First off, both AEM Assets as a Cloud Service and Asset Microservices are always current with the latest features. Adobe provides a daily update of the AEM Assets Base Image as well as daily hotfix releases for both AEM Assets and Asset Microservices. In addition, AEM Assets as a Cloud Service provides a monthly release of new features, while Asset Microservices provides a weekly release of new features. The architecture of AEM Assets as a Cloud Service is uniquely designed to improve Asset handling performance. A client, such as a web browser, sends an upload request to Adobe Experience Manager

As part of the latest Campaign Standard Release 21.3 - September 2021, the Quarantine vs Denylist section has been updated with further clarification.    It has been clarified that quarantine and denylist do not apply to the same object and has also been detailed out which ones applies where and when. Check out here for more details:  Quarantine vs Denylist   Feel free to reach out through below comment section for your queries and feedback.

In classis UI Siteadmin shows all hierarchy of files whereas in touch UI aem sites we can see only pages but not other files. How Do I enable other files? @14414417 @smacdonald   

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

Authors: Pallavi Kotkar, Anuj Shah, Imtiaz Ahmed, and Liviu Cismaru Companies often run multiple digital experience applications in parallel and need to cater to the development, testing, and deployment of these applications while ensuring operational compliance. Adobe Experience Platform is built to enrich digital experience applications on a global scale. We built a sandbox infrastructure to meet our customer, developer, and partner needs. This blog details our approach, architectural highlights, and what’s next. Adobe Experience Platform helps brands to build customer trust and deliver better-personalized experiences by standardizing customer experience data and content across the enterprise, enabling an actionable, single view of the customer. Customer experience data can be enriched with intelligent capabilities and governed with robust data governance controls to use data responsibly while delivering personalized experiences. Experience Platform makes the data, content, and insi

Authors: Gautam P. Kowshik and Xabriel J. Collazo Mojica 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: Consistency Between Data & Metadata: We had all our metadata in a s

Authors: Andrei Ionescu (@Andrei_Ionescu), Shone Sadler (@shone_sadler), and Anil Malkani Customers use Adobe Experience Platform to centralize and standardize their data across the enterprise resulting in a 360-degree view of their data. In our earlier blog “Iceberg at Adobe”, we introduced our scale and consistency challenges and the need to move to apache Iceberg. Adobe Experience Platform is the infrastructure capable of processing exabytes of data ingested through either Streaming for low-latency use-cases or Batch where processing larger chunks of data efficiently are the concern. Prior to Iceberg, we had a problem with high-frequency small files being sent to Adobe Experience Platform for batch ingestion. We suffered from a textbook case known in the big data industry as the “Small File Problem.” We immediately saw problems with attempting to commit these small files to Iceberg tables at scale and needed a solution. This blog details that uphill battle focusing on the buffered

Authors: Filip Bocse (@fbocse), Gautam P. Kowshik, Costin Ochescu, and Shone Sadler (@shone_sadler) With the first blog of the Iceberg series, we have introduced Adobe’s scale and consistency challenges and the need to move to Apache Iceberg. 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. Although Iceberg is designed for slow-changing datasets our system operates in a high-throughput ingest environment. In the second blog, we have covered our challenges and the solutions we found to accommodate our ingestion throughput requirements. Read performance optimization was key to the usability of our platform. The third blog focused on how we have achieved read performance using Apache Iceberg and compared how Iceberg performed in the initial prototype vs. how it does today and walked through the optimizations we did to make it work for AEP. For every data manage

Authors: Jaemi Bremner (@Jaemi_Bremner), Romin Parekh, Shone Sadler (@shone_sadler), and Miao Wang. In our previous blogs, Iceberg At Adobe, Data ingestion with Buffered writes to Iceberg, and Optimized Reads With Iceberg we understood the benefits of Apache Iceberg and how it fits in the overall Adobe Experience Platform architecture. In this blog, we will share our story of migrating 1 PB+ datasets to Iceberg on Adobe Experience Platform Data Lake, the challenges we faced, and lessons learned. Adobe Experience Platform is an open system for driving real-time personalized experiences. Customers use it to centralize and standardize their data across the enterprise resulting in a 360-degree view of their data of interest. That view can then be used with intelligent services to drive experiences across multiple devices, run targeted campaigns, classify profiles and other entities into segments, and leverage advanced analytics. At the center of our Data Lake

Authors: Jaemi Bremner (@Jaemi_Bremner), Yaksh Sharma, Sumit Kumar M, and Nipun Nair (@nipunn49017381). This is a follow-up to our previous blog about public cloud cost management for Adobe Experience Platform Pipeline. The previous blog covered an overview of Adobe Experience Platform Pipeline, a breakdown of expenses, a plan of action, and the need for a cost governance program. We recognize that both technology vendors and our enterprise customers (CIOs and IT organizations) have been faced with public cloud cost management. Building upon that, we focused on defining a cost optimization framework that establishes an iterable approach with sustainable long-term impact. In this blog, we will share our progress on how we reduced annual public cloud COGS spend by 40% without incurring any downtime. Goals We began by defining the following goals which would serve as our guiding principles as well, to the cost savings approach. Rightsizing our public cloud infrastructure:

Hey there, budding Forms 2.0 JS developer! Do you really know how local <script> tags work?  ’Cuz you should.   Let’s examine the difference between snippet A: <script> // something you pasted from somewhere function ABC(){ alerb("Independent function ABC running"); } ABC(); // something you pasted from somewhere else or wrote from scratch function DEF(){ alert("Independent function DEF running"); } DEF(); </script>   And snippet B: <script> // something you pasted from somewhere function ABC(){ alerb("Independent function ABC running"); } ABC(); </script> <script> // something you pasted from somewhere else or wrote from scratch function DEF(){ alert("Independent function DEF running"); } DEF(); </script>   Yes, the typo in alerb is deliberate, and appears in both A and B. To save your eyesight: the only difference

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!

Make the most of the Adobe Certification exam sale! Certification exam vouchers are 50% off till September 21, 2021.     Visit the Adobe Certification Voucher Center to make your purchase and enter code Summer50 at checkout.     This sale ends next week on September 21, 2021. But your voucher will be valid for one year from the date of purchase, so you can buy a voucher if you anticipate taking the exam within a year.     Please note that this sale applies to Adobe Certified Expert, Professional, and Master certifications and renewal exams. (Marketo Certified Master and Adobe Sign and Qualified credentials are excluded from this promotion.)     For queries, please reach out through below comment section.

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