Product Communities

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

Adobe Experience Manager Assets Brand Portal Guide by Adobe Docs Abstract Adobe Experience Manager Assets Brand Portal aids organizations to meet their marketing needs by securely distributing approved brand and product assets to external agencies, partners, internal teams, and resellers for download. The lack of a secure asset sharing solution can result in: Manual asset sharing through email or cloud Brand compliance issues Lack of control over asset usage Delays in campaigns and product launches Duplication of content across geographic locations and organizations Unsecured storage of assets before release With Brand Portal, organizations can ensure brand compliance by enabling marketers to collaborate with channel partners and internal business users to quickly create, manage, and deliver the latest design guidelines, logos, campaign and product assets to the stakeholders. Brand Portal is a cloud-based SAAS offering. It is available as an add-on to Adobe Experience Manager Assets

Configure AEM Assets with Brand Portal by Adobe Docs Abstract Configuring Adobe Experience Manager Assets with Brand Portal enables asset publishing, asset distribution, and asset contribution features for the Brand Portal users. It allows the AEM Assets users to publish and distribute assets with the Brand Portal users. The Brand Portal users can access the shared assets and contribute by uploading new assets to the asset contribution folders and publishing them back to AEM Assets. Configuring AEM Assets with Brand Portal is supported on: AEM Assets as a Cloud Service AEM Assets (on premise and managed service) 6.3 and above AEM Assets as a Cloud Service is automatically configured with Brand Portal by activating Brand Portal from the Cloud Manager. The activation workflow creates the required configurations at the backend and activates Brand Portal on the same IMS org as of the AEM Assets as a Cloud Service instance. Whereas, AEM Assets (on premise and managed service) is manuall

Share folders on Brand Portal by Adobe Docs Abstract Assets need to be published to Brand Portal from a pre-configured AEM Author instance, as Brand Portal does not support asset ingestion. Folder sharing workflow in Brand Portal The following describes the folder share workflow and user access: By default, all the folders published from AEM Assets to Brand Portal are visible only to the Brand Portal Administrator, unless marked as public while configuring replication. The Administrator uses the Folder Properties console to share a folder with selective users or groups. Only those users or groups with whom the folder is shared can see the folder after they log in to Brand Portal. The folder is not visible to other users. The Administrator can also choose to make a folder public through the Public Folder check box in the Folder Properties console. A public folder is visible to all the users. Irrespective of user roles and privileges, when users log in to Brand Portal, they see all

AEM - Content Insight by Adobe Docs Abstract Content Insight provides information about page performance using web analytics and SEO recommendations. Use Content Insight to make decisions about how to modify pages, or to learn how previous changes have changed performance. For every page that you author, you can open Content Insight to analyse the page. The layout of the Content Insight page changes to suit the screen dimensions and orientation of the device that you are using. Report Data The Content Insight page includes reports that use Adobe SiteCatalyst, Adobe Target, Adobe Social, and BrightEdge data: SiteCatalyst: Reports for the following metrics are available: Page views Average time spent on page Sources Target: Reports on campaign activity for which your page includes offers. BrightEdge: Reports on the page features that improve the visibility of the page to search engines, and recommends features that should be implemented. Read Full Blog AEM - Content Insight Q&

AEM - Analyzing Page Performance by Adobe Docs Abstract Open the Content Insight page to analyze the performance of the page that you are authoring. Configure the reporting period to focus your analysis. Opening Analytics and Recommendations for a Page Use the following procedure to see the Analytics and Recommendations for a page: Navigate to the page that you want to analyze. In the toolbar, click or tap Analytics and Recommendations. NOTE Analytics and Recommendations for a page only appear if you have configured AEM to integrate with Adobe Analytics. Changing the Reporting Period Change the following time-related aspects of the analytics reports: The period of time on which to report. The granularity of the data. The tools for changing the time-related aspects of the reports appear at the top of the Content Insight page. chlimage_1-126 Changing the Reporting Period Change the reporting period of the Content Insight page to focus your analysis of page activity to a specific

AEM - Forms Automated Conversion Guide by Adobe Docs Abstract Introduction Automated Forms Conversion service helps accelerate digitization and modernization of data capture experience through automated conversion of PDF forms to adaptive forms. The service, powered by Adobe Sensei, automatically converts your PDF forms to device-friendly, responsive, and HTML5-based adaptive forms. While leveraging the existing investments in PDF Forms and XFA, the service also applies appropriate validations, styling, and layout to adaptive form fields during conversion. The service helps: Save manual effort required to convert print forms to adaptive forms Applies patterns and appropriate validations during conversion Generate Document of Record during conversion Group commonly occurring fields into reusable form fragments Enables Adobe Analytics during conversion Onboarding The service is available for free to AEM 6.4 Forms and AEM 6.5 Forms On-Premise term customers and Adobe-Managed Service en

AEM - Development Best Practices by Adobe Docs Abstract Work according to a Definition of Done Each team has a different definition of what “done” means, but it is important to have one and ensure that a story meets the defined criteria before being accepted. Some criteria that are commonly specified by teams include: Code reviewed for formatting Comments/Javadoc added Meets required test coverage levels Passes unit and integration tests Validated in the QA environment Localization implemented Without a well-defined DoD, it is easy to end up in a situation where a lot of things are halfway done and nothing is truly complete. Define and adhere to coding and formatting conventions Things like indentation levels and white space may not seem important, but having properly formatted code goes a long way towards readability and maintainability. Conventions should be discussed and agreed to as a team and then followed in the code. Aim for high test coverage As a project implementation gr

AEM - Development Tools by Adobe Docs Abstract To develop your JCR, Apache Sling or AEM applications, the following tool sets are available: one set consisting of CRXDE Lite and WebDAV. CRXDE Lite is embedded into CRX/AEM and enables you to perform standard development tasks in the browser. With CRXDE Lite, you can create and edit files (like .jsp and .java), folders, templates, components, dialogs, nodes, properties and bundles while logging and integrating with SVN. CRXDE Lite is recommended when you do not have direct access to the CRX/AEM server, when you develop an application by extending or modifying the out-of-the-box components and Java bundles or when you do not need a dedicated debugger, code completion and syntax highlighting. one set consisting of an Integrated Development Environment (for example: Eclipse or IntelliJ), a build tool (for example: Apache Maven), FileVault which has been developed by Adobe to map a repository to a file system, a version control system (f

AEM Modernization Tools by Adobe Docs Abstract AEM Modernization Tools allow for the easy conversion of: Static templates to editable templates Design configurations to policies Foundation Components to Core Components Classic UI to Touch-Enabled UI For further information about the usage of these tools, see their documentation. NOTE AEM Modernize Tools are a community effort and are not supported or warrantied by Adobe. Read Full Blog AEM Modernization Tools Q&A Please use this thread to ask the related questions.