Product Communities

The LINE channel has been enhanced with improvements that include: Support for LINE video message Support for LINE Partner Registration API Support retry of message sending in the event of LINE server-side error or network timeout To learn more, check out this detailed documentation: Sending LINE Messages Please note that LINE is only available for on-premise or managed services installations.   In case you have any questions, please feel free to post them below or reach out through the community Q and A section. In case you have any ideas and/or suggestions regarding the Campaign product, then kindly submit them here. 

Fact Sheet on AEM as a Cloud Service by Hemalatha Chockalingam Abstract AEM as a Cloud Service [AEMAACS] Powered by Microsoft Azure cloud (AWS is in the future roadmap) Released on January 13, 2020 Latest update - AEMAACS 2021.5.0 on May 27, 2021 Next upcoming update - AEMAACS 2021.5.0 on June 24, 2021 Built-in CDN - Fastly CDN Identity Management for Author Tier - Adobe IMS and Adobe Admin Console Recommended Implementation Approach : Adobe Digital Foundation Blueprint Release Model - Blue Green Deployment. It also allows for zero downtime upgrades and provides fast rollbacks. The old version of the application (blue) runs at the same time as the new version of the application(green). Deployment Architecture - Adobe Cloud Manager with built in CI/CD functionality AEM Project Maven Archetype - 24 or later Deployable artifacts in AEMAACS - all.zip including ui.apps, ui.config & ui.content Environments available in AEMAACS: Production, Stage & Development Local Devel

Content Package Type Validation Forces Rethink of Standard Project Structure for Adobe Experience Manager by Mark Adamcin, Principal Architect Abstract With the launch of Adobe Experience Manager (AEM) as a Cloud Service, Adobe has redefined the way content, code, and configurations are stored in AEM. The changes create a more explicitly structured project with strict enforcement, which translates to how AEM projects are set up and deployed. Let’s dive into the before and after pictures of that change, as well as providing reasoning for the changes in order to effectively deploy AEM as a Cloud Service. Prehistoric FileVault For about a decade, 2009 to the beginning of 2019, we built and deployed CQ5/AEM content packages like this, where question marks, dashed lines, and cloudy boundaries indicate areas of ambiguity, non-determinism, and opportunities to become more proficient with the Felix Admin Console: Diagram showing how CQ5/AEM content packages were built and deployed from 2009

Nail Your New Ranking from Google’s Core Web Vitals by Webinar Abstract Customer relationships, acquisition, and revenue. Did you need another reason to make sure your digital experience has the best performance possible? Google is releasing a new reason, along with a deadline of August 2021, when the rollout of Core Web Vitals is complete. Core Web Vitals are becoming part of Google's ranking criteria and if you're not prepared, can lead to demoted page rankings, reduced traffic and revenue. Good news: Dynamic Media and Dynamic Media Classic have the tools you need to dramatically improve page load times - one of the key web vitals. Join Adobe’s Bridget Roman and Mark Dean as they explain Core Web Vitals, what it means to brands, and what to do next. In this webinar, you’ll learn: How Core Web Vitals is changing Google’s rankings Actions you can take to promote your brand How to optimize the performance intelligence built into Dynamic Media and Dynamic Media Classic Please regis

We have two below login-based site. Lets say siteA & siteBand an we use SAML to authenticate with our Azure AD.These two sites working perfectly when we hit the URL independently.Actually siteB url is used in one of link in siteA. Once we hit the siteA url it does the sso and landing the page correctly. If we click on the siteB link then it opens in a new-window and does the sso and landed with broken css. if we refresh the page then it loads the page correctly. We have two SAML configurations configured and used for these below two sites./content/siteA/content/siteB Even we tried with two certalias created in Trust Store and used in SAML config that too didn't help.What could cause the issue. Thanks in advance.

We can not add any component on segment page, the parsys does not have + button to add component and drag and drop is also not working. Tried to create a segment with new configuration and also with we.retail config, facing the same problem on both.Note - we have not overlay any component, it is just plain Vennila Instance + SP 8Segmentation page screen shotEven experience fragment also have the same problem, no + plus button and drag and drop is also not working.Experience fragment page screen shotError log -25.06.2020 18:07:21.218 *WARN* [0:0:0:0:0:0:0:1 [1593088641140] GET /editor.html/conf/we-retail/settings/wcm/segments/test123.html HTTP/1.1] org.apache.sling.caconfig.resource.impl.def.DefaultConfigurationResourceResolvingStrategy Ignoring reference to /conf/we-retail/settings from /conf/we-retail/settings - Probably misconfigured as it ends with '/settings' The we-retail config shipped with aem and I dont see any misconfiguraion. The interesting thing is we have tried the sa

