Product Communities

Experience Makers Live - 2021 by Adobe Abstract AUGUST 31–SEPTEMBER 1, 2021 A free virtual event Get ready for growth From inspiring celebrity keynotes to real-world case studies and practical advice, Experience Makers Live will help you kick-start your personal and professional growth. Join Adobe and a global community of Experience Makers for two days of learning, networking, and live Q&As. Read Full Blog Experience Makers Live - 2021 Q&A Please use this thread to ask the related questions.

Harmonizing work and asset management with Adobe Experience Manager Assets Essentials and Workfront by Purnima Rachoor Roy Abstract As companies accelerate to digital, they are seeing an increase in customer expectations for richer, personalized customer experiences. This requires companies to rethink their work and digital asset management processes and capabilities needed to deliver consistent and relevant content quickly. In an attempt to support this new way of working, companies inadvertently create a digital work crisis where functions and teams are disconnected, content is stale, inaccessible and trapped in silos, and work processes are analog. Instead of being empowered, employees end up wasting a lot of time on clumsy processes and searching for information. Read Full Blog Harmonizing work and asset management with Adobe Experience Manager Assets Essentials and Workfront Q&A Please use this thread to ask the related questions.

ADOBE EXPERIENCE MANAGER - WHAT IS IT? by HENRIK FELD-JAKOBSEN Abstract Adobe Experience Manager functions as a Content Management System (CMS), a Digital Asset Management (DAM) system, a Cloud Service, and much more with extensive integrations across the Adobe Experience Cloud. Adobe Experience Manager (AEM) is the solution to content complexity. As companies increase in size, they must control and optimise digital media across numerous sites and channels. In an ever-changing world, companies in both B2B and B2C commerce need to keep their marketing materials relevant to produce an omnichannel and personalised experience. For example, a Harvard study found that 73% of shoppers engage with brands across multiple channels, and omnichannel shoppers spend 4% more than shoppers completing their purchasing journey through a single channel. AEM will help you overcome the challenges of creating an omnichannel experience. WHAT IS ADOBE EXPERIENCE MANAGER (AEM)? Adobe Experience Manager (AEM

HOW AEM STREAMLINES MULTI-CHANNEL CONTENT MANAGEMENT by PJ UTSI Abstract We live in a multi-channel world, and in 2021, no one deals with just one eCommerce channel. Even the simplest digital businesses will likely connect with their customers through social media as well as their traditional sales channel. Some businesses are savvy with social media and email newsletters or employ multiple avenues of engagement for their employees and customers via mobile apps. Some retail outlets take advantage of digital signage or multiple marketing based channels. With these different touchpoints in play, content in different formats, sizes, and styles adds up. Naturally, managing this diverse content across all of these channels can get really complex, really fast. Yet, this is not a 'nice-to-have' initiative—it is imperative as it directly relates to an optimized digital customer experience. According to research from PWC, 90% of consumers expect consistent interactions across multiple channe

A Simple Example of Sling Pipes in AEM by Anurag Chaudhary Abstract With Sling Pipes it's very easy to update the AEM content. It is a tool for executing CURD operations over resources in AEM repository. Hope this will be helpful. Plumber is OSGi service and it has newPipe method in which we need to pass resourceResolver. After that we can call several pipes or methods to achieve our objective. Some of them are- echo(path) - to retrieve the root resource of the path. write(config) - to write/update properties of a resource. run() - to execute the code. Use case: To update property of a node using Sling Pipe OSGi service. Dependencies required- 1. Sling Query (org.apache.sling.query-4.0.0)- Maven Repository: org.apache.sling » org.apache.sling.query » 4.0.0 (mvnrepository.com) 2, Sling Pipes (org.apache.sling.pipes-3.1.0)- Maven Repository: org.apache.sling » org.apache.sling.pipes » 3.1.0 (mvnrepository.com) Either install the bundle of respective dependency in console

We are on AEM 6.5.8 with core component version 2.14.0 and facing an issue with rollout of container based core wcm components such as Carousel,Tabs and Accordion. Steps to replicate:Create a page on master copy using editable template.Author the master page with Carousel, Tabs and Accordion components and rollout the components to live copies using component level rollout.Verify if the Live copies have the components added to itBreak the component level inheritance of the Carousel, Tabs and Accordion components in the Live copy page and author them with a different content other than the one in master page.Repeat rolling out the Carousel, Tabs and Accordion components from the Master PageNow we observed that the Live copies are still inheriting the content from the Master Page, though the inheritance is broken.We tried the same with other components such as Title as well, but that seems to work fine.We observed this issue only for core wcm container based components. Ha

How to disable all workflows in Adobe Experience Manager? by Initialyze Abstract Adobe Experience Manager has a number of workflows and several of these workflows trigger automatically while performing certain operations such as uploading assets or creating / updating content. The DAM Update Asset workflow for e.g. generates thumbnail renditions, extracts metadata of assets etc. whenever you upload any asset and it’s resource intensive. There are certain times when performing certain large batch operations we don’t want workflows in AEM to kick in as they add additional overhead. Some common use cases where you may need to disable workflows for e.g: When backfilling content or syncing Digital Assets or content between environments Installing packages containing digital assets Performing large asset ingestions The workflows are triggered automatically by a Workflow Launcher configuration. While you can individually turn off each workflow, the quickest way to turn off all workflows in

Adobe Experience Manager as a Cloud Service - Terminology by Adobe Docs Abstract The following terms are used in relation to Adobe Experience Manager (AEM) as a Cloud Service: AEM as a CloudService :- The cloud-native way of leveraging the AEM applications AEM Assets as a Cloud Service:- Digital Asset Management (DAM) capabilities as cloud-native, scalable solution, to ingest, process, and manage your digital assets, while integrating with the wider Adobe Experience Cloud and Adobe Creative Cloud ecosystem. AEM Sites as a Cloud Service:- An instance of the AEM as a Cloud Service with the AEM Sites application. Adobe Pipeline:- The mechanism for publishing content from author to publish. AEM Author Tier:- Describes the authoring environment for Sites and Assets. AEM Preview Tier:- Describes the preview environment for Sites. AEM Publish Tier:- Describes the publishing environment for Sites. AEM Image:- A deployable artifact that contains the AEM product code together with the custom

About Adobe Experience Manager Assets as a DAM solution by Adobe Docs Abstract Assets is a Digital Asset Management (DAM) tool that is an integral part of the Experience Manager platform and enables your enterprise to manage and distribute digital assets. Users across an organization can manage, store, and access many types of digital assets such as images, videos, documents, audio clips, 3D files, and rich media for use on the web, in print, and for digital distribution. What is Digital Asset Management? Assets provides enterprise-wide sharing and distribution of an organization’s key digital assets. Users across an organization can store, manage, and access digital assets such as images, graphics, audio, video, and documents through a Web interface (or a CIFS or WebDAV folder). Assets capability of Experience Manager lets you do the following: Add and share images, documents, audio files, and video files in a variety of file formats. Manage assets by grouping them by tags, lightb

Best Practices for AEM Assets by Adobe Docs Abstract Adobe Experience Manager Assets is a crucial part of delivering high-quality digital marketing experiences that contribute to the achievement of business goals through increasing your content velocity. If you work with a large number of assets within Experience Manager Assets or regularly/periodically upload numerous assets, including videos and Dynamic Media, optimizing your digital asset management experience is critical for system efficiency. Depending upon how you have positioned Assets for your organization and the features that you use for asset ingestion, rendition generation, and metadata extraction, identifying and adhering to best practices in different areas greatly enhances system stability and performance under load. After reviewing the following guides, you will have the knowledge and tools to build and manage an enterprise asset management system that meets your needs: The Assets performance tuning guide: This guid

Configure Dynamic Media - Scene7 mode by Adobe Docs Abstract If you use Adobe Experience Manager set up for different environments, such as development, staging, and production, configure Dynamic Media Cloud Services for each one of those environments. Architecture diagram of Dynamic Media - Scene7 mode The following architecture diagram describes how Dynamic Media - Scene7 mode works. With the new architecture, Experience Manager is responsible for primary source assets and synchs with Dynamic Media for asset processing and publishing: When the primary source asset is uploaded to Experience Manager, it is replicated to Dynamic Media. At that point, Dynamic Media handles all asset processing and rendition generation, such as video encoding and dynamic variants of an image. (In Dynamic Media - Scene7 mode, the default upload file size is 2 GB or less. To enable upload file sizes of 2 GB up to 15 GB, see (Optional) Configure Dynamic Media - Scene7 mode for upload of assets larger tha

Customize and extend Assets by Adobe Docs Abstract The Asset Editor is the primary point of access that users of a Adobe Enterprise Manager website will use to find, view, and manipulate the digital assets in your repository. As an Experience Manager developer, you can customize and extend the Asset Editor in a number of ways, presenting users with a specifically tailored interface and set of functionality. The following aspects of the functionality can be customized or enhanced: Extend Asset Editor Extend Assets Search Process Assets Using Media Handlers and Workflows Integrate Assets with activity stream Assets proxy development Best practices to configure ImageMagick Customize the appearance The following aspects of the look and feel of the Asset Editor are customizable: Logo: You can add your own organization’s logo to the interface. Colors and Fonts: You can change the colors and fonts used in the interface. HTML Code: For more thorough customization you can change the underl

Assets HTTP API by Adobe Docs Abstract The Assets HTTP API allows for create-read-update-delete (CRUD) operations on digital assets, including on metadata, on renditions, and on comments, together with structured content using Experience Manager Content Fragments. It is exposed at /api/assets and is implemented as REST API. It includes support for Content Fragments. To access the API: Open the API service document at https://[hostname]:[port]/api.json. Follow the Assets service link leading to https://[hostname]:[server]/api/assets.json. The API response is a JSON file for some MIME types and a response code for all MIME types. The JSON response is optional and may not be available, for example for PDF files. Rely on the response code for further analysis or actions. After the Off Time, an asset and its renditions are not available via the Assets web interface and through the HTTP API. The API returns 404 error message if the On Time is in the future or Off Time is in the past. CA

What is AEM Screens? by Adobe Docs Abstract AEM (Adobe Experience Manager) Screens - a Digital Signage Solution that allows you to publish dynamic and interactive digital experiences and interactions involving different types of screens in conjunction with a comprehensive digital marketing platform. Get up and running with a simple digital signage experience, using Kickstart for AEM Screens. To learn how to configure and create your AEM Screens project in AEM as a Cloud Service, see here. Overview AEM Screens is built on the solid foundation of AEM Sites and enables marketers and IT personnel to create and manage experiences on multiple digital screens that impact in-store/in-venue goals for building brand and driving demand. Integration of AEM Screens with Sites allows you to re-use already existing content and effectively deliver a coherent and consistent customer solution. This provides a streamlined workflow to create dedicated digital experiences that are highly cost-effective

AEM 6.5 -> Deploying Guide -> Recommended Deployments by Adobe Docs Abstract NOTE This page refers to recommended topologies for AEM. For more information on clustering capabilities and how to configure them, see the Apache Sling Discovery API documentation. MicroKernels act as persistence managers starting from AEM 6.2. Choosing one to fit your needs depends on the purpose of your instance and the deployment type you are considering. The below examples are meant to be an indication of what are their recommended uses in the most common AEM setups. Read Full Blog AEM 6.5 -> Deploying Guide -> Recommended Deployments Q&A Please use this thread to ask the related questions.

How Content and Commerce Helps Customers Being Successful by Adobe Docs Abstract Content and Commerce With Adobe Experience Manager content and commerce, brands can scale and innovate faster to differentiate commerce experiences and capture accelerating online spend. AEM Content and Commerce combines the immersive, omnichannel, and personalized experiences in Experience Manager with any number of commerce solutions to bring differentiated experiences to all parts of the shopping journey, reducing time to value and driving higher conversion. How Content and Commerce Helps Customers Being Successful With ever-increasing customer expectations for online commerce experiences, brands are pressured to deliver differentiated experiences and more content faster. However, implementing a content management platform often requires heavy time and budget investments in developing foundational elements, such as custom components and authoring tools, and accrues costs in maintenance and upgrades. E

Optimizing JCR Session Saves by Andrew Top Abstract When performing many modifications to your AEM Java Content Repository (JCR) does your instance slow down, perhaps to the point where it is unusable? What is causing the slow down? Can it be prevented? The JCR is usually tuned to be quick with read operations but is relatively slow with writes. Many quick, subsequent writes can be quite taxing to the JCR session and the instance. But how often should you perform session saves? Can you save too infrequently? There are articles on this problem, many giving advice on the perfect save frequency. Is there a one-size-fits-all number? With these questions in mind, we’re presenting a new tool for testing session save frequencies: https://github.com/adobe/aem-performance-experiments/tree/main/experiments/session-save-frequency We hope this repository will help show, in a hands-on way, how different frequencies of JCR Session Saves can affect overall performance and instance health. It may gi

Hello Community - I am using the request object ${request.serverName} to retrieve the domain name. If I access the dispatcher URL, it is returning the AEM Publish instance name(which is incorrect) instead of the actual domain name of the page I am trying to access. i.e If I try to access the page: https://www.example.com/test.html - It should return "www.example.com"Accessing AEM Publish instance: https://aempublish:8080/test.html - should return "aempublish" I have even verified the dispatcher configs (VirtualHost entrues). Can someone tell me how can I fix this? 

Unit Testing JavaScript/TypeScript in AEM with Jest by 3sharecorp Abstract When there are tight timelines to meet, writing JS tests seems like unnecessary overhead. However, its benefits - identifying bugs earlier in the Software Development Life Cycle (SDLC), improving code quality and ensuring that code will fulfill its intended purpose if updated later - far outweigh the time invested implementing them. Below I will outline the setup we did for one of our projects at 3|SHARE to implement JS unit testing using Jest and Babel. Prerequisites For the setup below, you'll need a project directory housing the AEM Archetype with the ui.frontend module available. I recommend you use NodeJS v14.16.0+, and, ensure the frontend-maven-plugin reflects this in the root pom.xml so the correct version is picked up by the maven build. ... com.github.eirslett frontend-maven-plugin 1.11.3 v14.16.0 6.14.11 ... Setup We opted to use Jest because of its popularity and ability to integrate with many

Exadel Renews Adobe Experience Manager Sites Specialization by Exadel Abstract As an Adobe Solution Partner, we’ve recently had the opportunity to renew our Adobe Experience Manager Sites Specialization for the Americas. The Exadel MarTech Practice team of AEM-certified architects, developers, and business practitioners proved once again that they have the expertise necessary to pass the Adobe certification process. Our company provides marketing technology services to help clients across a variety of industries improve customer experience with leading MarTech platforms. The MarTech Practice creates unique open-source solutions that help customers and developers get the most out of AEM. Find out which of our MarTech services and solutions can benefit your website or portal. Read Full Blog Exadel Renews Adobe Experience Manager Sites Specialization Q&A Please use this thread to ask the related questions.

Hi, I am looking for some help here as I'm close but I am a bit lost. I have  a an adaptive form in our development environment.  Its pointing to a JEE Application*I used the following directions to set this up* https://experienceleague.adobe.com/docs/experience-manager-65/forms/install-aem-forms/configure-aem-forms/submit-form-data-livecycle-process.html?lang=en In the past with regular PDF I use exportData service to pull the information out of the PDF.  However this isn't a PDF and of course I'm running into an error. What Service Operation in workbench would I use to take the data from the Adaptive form, then push that to  Oracle database?   Thank you!

Experience League LIVE Ep. 2: Make Your Next Audience Segment Smarter than EverHeld on August 26, 2021, this live stream event featured Aaron Shields, Yaya Wang, and Andres Monroy, discussing the design, building, and functionality of the Adobe Experience Platform segment builder. Feel free to discuss this session here, ask questions, etc. We hope that you will find this session helpful as you learn and leverage the Platform segment builder.

Adobe Campaign Insider Monthly Webinar Series   Session Topic:  Team, skills, and organizational design required to support cross-channel marketing with Adobe Campaign   Recording URL: https://adobe.ly/3Pd8zVo    About the Session: In today’s cross-channel and digital world, consumers are empowered to engage wherever, whenever, and however they want. And the marketer must be ready, otherwise they risk a poor customer experience, or worse, attrition. The answer is not just a marketing platform that supports the orchestration of messages across channels, but also having a marketing organization that supports planning, execution, and measurement of marketing campaigns across all channels.Join this session to learn about: Industry trends and challenges Building blocks for an optimal marketing organization Where to start; change management Skills assessment Customer success stories   Session Speakers: Linda Reed, Campaign Consulting Practice Leader

Embedding Third party dependency/OSGi bundle in AEM application hosted in AEMasCS by Myaemlearnings Abstract This post illustrate the ways of embedding third party dependency in AEM maven project. Steps are mentioned considering the project structure to be followed for AEMasCS while the same can be followed for classic versions too. Before we begin, I would like to explain the scenario of including a dependency in our AEM maven project. When we would like to make use of an API that is not already available in our project, we look for that in maven-central repository and specify the dependency in main pom.xml and desired module's pom.xml file. (Lets say, AWS S3 Java SDK V2 dependency) Upon updating the project in the IDE, we would see our class files (making use of those APIs) are compiled/build successfully without any errors. Now, in the context of AEM/OSGi environment, when the same package and hence the bundle is deployed to AEM instance, dependencies that we added new might not b

Multi-Repo Git Script for AEM Cloud Service: cmreactor.sh ADOBE EXPERIENCE MANAGER by Bounteous Abstract Don't be an irritable CM Developer + Deployment Manager—add our portable cmreactor script to your AEM Cloud Service project today! Adobe Experience Manager (AEM) developers are often caught by surprise the first time they deploy a second codebase to an AEM as a Cloud Service environment when they discover that the first codebase has been completely removed. This is due to a fundamental change to how AEM loads code at runtime in Cloud Service, compared to how the process has traditionally worked in AEM Classic. Instead of uploading and installing any content packages in the build to a running AEM Package Manager, a Cloud Manager pipeline now builds a complete docker volume from scratch every time it is run by combining the standard AEM platform libraries with the build artifacts resulting only from the current git commit. A major benefit of this new approach is that the server cod