AEM as cloud service/ AEM Assets/ CQ5/AEM 6 hacks /Interview Questions

    Use Case: Search for similar assets in AEM DAM/Azure Storage using the FAISS vector database. For example, searching for images classified as male. This approach is particularly useful when metadata is unavailable for a given set of assets and duplicate/similar assets needs to be searched. Overview Fetch Images : Retrieve images from the repository. Filter Images : Use face detection and gender classification to filter the images. Extract Features : Convert the filtered images into feature vectors. Index and Search : Index these feature vectors using FAISS and find similar images. Prerequisites for Local Setup : An AEM instance with assets in DAM, Python, FAISS installed, and necessary Python libraries. Models Used ResNet50 : A deep learning model utilized for extracting features from images. The final classification layer is removed to use only the feature extraction part. Steps 1. Fetch Images from AEM DAM The script retrieves images from the AEM DAM. 2. Image Processing Face Det

  AEM developers need frequent upgrades as a necessity to ensure that your environment remains up-to-date with the latest features and fixes.  Prerequisites Make sure to download the latest version of the AEM local sdk package Ensure you already have a local instance of older version of AEM local sdk version. Script Overview This Windows batch script performs the following actions: Extracts the JAR File : Prompts you to enter the path to a ZIP file containing the new JAR file. It then extracts the ZIP file to a temporary folder and identifies the JAR file. Replace JAR : Checks if a older version JAR file already exists in the AEM installation directory. If it does, the script deletes the old JAR file and copies the new version JAR file to the installation directory. Execute New JAR : Opens a new Command Prompt window, navigates to the AEM installation path, and executes the new JAR file. The script will wait for 5 minutes to allow the JAR file to complete installation. During this time

Are you facing such errors while migrating to AEM 6.3 : osgi bundle whitelist error-osgi-service is NOT whitelisted to use SlingRepository.loginAdministrative Here is a quick hack but please ensure not to use it in production I believe most of the AEM developers are aware that ResourceResolverFactory.getAdministrativeResourceResolver   and   SlingRepository.loginAdministrative   methods have been defined to provide access to the resource tree and JCR Repository .  Consequently the following methods are being deprecated  ResourceResolverFactory.getAdministrativeResourceResolver ResourceProviderFactory.getAdministrativeResourceProvider SlingRepository.loginAdministrative and alternatively we started using service authentication method  getServiceResourceResolver to get the resourceResolver and then making a systme user and mapping service with user in felix congigurations. like this  < service - name > [: < subservice - name > ]= < authorizable id of

You can add combobox widget with xtype as "combo" in the custom component dialog and add the property  editable  ,value= true. For events and other functions you can refer to https://docs.adobe.com/content/docs/en/cq/5-6-1/widgets-api/index.html

Add the list of styles as given below and then in your css file add the check mark image in css rule corresponding to the class name e.g  .className1{ background:url(check.png) 10px 0px  }       jcr:primaryType="cq:Widget"                     fieldLabel="Text"                     height="200"                     name="./text"                     xtype="richtext">                     <rtePlugins jcr:primaryType="nt:unstructured">                         <styles                             jcr:primaryType="nt:unstructured"                             features="*">                             <styles jcr:primaryType="cq:WidgetCollection">                                 <className1                                     jcr:primaryType="nt:unstructured"                                     cssName="className1"                                     text=

Make sure you have  editorType="text" or editorType="textImage" property  added to the inlineEditing node. Refer to xml below: <jcr:root xmlns:cq="http://www.day.com/jcr/cq/1.0" xmlns:jcr="http://www.jcp.org/jcr/1.0" xmlns:nt="http://www.jcp.org/jcr/nt/1.0"     cq:actions="[text:Text/Image,-,EDIT,DELETE]"     cq:dialogMode="floating"     cq:layout="editbar"     jcr:primaryType="cq:EditConfig">     <cq:inplaceEditing         jcr:primaryType="cq:InplaceEditingConfig"          active="{Boolean}true"         editorType="text" >         <config jcr:primaryType="nt:unstructured">             <rtePlugins jcr:primaryType="nt:unstructured">                 <subsuperscript                     jcr:primaryType="nt:unstructured"                     features="*"/>             </rtePlugins>         <