On launching the AEM local setup I am getting error on author  HTTP ERROR 500Problem accessing /sites.html/content/we-retail/language-masters. Reason: Server Error Caused by:java.lang.NullPointerException: Cannot invoke "org.apache.sling.jcr.resource.internal.helper.jcr.JcrProviderStateFactory.createProviderState(java.util.Map)" because "this.stateFactory" is null at org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.authenticate(JcrResourceProvider.java:304) at org.apache.sling.jcr.resource.internal.helper.jcr.JcrResourceProvider.authenticate(JcrResourceProvider.java:76) at org.apache.sling.resourceresolver.impl.providers.stateful.ProviderManager.authenticate(ProviderManager.java:161) at org.apache.sling.resourceresolver.impl.providers.stateful.ProviderManager.getOrCreateProvider(ProviderManager.java:87) at org.apache.sling.resourceresolver.impl.providers.stateful.ProviderManager.authenticateAll(ProviderManager.java:129) at org.apache.sl

If you have not yet migrated to the new Workfront experience, I invite you to join us tomorrow for an interactive networking session where you can ask questions of Workfront experts AND hear about an example migration from a customer who has been in your shoes. Register here. You'll hear and be able to discuss: Guidance from the Workfront Customer Success team on what they have seen work bestInland Empire Health Plan's journey with their own transition, from pre-planning to roll-out, and lessons learned along the way.Available resources, including videos, guides and pre-built templatesAnd much more.We'll leave plenty of time for group discussion for you to share questions, concerns and ideas about your own migration. Please note: This call is 90-minutes and is different from a traditional webinar. Be prepared to turn on your video, come off mute and join an active conversation. Workfront Virtual User GroupTransitioning to the New Workfront ExperienceTuesday, June 22, 20219

When accessing Journey Optimizer for the first time, you are provisioned a production sandbox and allocated a certain number of IPs depending on your contract. To be able to create your journeys and send messages, you need to go though the configuration steps listed in this documentation: Get started with Journey Optimizer Configuration   Please feel free to reach out for your queries through the Community Q&A or below comment section. If you have any feedback or feature requests for the Adobe Journey Optimizer product, then submit them here.

The Transactional Messaging section has been reorganized and clarified with a new Get started section: Get started with transactional messaging , along with a Transactional Messaging Operating Principle section, that includes an enhanced schema for a better understanding of the process.   In case you have any questions, please feel free to post them below or reach out through the community Q and A section. In case you have any ideas and/or suggestions regarding the Campaign product, then kindly submit them here. 

Has anyone had a similar problem? Please tell me how to solve it.AEM 6.5 *ERROR* [10.243.254.107 [1623402348266] GET /etc/clientcontext/default/content/jcr:content/stores.init.js HTTP/1.1] libs.cq.personalization.components.clientcontextdesigner.parsys.init$js$jsp error while including a init file /etc/clientcontext/default/content/jcr:content/stores/cart org.apache.sling.api.scripting.ScriptEvaluationException: javax.servlet.ServletException: java.lang.LinkageError: loader constraint violation for class

DRY way of using RichText Granite UI Component in AEM for Static Templates by Sourced Code Abstract Every developer have experienced a situation where they are working with AEM multiple AEM components, where Touch UI dialogues consist of a common richtext Granite UI component configuration cq/gui/components/authoring/dialog/richtext. When I mention common richtext Granite UI component, I mean there are multiple AEM components that will have the richtext Granite UI component as one of it’s input fields, where only the “links*” and “format*” richtext features are enabled, as an example. Enabling only the “links*” and “format*” richtext features, we catch ourselves repeating lines of code by copying and pasting the entire block of code for all of our Touch UI dialogues that require the richtext requirement. This works, but this is Write Everything Twice, “WET” code, and it’s not good implementation; this can be improved. What happens if there is a new requirement where the authors would

How Does S3 works with AEM ? by Rules of AEM - Abstract How Does S3 works with AEM ? Accommodating a huge amount of assets in any content management platform is challenging. Adobe Experience Manager offers an integration with the Amazon S3 storage solution, allowing binary data for images, documents and videos to be stored in an S3 bucket. Amazon S3 is highly performant and offers nearly infinite storage capacity. When talking about terabyte storage, performance is everything. The choices made during the planning and architecting phase can literally make or break the performance of a CMS system and the websites running on it. Adobe Experience Manager offers a number of storage methods, each offering a different way of storing data. Each of these options has its strengths and weaknesses. In AEM storage the mechanisms are called Micro Kernels, or MK for short. In this article we will look at the AEM with S3 data store. There are two ways in which AEM can be set up with Amazon S3 sto

OSGI and Servlet Container by Blog TechInnovia: Adobe AEM Developmen... Abstract Welcome to part 8, in this final part we will review Servlets & Filters in OSGI environment. More precisely we will look at only one case, Sling Servlets & Filters in AEM. After reading this article, you should be able to 1. Create a Sling Servlet. 2. Create a Sling Filter. 3. Invoke a service from Servlet using reference. 4. Be able to use this Servlet Resolver Page. Let me remind you that Sling is a REST based web framework build on top of OSGI. Content-driven that means the framework first finds the content render then determines how to render it basing on the request. It supports multiple programming languages for rendering scripts. In this part we will concentrate on Sling Servlets & Filters. We will not discuss rendering pages & Components. Read Full Blog OSGI and Servlet Container Q&A Please use this thread to ask the related questions.

