<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Abhigyan Swaroop on Medium]]></title>
        <description><![CDATA[Stories by Abhigyan Swaroop on Medium]]></description>
        <link>https://medium.com/@abhigyanswaroop?source=rss-249a05c86f5a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*YiBQEtBZW3thtIiSTKid8g.jpeg</url>
            <title>Stories by Abhigyan Swaroop on Medium</title>
            <link>https://medium.com/@abhigyanswaroop?source=rss-249a05c86f5a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:49:44 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@abhigyanswaroop/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Understanding the Dispatcher in Adobe Experience Manager (AEM)]]></title>
            <link>https://abhigyanswaroop.medium.com/understanding-the-dispatcher-in-adobe-experience-manager-aem-096b8ab29c31?source=rss-249a05c86f5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/096b8ab29c31</guid>
            <category><![CDATA[aem-dispatcher]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[dispatcher]]></category>
            <dc:creator><![CDATA[Abhigyan Swaroop]]></dc:creator>
            <pubDate>Wed, 20 Aug 2025 08:11:09 GMT</pubDate>
            <atom:updated>2025-08-20T08:13:59.211Z</atom:updated>
            <content:encoded><![CDATA[<h3>Understanding Dispatcher in Adobe Experience Manager (AEM)</h3><h3>What is a Dispatcher?</h3><p>In Adobe Experience Manager (AEM), the <strong>Dispatcher</strong> is a key component that acts as both a <strong>caching tool</strong> and a <strong>load balancer</strong>. It sits between the end-users (clients) and the AEM publish servers, managing how requests for content are handled. Think of it as a smart traffic controller: it decides whether to serve content quickly from its cache, or to fetch fresh content from the AEM servers, and it distributes incoming requests to keep the system running smoothly.</p><h3>Why is the Dispatcher Important?</h3><p>The Dispatcher is vital for several reasons:</p><ul><li><strong>Performance Boost:</strong> By caching frequently requested pages and assets, it reduces the load on AEM servers and speeds up content delivery to users.</li><li><strong>Scalability:</strong> It balances requests across multiple AEM publish instances, allowing the system to handle more users and higher traffic.</li><li><strong>Security:</strong> It can filter requests, blocking unwanted or potentially harmful traffic before it reaches the AEM servers.</li><li><strong>Efficiency:</strong> By serving cached content, the Dispatcher minimizes redundant processing, freeing up resources for dynamic or personalized content.</li></ul><p>In summary, the Dispatcher is essential for making AEM-powered websites fast, reliable, and secure.</p><h3>2. Usual Flow of Requests</h3><h3>Step-by-Step Module Interaction</h3><p>Let’s walk through how each module participates in the request flow:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*atgDLyrQG6IVLbqydL-Cbg.png" /><figcaption>Simplifined Request processing within dispatcher</figcaption></figure><h4>1. User Request Arrives</h4><ul><li>The user’s browser sends a request (e.g., for a web page).</li><li>The request first hits the <strong>Web Server</strong> (like Apache or IIS) where the Dispatcher module is installed.</li></ul><h4>2. Dispatcher Receives Request</h4><ul><li>The Dispatcher becomes the gatekeeper and starts processing the request using its configuration modules.</li></ul><h4>3. Virtual Hosts (/virtualhosts)</h4><ul><li><strong>Role:</strong> Determines which farm (set of rules) should handle the request based on hostname and URI.</li></ul><p><strong>Visual:</strong> Imagine a sorting machine that directs requests to the right set of rules depending on the website or section being accessed.</p><h4>4. Farms (/farms)</h4><ul><li><strong>Role:</strong> Each farm contains its own configuration for caching, filtering, and load balancing.</li></ul><p><strong>Visual:</strong> Farms are like different lanes in a highway toll booth, each with its own rules for traffic.</p><h4>5. Filters (/filter)</h4><ul><li><strong>Role:</strong> Acts as a security checkpoint, allowing or denying requests based on method, path, or other criteria.</li></ul><p><strong>Visual:</strong> Think of this as a guard who checks if a request is safe or needs to be blocked.</p><h4>6. Cache (/cache)</h4><ul><li><strong>Role:</strong> Checks if the requested content is already stored locally.</li><li>If cached, serves it instantly.</li><li>If not, forwards the request to AEM.</li></ul><p><strong>Visual:</strong> Like a pantry — if the food (content) is there, you get it fast; if not, someone needs to cook (AEM server).</p><h4>7. Renders (/renders)</h4><ul><li><strong>Role:</strong> Lists available AEM publish servers to handle uncached requests.</li></ul><p><strong>Visual:</strong> Like a manager assigning tasks to available team-mates(servers).</p><h4>8. Statistics (/statistics)</h4><ul><li><strong>Role:</strong> Tracks how quickly each AEM server responds, helping the Dispatcher pick the best one for new requests.</li></ul><p><strong>Visual:</strong> Like a scoreboard showing which batsmans strike rate is highest.</p><h4>9. Vanity URLs (/vanity_urls)</h4><ul><li><strong>Role:</strong> Maps friendly URLs to actual content paths.</li></ul><p><strong>Visual:</strong> Like a directory that translates “/about-us” to the actual location in the system.</p><h4>10. Session Management (/sessionmanagement)</h4><ul><li><strong>Role:</strong> Ensures requests from the same user are handled consistently, especially for personalized content.</li></ul><p><strong>Visual:</strong> Like a VIP lane for returning customers, ensuring their experience is seamless.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZTaEnQctb3jLP2BVpKHm9g.png" /><figcaption>Detailed request processing in Dispatcher</figcaption></figure><h3>3. Different Modules and Their Functions</h3><p>The Dispatcher’s behavior is controlled by its configuration, typically set in a file called dispatcher.any. Here are the main modules (sections) and their functions:</p><h4>a. Farms</h4><ul><li><strong>What They Do:</strong> Define groups of rules for handling different websites or sections of a site.</li><li><strong>How They Work:</strong> Each farm can have its own set of rules for caching, filtering, and load balancing, allowing fine-tuned control.</li></ul><h4>b. Virtual Hosts</h4><ul><li><strong>What They Do:</strong> Specify which hostnames and URLs the Dispatcher should handle.</li><li><strong>How They Work:</strong> Help route requests to the correct farm or set of rules, especially in multi-site environments.</li></ul><h4>c. Filters</h4><ul><li><strong>What They Do:</strong> Control which types of requests are allowed through to AEM.</li><li><strong>How They Work:</strong> Act as security gates, blocking unwanted or potentially dangerous requests (e.g., certain HTTP methods or paths).</li></ul><h4>d. Renders</h4><ul><li><strong>What They Do:</strong> List the AEM publish servers available to handle requests.</li><li><strong>How They Work:</strong> Enable load balancing by distributing requests among multiple servers.</li></ul><h4>e. Cache</h4><ul><li><strong>What It Does:</strong> Defines how and where content is cached.</li><li><strong>How It Works:</strong> Sets rules for what gets cached, for how long, and under what conditions content should be invalidated or refreshed.</li></ul><h4>f. Statistics</h4><ul><li><strong>What It Does:</strong> Tracks how responsive each AEM server is.</li><li><strong>How It Works:</strong> Helps the Dispatcher choose the best server for new requests, improving performance and reliability.</li></ul><h4>g. Vanity URLs</h4><ul><li><strong>What They Do:</strong> Support friendly URLs (e.g., /about-us instead of /content/site/about-us.html).</li><li><strong>How They Work:</strong> Map short, memorable URLs to actual content paths in AEM.</li></ul><h4>h. Session Management</h4><ul><li><strong>What It Does:</strong> Manages user sessions and authentication.</li><li><strong>How It Works:</strong> Ensures that requests from the same user are handled consistently, especially important for personalized or secure content.</li></ul><h3>Real-World Example</h3><p>Imagine a large retail website during a holiday sale. Thousands of users are browsing and making purchases at the same time. The Dispatcher:</p><ul><li>Serves cached product pages instantly to most users, reducing server strain.</li><li>For personalized content (like shopping carts), forwards requests to the AEM servers.</li><li>Balances requests so no single server is overwhelmed.</li><li>Blocks suspicious requests, protecting the site from attacks.</li></ul><p>Without the Dispatcher, the AEM servers could quickly become overloaded, leading to slowdowns or outages.</p><h3>Conclusion</h3><p>The Dispatcher is a cornerstone of any robust AEM deployment. By intelligently caching content, balancing loads, and filtering requests, it ensures that websites remain fast, secure, and scalable — even under heavy traffic. Understanding its modules and how they work together helps both technical and non-technical stakeholders appreciate the Dispatcher’s vital role in delivering exceptional digital experiences.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=096b8ab29c31" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[End-to-End Request Processing in Adobe Experience Manager: MVC Architecture Explained]]></title>
            <link>https://abhigyanswaroop.medium.com/end-to-end-request-processing-in-adobe-experience-manager-mvc-architecture-explained-e7bf8822d957?source=rss-249a05c86f5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7bf8822d957</guid>
            <category><![CDATA[mvc-architecture]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <dc:creator><![CDATA[Abhigyan Swaroop]]></dc:creator>
            <pubDate>Thu, 14 Aug 2025 10:56:05 GMT</pubDate>
            <atom:updated>2025-08-14T10:56:05.706Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>In today’s rapidly evolving digital landscape, enterprises are increasingly turning to sophisticated content management systems (CMS) to meet the demands of a dynamic market. Among these, Adobe Experience Manager (AEM) has emerged as a leading platform, renowned for its ability to seamlessly integrate with various backend systems, from customer data platforms to e-commerce engines.</p><p>At the heart of AEM’s robust functionality lies the Model-View-Controller (MVC) architecture — a design pattern that ensures modularity, maintainability, and scalability of digital experiences.</p><p>As organizations transition towards cloud-native architectures and strive for real-time data synchronization, the integration capabilities of AEM become crucial. The need to effectively manage diverse content assets while orchestrating personalized user experiences across multiple channels is more pressing than ever. This article delves into the intricacies of the MVC architecture within AEM, exploring how it facilitates end-to-end request processing and optimizes infrastructure for performance, scalability, and reliability.</p><p>In this article, we will explore the end-to-end lifecycle of user requests within AEM, the optimization strategies for infrastructure components, and the importance of a unified identity framework for personalized content delivery. By examining industry best practices and empirical findings, we aim to provide technical leaders with the insights needed to architect high-performing, resilient digital platforms that support business agility and omni-channel engagement. Join us as we uncover the power of AEM’s MVC architecture and its integration with backend systems, paving the way for future-ready enterprise digital experiences.</p><figure><img alt="MVC architecture of AEM" src="https://cdn-images-1.medium.com/max/1024/1*etD2rJK9v6aTcPtPTO6FPA.png" /><figcaption>MVC architecture of AEM</figcaption></figure><h3>Understanding MVC Architecture in Adobe Experience Manager (AEM)</h3><h3>What is MVC Architecture?</h3><p><strong>MVC</strong> stands for <strong>Model-View-Controller</strong>. It’s a common way to organize code in software development, especially for web applications. Think of it as dividing responsibilities among three main parts:</p><ul><li><strong>Model:</strong> Handles the data and business logic (the “brains”).</li><li><strong>View:</strong> Manages how information is displayed to users (the “face”).</li><li><strong>Controller:</strong> Acts as the coordinator, handling user input and updating the Model or View as needed (the “traffic cop”).</li></ul><p>This separation makes applications easier to build, maintain, and scale.</p><h3>How Does MVC Work in AEM?</h3><p>Adobe Experience Manager uses the MVC pattern to manage how web pages are built and served to users. Here’s how each part fits in:</p><h4>1. Model (Data and Logic)</h4><ul><li>In AEM, the Model is often represented by <strong>Sling Models</strong> or Java classes.</li><li>These models fetch data from the content repository (where all your website’s content is stored) or from backend systems (like databases or APIs).</li></ul><p>Example: If you have a “Product” page, the Model gathers product details, prices, and images.</p><h4>2. View (Presentation)</h4><ul><li>The View in AEM is typically built using <strong>HTL (HTML Template Language)</strong>, which controls how content appears on the website.</li><li>HTL templates pull in data from the Model and display it in a user-friendly way.</li></ul><p>Example: The product details fetched by the Model are shown in a visually appealing layout.</p><h4>3. Controller (Request Handling)</h4><ul><li>The Controller is responsible for handling user actions, such as clicking a button or submitting a form.</li><li>In AEM, this is often managed by <strong>Sling Servlets</strong> or <strong>OSGi Services</strong>.</li></ul><p>Example: When a user clicks “Add to Cart,” the Controller processes this request and updates the shopping cart.</p><h3>How Does AEM Integrate with Backend Systems?</h3><p>AEM rarely works alone. It often needs to connect with other systems — like customer databases, inventory management, or e-commerce platforms — to deliver a complete digital experience.</p><h4>Integration Flow:</h4><ol><li><strong>User Request:</strong> A visitor lands on a web page or interacts with a feature.</li><li><strong>Controller Activation:</strong> The Controller receives the request and decides what needs to happen.</li><li><strong>Model Fetches Data:</strong> The Model may pull information from AEM’s own content repository or reach out to backend systems via APIs.</li><li><strong>View Renders Content:</strong> The View displays the updated information to the user.</li></ol><p><strong>Example Scenario:</strong><br> A customer visits a product page. The Controller triggers the Model to fetch the latest product details from an inventory system. The View then displays this information in real time.</p><h3>Optimizing Performance and Scalability</h3><p>For large organizations, it’s crucial that digital platforms are fast, reliable, and can handle lots of users at once. AEM uses several strategies to achieve this:</p><h4>Key Components:</h4><ul><li><strong>Caching:</strong> Stores frequently accessed content so it can be delivered quickly without repeated processing.</li><li><strong>Content Delivery Network (CDN):</strong> Distributes content across global servers, reducing load times for users everywhere.</li><li><strong>Load Balancer:</strong> Spreads user requests across multiple servers to prevent any one server from becoming overwhelmed.</li><li><strong>Dispatcher:</strong> AEM’s own tool for caching and security, ensuring only approved requests reach the core system.</li></ul><p><strong>Why This Matters:</strong><br> These components work together to ensure that users get a fast, seamless experience — even during high-traffic events like product launches or sales.</p><h3>Security and Personalization</h3><p>AEM also supports secure, personalized experiences:</p><ul><li><strong>Unified Identity Framework:</strong> Helps manage user authentication and authorization, ensuring that content is delivered to the right people.</li><li><strong>Personalization:</strong> By integrating with backend systems, AEM can tailor content based on user profiles, preferences, or past behavior.</li></ul><p><strong>Example:</strong><br> A returning customer sees personalized product recommendations based on their previous purchases.</p><h3>Visualizing the MVC Flow in AEM</h3><p>Here’s a simplified step-by-step flow:</p><ol><li>User visits a web page</li><li>Controller (Sling Servlet) receives the request</li><li>Model (Sling Model/Java class) gathers data from AEM or backend systems</li><li>View (HTL template) displays the data as a web page</li><li>Caching, CDN, and Dispatcher optimize delivery and security</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PU3wXjk5wVigjJzl9tudaA.png" /><figcaption>Request processing in AEM</figcaption></figure><h3>Why MVC in AEM Matters for Businesses</h3><ul><li><strong>Flexibility:</strong> Teams can update the look and feel (View) without changing how data is handled (Model).</li><li><strong>Maintainability:</strong> Issues can be fixed in one part without affecting the others.</li><li><strong>Scalability:</strong> Easily handle more users and content as your business grows.</li><li><strong>Integration:</strong> Connect seamlessly with other enterprise systems for richer digital experiences.</li></ul><h3>Conclusion</h3><p>Adobe Experience Manager’s implementation of the Model-View-Controller (MVC) architecture provides a powerful foundation for building scalable, maintainable, and integrated digital experiences. By clearly separating data management, presentation, and user interaction, AEM enables organizations to deliver content-rich, personalized websites and applications that can easily adapt to evolving business needs.</p><p>Through seamless integration with backend systems, robust caching, and optimization tools like CDNs and load balancers, AEM ensures high performance and reliability — even as user demands grow. The MVC approach also simplifies development and maintenance, allowing teams to innovate quickly while minimizing risk.</p><p>For businesses seeking to create engaging, secure, and future-ready digital platforms, understanding and leveraging MVC architecture within AEM is essential. By embracing these best practices, organizations can unlock new opportunities for customer engagement, operational efficiency, and digital transformation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7bf8822d957" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reimagining Digital Authoring: A Deep Dive into AEM EDS Architectures]]></title>
            <link>https://abhigyanswaroop.medium.com/reimagining-digital-authoring-a-deep-dive-into-aem-eds-architectures-4e5c323e0582?source=rss-249a05c86f5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e5c323e0582</guid>
            <category><![CDATA[aem-eds-universal-editor]]></category>
            <category><![CDATA[edge-delivery-services]]></category>
            <category><![CDATA[universal-editor]]></category>
            <category><![CDATA[document-base-authoring]]></category>
            <category><![CDATA[eds-with-universal-editor]]></category>
            <dc:creator><![CDATA[Abhigyan Swaroop]]></dc:creator>
            <pubDate>Wed, 06 Aug 2025 08:50:48 GMT</pubDate>
            <atom:updated>2025-08-06T09:31:35.781Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Adobe Experience Manager (AEM) Edge Delivery Services (EDS) is a robust solution for organizations seeking to modernize and streamline their digital content creation, management, and delivery. As enterprises face increasing demands for scalable, efficient, and collaborative content workflows, AEM EDS offers flexible implementation models to suit diverse business needs. This article, written from the perspective of an AEM developer, explores in detail the two primary AEM EDS setups — <strong>Document-Based Authoring</strong> and the <strong>Universal Editor</strong> — highlighting their architectures, integration patterns, workflow implications, scalability, and best practices.</p><h3>1. Document-Based Authoring Setup</h3><h3>1.1 Overview</h3><p>Document-Based Authoring leverages familiar productivity tools (e.g., Microsoft Word, Google Docs) for content creation. Authors draft documents offline or in cloud environments, which are then ingested into AEM EDS. The system parses these documents, extracting structured content and metadata, and transforms them into web-ready assets using predefined templates and mapping rules.</p><h3>1.2 Architecture</h3><h4>Diagram</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FxQ-UrkYKoHE4KFCI6vH9Q.png" /><figcaption>EDS with Document based authoring set-up</figcaption></figure><h3>1.3 Integration Patterns</h3><ul><li><strong>DAM Integration</strong>: Images and media referenced in documents are linked or uploaded to AEM’s Digital Asset Manager.</li><li><strong>Metadata Mapping</strong>: Document properties (author, date, tags) are mapped to AEM metadata fields.</li><li><strong>External Systems</strong>: Optional integration with document management systems (e.g., SharePoint) for source control.</li></ul><h3>1.4 User Workflows</h3><ul><li><strong>Content Creation</strong>: Authors work in their preferred tools.</li><li><strong>Submission</strong>: Documents are uploaded via portal, email, or automated sync.</li><li><strong>Transformation</strong>: Automated or semi-automated mapping to AEM page templates.</li><li><strong>Review &amp; Approval</strong>: Standard AEM workflow applies.</li><li><strong>Publishing</strong>: Content is published to web or other channels.</li></ul><h3>1.5 Scalability &amp; Performance</h3><ul><li><strong>Batch Processing</strong>: Supports high-volume ingestion via scheduled jobs.</li><li><strong>Horizontal Scaling</strong>: Parsing and transformation services can be scaled independently.</li><li><strong>Caching</strong>: Static content benefits from AEM dispatcher and CDN caching.</li></ul><h3>1.6 Pros &amp; Cons</h3><p><strong>Pros:</strong></p><ul><li>Low barrier to entry for non-technical users.</li><li>Rapid onboarding and content production.</li><li>Consistency through templates.</li></ul><p><strong>Cons:</strong></p><ul><li>Limited real-time collaboration.</li><li>Customization restricted to what templates allow.</li><li>Potential for content silos if not well integrated.</li></ul><h3>2. Universal Editor Setup</h3><h3>2.1 Overview</h3><p>The Universal Editor is AEM’s modern, browser-based, WYSIWYG content authoring tool. It provides in-context editing, drag-and-drop component assembly, and real-time collaboration. This setup is ideal for organizations requiring advanced customization, multi-site management, and dynamic content experiences.</p><h3>2.2 Architecture</h3><h4>Diagram</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/792/1*hMQb4fC26fnMh5onNRKGoA.png" /><figcaption>EDS with Universal Editor set-up</figcaption></figure><h3>2.3 Integration Patterns</h3><ul><li><strong>Headless APIs</strong>: Content can be delivered to web, mobile, and IoT via GraphQL/REST.</li><li><strong>Enterprise Systems</strong>: Deep integration with identity management (SSO), analytics, and marketing automation.</li><li><strong>Localization</strong>: Integration with translation services for global content delivery.</li></ul><h3>2.4 User Workflows</h3><ul><li><strong>In-Context Editing</strong>: Authors see changes as they make them.</li><li><strong>Component Assembly</strong>: Drag-and-drop interface for building pages.</li><li><strong>Collaboration</strong>: Multiple users edit, comment, and resolve conflicts in real time.</li><li><strong>Advanced Workflows</strong>: Customizable approval, localization, and publishing flows.</li></ul><h3>2.5 Scalability &amp; Performance</h3><ul><li><strong>Cloud-Native</strong>: Supports containerization and orchestration (Kubernetes, Docker).</li><li><strong>Auto-Scaling</strong>: Dynamically scales based on user load.</li><li><strong>Performance Monitoring</strong>: Integrated with real-user monitoring and analytics.</li></ul><h3>2.6 Pros &amp; Cons</h3><p><strong>Pros:</strong></p><ul><li>Rich authoring experience with real-time collaboration.</li><li>Highly customizable and extensible.</li><li>Supports complex, multi-site, and multi-language needs.</li></ul><p><strong>Cons:</strong></p><ul><li>Steeper learning curve for authors.</li><li>Higher infrastructure and governance requirements.</li><li>Greater potential for security and compliance risks.</li></ul><h3>3. Comparative Summary</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gjsxqVdPSkJBJWU52OmSCw.png" /><figcaption>Comparisonbased on features</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fncaPldq089wYj-8kKLj6Q.png" /><figcaption>Comparison based on architectural basis</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y4HBQAi4mpv-2bym_LRLhQ.png" /><figcaption>Comparison based on scalability metric</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M53gzFOCwf6kvKShUeBEqA.png" /><figcaption>Comparison based on areas of challenge</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FKey31JJr_eSPBW_gw0Krg.png" /><figcaption>Comparison based on integration metric</figcaption></figure><h3>4. Best Practices for AEM EDS Implementation</h3><h3>4.1 Assess Business Needs</h3><ul><li><strong>Content Volume</strong>: High-volume, repetitive content favors document-based setups.</li><li><strong>Customization</strong>: Advanced, personalized experiences require the Universal Editor.</li><li><strong>User Base</strong>: Large, non-technical teams benefit from document-based authoring.</li></ul><h3>4.2 Design for Security &amp; Compliance</h3><ul><li>Implement role-based access controls.</li><li>Encrypt sensitive data at rest and in transit.</li><li>Integrate with enterprise IAM for authentication and authorization.</li></ul><h3>4.3 Plan for Integration</h3><ul><li>Use standardized APIs for connecting with CRM, ERP, and analytics platforms.</li><li>Ensure DAM is a single source of truth for all assets.</li><li>Automate metadata mapping and content tagging.</li></ul><h3>4.4 Optimize for Performance</h3><ul><li>Leverage AEM Dispatcher and CDN for caching.</li><li>Monitor system health and user experience with analytics.</li><li>Regularly review and optimize workflows and templates/components.</li></ul><h3>4.5 Invest in Training &amp; Change Management</h3><ul><li>Provide tailored training for authors, editors, and administrators.</li><li>Document workflows and governance policies.</li><li>Foster a culture of continuous improvement.</li></ul><h3>5. Conclusion</h3><p>AEM EDS offers flexible, scalable solutions for digital content management, catering to both non-technical and advanced authoring needs. By carefully evaluating organizational requirements, investing in robust integration and security, and fostering user adoption, enterprises can maximize the value of their AEM EDS implementation — whether through document-based authoring for speed and simplicity or the Universal Editor for dynamic, collaborative content creation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e5c323e0582" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Add Watermark on the Video in AEM using FFmpeg]]></title>
            <link>https://abhigyanswaroop.medium.com/add-watermark-on-the-video-in-aem-using-ffmpeg-2b7cf9268185?source=rss-249a05c86f5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b7cf9268185</guid>
            <dc:creator><![CDATA[Abhigyan Swaroop]]></dc:creator>
            <pubDate>Thu, 18 Mar 2021 13:08:54 GMT</pubDate>
            <atom:updated>2021-03-18T13:31:33.541Z</atom:updated>
            <content:encoded><![CDATA[<h3>What is Watermarking?</h3><p>Watermarking is a technique with similarities to steganography. It is typically used to identify ownership of the copyright of such audio, videos or images. <strong>Digital watermark </strong>is the process to add such identifiable digital signature on the assets.</p><h4>What is Common use cases?</h4><p>In this world of digital marketing, companies spend a lot on increasing the digital presence and register themselves in every way possible to its prospective customers. Images and video production and use in advertisement is common practice. This not only attract customers but also established the brand presence among them. Adding watermark to these assets further adds on this and adds a recall of a brand whenever one see these content. Common industries making use of watermark are Consumer goods, Online retailers and content creators, Sponsors for event/celebrity etc.</p><p>AEM is a very powerful tool to manage content and cater to the customers.<br>During various implementation, I learnt client want to protect their videos and images</p><p>In this article, I will try to walk you through the process to add watermark image on any video via FFmpeg and then how to do it in AEM.</p><h3>Prerequisite</h3><ol><li>You should have FFmpeg installed on your local.<br>(For windows : go to <a href="https://github.com/BtbN/FFmpeg-Builds/releases">https://github.com/BtbN/FFmpeg-Builds​.</a> You need to download the FFmpeg zip file ending in “win64-gpl-4.3.zip” and add the path to bin folder of the installation in the environment variables.) there are plenty of video online which explains it in details.</li><li>Once you have FFmpeg installed on your system, verify the installations.</li></ol><p>You are good to go now.</p><h3>How to add image watermark on the video in AEM</h3><p>You would need to create a video profile in AEM with the filters options defined. <br>There are different ways we can add watermark on the videos, some of them are as follows, but this will need to be run in the command prompt/terminal directly. Using these you will get a feel of how your video will appear post-processing in AEM, however this is not exactly we will do in AEM. We will touch the topic to tackle it in AEM in following sections soon!</p><blockquote>Adding watermark on the centre of the video.</blockquote><blockquote>ffmpeg -i yourVideoName.mp4 -i yourWaterMarkImage.png -filter_complex &quot;overlay=(main_w-overlay_w)/2:(main_h-overlay_h)/2&quot; -codec:a copy yourDesiredOutputVideName.mp4</blockquote><blockquote>2. Similarly, the overlay of the watermark can be adjusted anywhere on the video<br>a. Top right with 10 pixel padding<br>overlay=main_w-overlay_w-10:10<br> b. Bottom right with 10 pixel padding<br>overlay=main_w-overlay_w-10:main_h-overlay_h-10 <br>c. Bottom left with 10 pixel padding<br>overlay=10:main_h-overlay_h <br>there are many options which can also be explored to adjust the opacity of the watermark image as well such as <br>ffmpeg -i yourVideoName.mp4 -i yourWaterMarkImage.png -filter_complex &quot;[1]format=rgba,colorchannelmixer=aa=0.5[logo];[0][logo]overlay=(W-w)/2:(H-h)/2:format=auto,format=yuv420p&quot; -c:a copy yourDesiredOutputVideName.mp4</blockquote><blockquote>Animation to the watermark image can also be done</blockquote><pre>1. For Watermark to animate on diagonal line:</pre><pre>ffmpeg -i demoVideo.mp4 -loop 1 -i myWatermark.png -filter_complex “[1]format=rgba,colorchannelmixer=aa=0.3[logo];[0][logo]overlay=x=’if(gte(t,0), ((W+w)\/5)\*mod(t\,5)-w, NAN)’:y=’if(gte(t,0), ((H+h)\/5)\*mod(t\,5)-h, NAN)’:shortest=1” -c:a copy yourDesiredOutputVideoName.mp4</pre><pre>2. For Watermark to animate along y-axis:</pre><pre>ffmpeg -i demoVideo.mp4 -loop 1 -i myWatermark.png -filter_complex overlay=x=0:y=&#39;((H+h)\/5)\*mod(t\,5)-h&#39;:shortest=1 yourDesiredOutputVideoName.mp4</pre><blockquote>Video will appear as below (along diagonal line) :</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*ZbnCLB1d9IYvwAeWR6YHpQ.gif" /></figure><h3><strong><em>Now let’s discuss how to get it working in AEM</em></strong></h3><p>Create a video profile with the desired custom filter argument. Here I will show how to add a thumbnail in the centre of the video with adjusted opacity of 10% (0.1).</p><ol><li>Create a custom video filter with below parameter inside</li></ol><p>“/conf//settings/dam/video/myCustomProfile”</p><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;jcr:root xmlns:sling=&quot;<a href="http://sling.apache.org/jcr/sling/1.0">http://sling.apache.org/jcr/sling/1.0</a>&quot; xmlns:cq=&quot;<a href="http://www.day.com/jcr/cq/1.0">http://www.day.com/jcr/cq/1.0</a>&quot; xmlns:jcr=&quot;<a href="http://www.jcp.org/jcr/1.0">http://www.jcp.org/jcr/1.0</a>&quot; xmlns:nt=&quot;<a href="http://www.jcp.org/jcr/nt/1.0">http://www.jcp.org/jcr/nt/1.0</a>&quot;<br>    jcr:primaryType=&quot;cq:Page&quot;&gt;<br>    &lt;jcr:content<br>        cq:template=&quot;/libs/dam/templates/videoprofile&quot;<br>        jcr:description=&quot;A video profile with high quality output to create watermarked videos&quot;<br>        jcr:primaryType=&quot;nt:unstructured&quot;<br>        jcr:title=&quot;Watermark FullHD (H.264 - HP - Lvl4.0)&quot;<br>        sling:resourceType=&quot;dam/components/video/profile&quot;<br>        customArgs=&quot;-i C:/Users/myuser/myfolder/watermark.png -filter_complex &amp;quot;[1][0]scale2ref=w=oh*mdar:h=ih*0.1[logo][video];[video][logo]overlay=5:H-h-5&amp;quot; -c:a copy&quot;<br>        extension=&quot;mp4&quot;<br>        htmlType=&quot;video/mp4; codecs=&amp;quot;avc1.640028, mp4a.40.2&amp;quot;&quot;<br>        mimeType=&quot;video/x-m4v&quot;<br>        renditionSelector=&quot;myIdentifiableID&quot;/&gt;<br>&lt;/jcr:root&gt;</pre><p>please look closely, I have added watermark image path as input (-i ) as</p><pre>C:/Users/myuser/myfolder/watermark.png</pre><p>This should be the address of the image which can be accessed via FFmpeg while processing i.e. the image should be local to the AEM server.</p><p>2. Now that we have a video profile created, we can design a workflow to add this filter to be picked up during the workflow process.<br>We would need to add a <strong>Process step </strong>in the workflow</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*zlwgk7ZwDk9LuT7dsFb8lg.png" /><figcaption>Workflow Process step configuration in AEM.</figcaption></figure><p>a. Select Process step from the available options to design the workflow.</p><p>b. go to the process tab and from dropdown select <strong>Transcode video </strong>process.</p><p>c. Add arguments as <strong>profile:myCustomProfile </strong>(name of the video profile you created above.)</p><p>3. Now we are ready, lets trigger the workflow and an additional rendition will be available under <strong>encode </strong>when you visit your video.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4-gJn9Irr-SNfXFgbq_PpA.png" /><figcaption>Video with added watermark</figcaption></figure><blockquote>If you want animation of the watermark image on video here you go with the filter</blockquote><pre>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br>&lt;jcr:root xmlns:sling=&quot;<a href="http://sling.apache.org/jcr/sling/1.0">http://sling.apache.org/jcr/sling/1.0</a>&quot; xmlns:cq=&quot;<a href="http://www.day.com/jcr/cq/1.0">http://www.day.com/jcr/cq/1.0</a>&quot; xmlns:jcr=&quot;<a href="http://www.jcp.org/jcr/1.0">http://www.jcp.org/jcr/1.0</a>&quot; xmlns:nt=&quot;<a href="http://www.jcp.org/jcr/nt/1.0">http://www.jcp.org/jcr/nt/1.0</a>&quot;<br>    jcr:primaryType=&quot;cq:Page&quot;&gt;<br>    &lt;jcr:content<br>        cq:template=&quot;/libs/dam/templates/videoprofile&quot;<br>        jcr:description=&quot;A video profile with high quality output to create watermarked videos&quot;<br>        jcr:primaryType=&quot;nt:unstructured&quot;<br>        jcr:title=&quot;Watermark FullHD (H.264 - HP - Lvl4.0)&quot;<br>        sling:resourceType=&quot;dam/components/video/profile&quot;<br>        customArgs=&quot;-loop 1 -i yourImagePAthFromServer/myWatermark.png -filter_complex overlay=x=0:y=&#39;((H+h)\/5)\*mod(t\,5)-h&#39;:shortest=1&quot;<br>        extension=&quot;mp4&quot;<br>        htmlType=&quot;video/mp4; codecs=&amp;quot;avc1.640028, mp4a.40.2&amp;quot;&quot;<br>        mimeType=&quot;video/x-m4v&quot;<br>        renditionSelector=&quot;myIdentifiableID&quot;/&gt;<br>&lt;/jcr:root&gt;</pre><pre><br>* You can play with x=0 to move the watermark image anywhere in the video.</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*RpfNV9u-H61kqVUG8BCegg.gif" /></figure><h3>Some disadvantages of processing video like this :</h3><ol><li>Video thumbnail processing is heavy operation, and therefore it can result in performance issues.</li><li>Long videos may take a lot of time to process as this thumbnail process step adds a watermark on each frame of the video.</li><li>Maintenance of the watermark image can be a challenge as it won’t be hosted in AEM DAM.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b7cf9268185" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Resource Mapping in Adobe Experience Manager (AEM)]]></title>
            <link>https://abhigyanswaroop.medium.com/resource-mapping-in-adobe-experience-manager-aem-1658653a683?source=rss-249a05c86f5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1658653a683</guid>
            <category><![CDATA[resource-mapping]]></category>
            <category><![CDATA[sling-resolution]]></category>
            <category><![CDATA[sling-mapping]]></category>
            <category><![CDATA[aem]]></category>
            <category><![CDATA[url-rewriting]]></category>
            <dc:creator><![CDATA[Abhigyan Swaroop]]></dc:creator>
            <pubDate>Sat, 11 Jul 2020 16:35:00 GMT</pubDate>
            <atom:updated>2020-07-13T08:31:27.773Z</atom:updated>
            <content:encoded><![CDATA[<p>Resource Mapping is very common and one of the extensively used solution in any technical implementation using AEM. In this article, we will try to understand the basics about it.</p><h4><strong>What is Resource Mapping in AEM?</strong></h4><p>Resource Mapping in AEM is a feature which enables AEM to define redirect, virtual host or Vanity URLs. It is used to create desired beautified URL Patterns which is clean and user-friendly in order to help make your website user-friendly and URLs, easy to remember.</p><p>For example, if an actual URL/content path in repository refers to <a href="#"><strong><em>https:www.myHost.com/Content/myHome/Homepage/contentpage.html</em></strong></a><strong><em><br></em></strong><em>with the help of resource Mapping it can be converted into a user-friendly form<br></em><a href="#"><strong><em>https:www.myHost.com/contentpage.html</em></strong></a></p><h4>How to define Resource Mapping ?</h4><ol><li>Define desire mapping pattern in <br><a href="http://localhost:4502/system/console/configMgr"><strong><em>org.apache.sling.jcr.resource.internal.JcrResourceResolverFactoryImpl</em></strong></a><strong><em><br></em></strong>You can define the set of rules which will execute and form the URLs based on the pattern you want the end users to access.<br>The list can be viewed under <a href="http://localhost:4502/system/console/jcrresolver"><strong>JCRResolver</strong></a> in AEM and can be used to resolve and test the configuration.<br>You can make a use of <strong><em>resource.resolver.mapping </em></strong><em>to create desired pattern of content path, </em>for an example, a typical mapping set-up looks like following:</li></ol><pre>&lt;?xml version=”1.0&quot; encoding=”UTF-8&quot;?&gt;<br>&lt;jcr:root xmlns:sling=”<a href="http://sling.apache.org/jcr/sling/1.0">http://sling.apache.org/jcr/sling/1.0</a>&quot; xmlns:jcr=”<a href="http://www.jcp.org/jcr/1.0">http://www.jcp.org/jcr/1.0</a>&quot;<br> jcr:primaryType=”sling:OsgiConfig”<br> resource.resolver.map.location=”/etc/map.publish”<br> resource.resolver.mapping=”[/content/myCompany/((?=us|au)[^/]+)/([^/]+)&amp;lt;/$2,/content/myCompany/((?=us|au)[^/]+)/([^/]+)/([^/]+)/([^/]+)&amp;lt;/$4]”/&gt;</pre><p>If, you notice closely, I have defined <strong>resource.resolver.map.location</strong> to,<strong>etc/map.publish</strong> That way you can even make it <strong>run mode</strong>specific, by taking advantage of the Sling OSGi Installer’s run mode awareness. More details <a href="https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#properties">here</a>.</p><p>The Above Mapping will convert on publish (as you are making use of publish run mode).</p><blockquote><strong>* (host)</strong>/content/myCompany/us/en.html -&gt; <strong>(host)/en.html</strong></blockquote><blockquote><strong>* (host)</strong>/content/myCompany/us/en/article/mySampleArticle.html -&gt;<strong>(host)/mySampleArticle.html</strong></blockquote><p>More information about each of the properties and flags for attached Image can be found <a href="https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#string-interpolation-for--etc-map"><strong>here</strong></a></p><figure><img alt="Resource Resolver Factory config" src="https://cdn-images-1.medium.com/max/1024/1*RAp_JmHRTmsgdtMlyCsDuA.png" /></figure><p>2. <strong>Testing your Configuration<br></strong>To test your Resource Resolution is working as expected, you can go to <a href="http://localhost:4502/system/console/jcrresolver">Resource Resolver</a> console in AEM and can test your URL and corresponding pattern.<br>This allows you to enter a URL or resource path. Click <strong>Resolve </strong>or <strong>Map </strong>to confirm how the system will transform the entry.<br><strong>* Resolver Map Entries </strong>The list of entries used by the ResourceResolver.resolvemethods to map URLs to Resources.<br><strong>* Mapping Map Entries </strong>The list of entries used by the ResourceResolver.map methods to map Resource Paths to URLs.</p><h4>Defining Reverse Mapping for the mapped Paths</h4><p>Now, that you have shortened the URLs for the end-users, we would need a reverse mapping in order to create an internal redirect so that correct content is served upon request.</p><ol><li>If you remember <strong>resource.resolver.map.location </strong>in the configuration we defined above, would be our location to create this reverse mapping (by default this mapping location is <strong>/etc/map</strong>).<br>A typical Reverse Resolver mapping would look like</li></ol><pre><em>&lt;?</em>xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;<em>?&gt;<br></em>&lt;jcr:root xmlns:sling=&quot;http://sling.apache.org/jcr/sling/1.0&quot; xmlns:jcr=&quot;http://www.jcp.org/jcr/1.0&quot;<br>    jcr:primaryType=&quot;sling:Mapping&quot;<br>    sling:internalRedirect=&quot;[/content/myCompany/$1/$2,/content/myCompany/us/en/article/$1/$2]&quot;<br>    sling:match=&quot;.+([^/]+)/(.*)$&quot;/&gt;</pre><p>This will convert the shortened URLs into AEM understandable path i.e. <br><strong><em>(host)/mySampleArticle.html </em></strong><strong>-&gt; <em>(host)/ </em></strong><strong><em>content/myCompany/us/en/artical /mySampleArticle</em></strong></p><p>More details on the reverse mapping can be found <a href="https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html#regular-expressions-for-reverse-mappings">here</a>.</p><p>2. If you notice closely the screen-shot attached above, we can define both forward and backward mapping as a part of <strong>resource.resolver.mapping </strong>itself.<br>Incoming mappings are applied to request paths to map to resource paths, outgoing mappings are applied to map resource paths to paths used on subsequent requests.<br>Form is &lt;internalPathPrefix&gt;&lt;op&gt;&lt;externalPathPrefix&gt; where <strong>&lt;op&gt;</strong>is</p><ul><li><strong>&gt;</strong> for incoming mappings,</li><li><strong>&lt;</strong> for outgoing mappings and</li><li><strong>:</strong> for mappings applied in both directions.<br>Mappings are applied in configuration order by comparing and replacing URL prefixes. <br><strong><em>Note: The use of “-” as the &lt;op&gt; value indicating a mapping in both directions is deprecated. (resource.resolver.mapping)</em></strong></li></ul><pre>From my experience, I would suggest creating rewrite rules in dispatcher which would make the reverse mapping lot simpler and clean.</pre><pre>For example: </pre><pre>A sample rewrite Rule </pre><pre>RewriteCond %{HTTP_HOST}    www.myCompany.com [OR]<br>RewriteCond %{HTTP_HOST}    www.beta.myCompany.com<br>RewriteRule ^/$             /en [R=permanent,L]</pre><pre>RewriteCond %{HTTP_HOST}    www.myCompany.com [OR]<br>RewriteCond %{HTTP_HOST}    www.beta.myCompany.com<br>RewriteCond %{REQUEST_URI}  ^/en$<br>RewriteRule /(.*) /content/MyCompany/us/$1.html [PT,QSA,NE,L]</pre><h4><strong><em>Some issue you could face in above implementation</em></strong></h4><ol><li>If the Resource mapping is done for child pages i.e. for above example article then the reverse mapping needs to be defined keeping the URL structure which dispatcher will hit Publish server (<em>check the dispatcher logs in this case</em>), that can be little complex.<br>2. While writing the reverse mapping, you can face, conflicting rule, which could result in 404 or incorrect redirection, therefore, always make use of <a href="http://localhost:4502/system/console/jcrresolver">JCR Revolver</a> to check your config.</li></ol><blockquote><strong><em>Useful Resources :</em></strong></blockquote><ul><li><a href="https://docs.adobe.com/content/help/en/experience-manager-65/deploying/configuring/osgi-configuration-settings.html">https://docs.adobe.com/content/help/en/experience-manager-65/deploying/configuring/osgi-configuration-settings.html</a></li><li><a href="https://docs.adobe.com/content/help/en/experience-manager-64/deploying/configuring/resource-mapping.html">https://docs.adobe.com/content/help/en/experience-manager-64/deploying/configuring/resource-mapping.html</a></li><li><a href="https://sling.apache.org/documentation/the-sling-engine/resources.html">https://sling.apache.org/documentation/the-sling-engine/resources.html</a></li><li><a href="https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html">https://sling.apache.org/documentation/the-sling-engine/mappings-for-resource-resolution.html</a></li><li><a href="https://cwiki.apache.org/confluence/display/SLING/Flexible+Resource+Resolution">https://cwiki.apache.org/confluence/display/SLING/Flexible+Resource+Resolution</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1658653a683" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Getting started with Adobe Smart Tags]]></title>
            <link>https://abhigyanswaroop.medium.com/getting-started-with-adobe-smart-tags-b8b00cfdd14e?source=rss-249a05c86f5a------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8b00cfdd14e</guid>
            <category><![CDATA[tag]]></category>
            <category><![CDATA[smart-tag]]></category>
            <category><![CDATA[adobe-experience-manager]]></category>
            <category><![CDATA[adobe-sensei]]></category>
            <category><![CDATA[adobe-tag-management]]></category>
            <dc:creator><![CDATA[Abhigyan Swaroop]]></dc:creator>
            <pubDate>Sat, 30 May 2020 19:41:56 GMT</pubDate>
            <atom:updated>2020-05-31T09:58:32.496Z</atom:updated>
            <content:encoded><![CDATA[<p>Adobe sensei offers a very powerful capability to auto-tag assets which helps the business users to quickly find the assets based on taxonomy.</p><p>In the recent years, Adobe has been making a lot of efforts to improve the assets&#39; capability and make it more interactive for both customers and business authors. In this journey, a significant push is given by using artificial intelligence (AI) and machine learning (ML) framework which enables auto tagging of assets by applying both Standard and business specific tags to imagery.<br>This capability of adobe sensei called <strong><em>Smart Tags </em></strong>can also identify content, individual words, or phrases and can automatically apply descriptive tags to them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/1*tMwEhzVTnOMSejt9kLFqqg.png" /></figure><p><em>Image courtesy : Adob</em>e</p><h4><strong><em>Prerequisite</em></strong></h4><blockquote><em>An Adobe ID account that has administrator privileges for the organization.</em></blockquote><blockquote><em>The Smart Content Service service is enabled for your organization.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/753/1*EnF9cq2LlPyUtu_8ZaqYNg.png" /><figcaption>Typical set-up</figcaption></figure><p>Basically, there are 3 main steps involved in enabling smart tags on your assets.<br>1.<a href="https://docs.adobe.com/content/help/en/experience-manager-64/assets/managing/config-smart-tagging.html"> Enable Smart tag service </a><br>2.<a href="https://docs.adobe.com/content/help/en/experience-manager-64/assets/managing/smart-tags-training-guidelines.html"> Train Smart tagging Algorithm</a><br>3. Add smart tags on your assets</p><p>Important things to keep in mind while performing above steps</p><h3><em>1. </em><strong><em>Enable Smart tag service</em></strong></h3><p><strong>a). </strong>Login to <a href="https://adminconsole.adobe.com/">https://adminconsole.adobe.com/</a> via your organization id<br>After successful login, you should be redirected to an organization overview page. Verify the organization on top Right corner, to assure you are accessing the desired organization admin console.<br><strong>b). </strong><em>In the overview link, look for “Smart Content Services”. If it appears, the service is enabled.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/367/1*aFGy6uWDuQjvwjV5KV1UlQ.png" /></figure><p><strong>c). </strong>Follow link <a href="https://helpx.adobe.com/experience-manager/6-5/assets/using/config-smart-tagging.html#Obtainpubliccertificate"><strong>o<em>btain public certificate</em></strong></a><em><br></em><strong><em>d).</em></strong><em> Follow link to</em><strong><em> </em></strong><a href="https://docs.adobe.com/content/help/en/experience-manager-65/assets/managing/config-smart-tagging.html#CreateAdobeIOintegration"><strong><em>create Adobe I/O integration</em></strong></a><strong><em><br>e). </em></strong><em>Follow link</em><strong><em> </em></strong><a href="https://docs.adobe.com/content/help/en/experience-manager-65/assets/managing/config-smart-tagging.html#configure-smart-content-service"><strong><em>configure smart content service</em></strong></a><strong><em><br>f). </em></strong><em>Follow link to</em><strong><em> </em></strong><a href="https://docs.adobe.com/content/help/en/experience-manager-65/assets/managing/config-smart-tagging.html#validate-the-configuration"><strong><em>validate the configuration.</em></strong></a></p><h3><strong><em>2. Train Smart tagging Algorithm</em></strong></h3><p><strong><em>a). </em></strong><em>Use set of approx. 30 similar looking images(preferably object in focus) with different background.<br></em><strong><em>b). </em></strong><em>Avoid using same tags on dissimilar looking images, it may lead to inaccurate tagging.<br></em><strong><em>c). </em></strong><em>Add all different tags qualifying for the asset at once and avoid multiple training session on same image as it may affect the previous trained tags.<br></em><strong><em>d). The training workflow runs on folders only.<br>e). Follow link to </em></strong><a href="https://docs.adobe.com/content/help/en/experience-manager-65/assets/administer/asset-reports.html#generate-reports"><strong><em>generate report for trained tags</em></strong></a><strong><em>.<br>f). Follow link for </em></strong><a href="https://docs.adobe.com/content/help/en/experience-manager-65/assets/administer/asset-reports.html#add-custom-columns"><strong><em>Additional column can be added to report</em></strong></a></p><h3>3. <strong>Add smart tags on your assets</strong></h3><p><strong>a). </strong><a href="https://docs.adobe.com/content/help/en/experience-manager-64/assets/managing/config-smart-tagging.html#enable-smart-tagging-in-the-update-asset-workflow-optional">Enable smart tagging in the DAM Update Asset workflow</a><strong><br>b). <em>The tagging workflow runs on both assets and folders.</em></strong><em><br></em><strong><em>c). </em></strong><em>Open the properties page of your asset folder, select </em><strong><em>Enable Smart Tags </em></strong><em>under the </em><strong><em>Details </em></strong><em>tab, and save the changes.<br></em><strong><em>d). </em></strong><em>In the subsequent tagging cycles, only the modified assets are tagged again with newly-trained tags. However, even unaltered assets are tagged if the gap between the last and current tagging cycles for the tagging workflow exceeds 24 hours. For periodic tagging workflows, unaltered assets are tagged when the gap exceeds 6 months.</em></p><h3>Limitations of Smart Tagging</h3><p>Enhanced smart tags are based on learning models of brand images and their tags. These models are not always perfect at identifying tags. The current version of the Smart Content Service has the following limitations:</p><p><em>1. Inability to recognize subtle differences in images. For example, slim versus regular fitted shirts.<br>2. Inability to identify tags based on tiny patterns/parts of an image. For example, logos on T-shirts.<br>3. Tagging is supported in the locales that AEM is supported in. For a list of languages, see </em><a href="https://docs.adobe.com/content/help/en/experience-manager-64/release-notes/smart-content-service-release-notes.html"><em>Smart Content Services release notes</em></a><em>.</em></p><p><strong>Official document:</strong><br><a href="https://helpx.adobe.com/experience-manager/6-3/assets/using/touch-ui-smart-tags.html">Smart Tags</a></p><p><em>Stay tuned for more similar quick reads.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8b00cfdd14e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>