Adobe PDF Extract: API Output Demystified by Adobe Tech Blog Abstract Video: https://youtu.be/oIG6U_dDHII Since PDF’s invention, getting text out of a PDF file, in the correct reading order, from any PDF, including tabular data, has been a challenge. Even the best tools on the market were only good at one part of the problem or the other. Developers had to cobble together multiple tools depending on the type of PDF they had and the kind of data they needed to get out of it. The result was, they needed to know way too much about the PDF file before they knew which tool to use. A single API to extract the text to a usable form regardless of the actual content of the PDF simply didn’t exist. One of the main reasons that PDF can be difficult for computers to read is that there are many poor PDF renderers and engines out there. While the PDFs that these engines create might create an output that can be visually read, they often were not well-structured for computers to easily understand

The future of Adobe's developer experience by Digitalum Abstract Digital transformation is everywhere. In Covid times, entire businesses had to pivot in weeks, if not days. What used to be considered convenience features, became critical services. Developers were there to rally for the cause, to virtually connect family, friends, coworkers and businesses; keep workers employed and business afloat. To support developers with this accelerated pressure, the developer experience organization, or DevX for short, was formed within Adobe with this ambitious aspiration: empower and support the world’s best Customer Experience Management (CXM) community, ecosystem and platform. DevX in the Adobe Experience Cloud The Adobe Experience Cloud (AEC) began as a series of acquisitions. Who amongst us recognizes some of the old pre-acquisition names like Day Software, Neolane, Omniture, Satellite or Livefyre? The need for a more seamless integration was apparent and much has changed since the ol

Cloud Manager timeout by rashid jorvee blog Abstract Cloud Manager timeout While using the cloud manager to build and deploy the code on Adobe Experience Manager (AEM), the default waiting time at a step is 7 days. If we left the pipeline waiting at any step for more than 7 days then the pipeline automatically gets failed. Read Full Blog Cloud Manager timeout Q&A Please use this thread to ask the related questions.

Migrating to Apache Iceberg at Adobe Experience Platform by Stories by Jaemi Bremner on Medium Abstract 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 Architecture is the unde

Massive Data Processing in Adobe Experience Platform Using DeltaLake by Adobe Tech Blog Abstract In this blog post, we are going to go over how the data lake house architecture at Adobe Experience Platform combines with the Real-time Customer Profile architecture to increase our Apache Spark Batch workload throughputs and reduce costs while maintaining functionality. Adobe Experience Platform enables you to drive coordinated, consistent, and relevant experiences for your customers no matter where or when they interact with your brand. With Adobe Experience Platform Real-time Customer Profile, you can see a holistic view of each individual customer that combines data from multiple channels, including online, offline, CRM, and third-party data. It allows you to consolidate your disparate customer data into a unified view offering an actionable, timestamped account of every customer interaction. Architecture Overview Given that the Adobe Experience Platform assimilates data from variou

  Lab Details Learn about Predictive Audiences, Trait Recommendations and how to leverage these Adobe AI-driven features to achieve your business goals. Discover how to classify unknown audiences into Personas using AI. Discover how to surface similar audiences in Segment Builder to expand segments. Use intelligent recommendations in Audience Marketplace to uncover third-party data opportunities.  Summit LAB Schedule Wednesday, April 01 | 01:30 PM - 03:00 PM Thursday, April 02 | 09:00 AM - 10:30 AM Speaker(s) Liron Goren Snai, Product Manager, Adobe Matt Kapilevich, Senior Architect, Data Science, Adobe Session Length 1h 30m Catalog Link L798 - Embrace the Power of Data Science in Adobe Audience Manager   Q&A Please use this thread to ask the question related to this lab. Don't forget to register yourself for the LAB using the catalog link above. Seats are limited!!

https://www.linkedin.com/pulse/fact-sheet-aem-cloud-service-hemalatha-chockalingam  

.content.xml files are not visible in Eclipse project explorer by rashid jorvee blog Abstract While working in Eclipse with Adobe Experience Manager (AEM) code, .content.xml file which is the content file of node structure is not visible in Eclipse project explorer. This is happening because of the filtration of the file in the project explorer. To view the .content.xml or any other hidden file which starts with .[dot], remove the following filter from project explorer. Open Eclipse >> open project explorer >> click on view option >> Filters and Customization Read Full Blog .content.xml files are not visible in Eclipse project explorer Q&A Please use this thread to ask the related questions.

Hi Guys , I wrote this article years back to setup the dispatcher in local environment.It can be helpful for people who are new in AEM and want to explore caching . https://www.linkedin.com/pulse/dispatcher-setup-local-enviornment-varun-shakya/

 Hi ,when i upload the some of the pdf or docx in to the dam , title is taking complete name of the file with extension in aem 6.5 and some of the pdf taking complete file name with docx extention. Please help where is the issue. Thank you

Hello, Is here any way to add item under Page Information tab? Thank you,Keehwan