Top Features in Adobe Experience Manager (AEM) 6.3 version

              Adobe has announced the official release of its new version Adobe Experience Manager AEM 6.3 on 27-Apr-17 after the release of AEM 6.2 which happened in 2016. 

It consists of all the Service pack and hot fixes of AEM 6.2 along with many more key fixes.

Features got introduced in Adobe Experience Manager 6.3:-

  • Introduction to Production-ready components:- Faster time-to-market with Adobe-vetted, production-ready components based on best practices.
    aem6.3_core_components-min

  • Experience fragments: Composition and delivery of experiences to both owned web properties and affiliated properties, like Pinterest and Facebook.
    aem6.3_experience_fragments_dashboard-min

  • Stable online revision Clean up(online tar compaction):- From limited support to full support for online revision clean up. As customers are regularly forced to shut down their AEM production environments for maintenance which prevents them from publishing content during that time. (Up to 4 hours a week).

  • Bulk workflow: Increased productivity with faster workflow-related tasks and ability to process multiple items in one click.

  • Performance and scale enhancements: Empower your teams to work more productively and efficiently with a broad range of enhancements to support large scale operations—including bulk ingestion, workflow processing, video processing and encoding, handling large files, repositories, and more.

  • Community ideation: New community engagement mode to source and surface the best ideas crowd-sourced from the community. Community can vote and rank to help prioritize and highlight the best content.
    AEM6.3_commerce_dashboard-min

  • Source user generated content: Livefyre is now fully integrated within Experience Manager, enabling marketers to rapidly discover, filter and manage user-generated content into the central repository of Experience Manager. Unlock the power of user-generated content from social sites such as Twitter, Facebook, Instagram and tell your brand’s most authentic and engaging story.

  • 3D assets: Repurpose 3D assets to accelerate time to market and save on production costs. Upload, manage, view, and render 3D content created from Creative Cloud or many popular 3D applications. Easily rotate, zoom, change colors, textures, backgrounds (stages) and lighting on 3D objects to create a new set of images from an infinite number of camera angles to use in digital marketing campaigns.

  •  Asset templates: Leverage self-service templates based on Adobe InDesign to create and export brochures, flyers and print ads that speeds time to market while complying with brand guidelines.

  • High-quality file format and color management: Experience Manager now uses Photoshop and Acrobat-quality image and PDF libraries to support high quality file operations such as conversion, previewing, raster and creating thumbnails and preserving color and embedded color profiles, using Adobe ICC profiles or your own. Deliver images with RGB, CMYK or grayscale so your digital assets look bright and beautiful across channels.

For More Information go through below Links:-

AEM CQ5 Tutorial for Beginners - AEM CQ5 Tutorials


Below Index consist of all topics in sequence that a beginner of AEM should follow to learn the technology very easily.

Introduction:-

Basics for AEM Developer

HTL (HTML Template Language) formerly known Sightly

Advanced AEM Developer

AEM System Administrator

Troubleshooting AEM

AEM Integrations

AEM Programs

Interview Questions for AEM

OTHER MISCELLANOUS TOPICS:-

Create AEM Page with predefined components


                Templates and components are core assets/building blocks of any AEM project and they provide capability for content authors to update pages/content on the fly.

                       Many times we want to create pages with some default components configured on our newly created page with an option for authors where they can remove any component (if it is not required on that page).

Let’s consider a scenario / use case where this can be achieved. 
Let’s say we have a photo album site where author can create new albums/pages using a photo album template. 
A photo album page has some space reserved on right hand side for displaying popular images and newly added images. Both of these components are dropped inside a parsys.


                       Now, if author wants to create an album page he needs to create a page and then drop components one by on the newly create page. Is there a way to have a page refilled with all the components so that author doesn’t need to add them one by one? Yes, this is what we are going to cover in this article.

Follow these steps to have a template preconfigured with some default components:

  • Create a new page and drop all required components on that page. In our case, we’ll create a new album page and will drop “photo album”, “popular images” and “newly added” component.
  • Go the CRXDELite and explore the newly created page and nodes under it. You’ll see that with there are 2 parsys nodes one of them has “photo album” and another parsys node have “popular images” and “newly added” component nodes.
  • Go the template in apps folder using which page has been created (e.g. (/apps/photogallery/templates/albumpage) and as you can see it by default contains “jcr:content” node.
  • Now copy both parsys nodes from album page that we have created in step#1 to jcr:content node of template (albumpage). At this point the structure of jcr: content should match the with node structure of actual album page.
  • Create a new album page using the same template (i.e. (/apps/photogallery/templates/albumpage) and now when you open the page you’ll see that newly created page already contains all the components on it.


                   A template node in CQ/AEM is of type cq:template and its default behavior of node is doing all the work which is required. 
So whatever properties/nodes that we have at template’s jcr:content level will be copied over to a newly created page’s node. 

Adobe CQ/AEM Useful Links


  1. CRX Explorer - /crx/explorer/index.jsp
  2. CRXDE Lite - /crx/de/index.jsp
  3. DAMAdmin - /damadmin
  4. SITEAdmin - /siteadmin 
  5. Query debug tool - /libs/cq/search/content/querydebug.html
  6. Content sync console - /libs/cq/contentsync/content/console.html – 
  7. User manager - /libs/granite/security/content/admin.html – 
  8. Felix Bundles console - /system/console/bundles
  9. Felix admin console JMX / Workflow maintenance tasks - /system/console/jmx/com.adobe.granite.workflow%3Atype%3DMaintenance - 
  10. Felix web admin console JMX / Repository maintenance tasks - /system/console/jmx/com.adobe.granite%3Atype%3DRepository
  11. /system/console/depfinder – This new 5.6 tool will help you figure out what package exports a class and also prints a Maven Dependency for the class.
  12. /libs/granite/ui/content/dumplibs.rebuild.html?rebuild=true – For debugging caching problems. Wipes the clientlibs and designs, and force it to rebuild it.
  13. /system/console/adapters – Shows Adapters registered in the system. This in return helps you to figure out what you can adaptTo() from resource to resource.
Note: - 
wcmmode=DISABLED - This handy publisher parameter turns off CQ authoring features so you can preview any page.

Top Features in Adobe Experience Manager AEM 6.2

          Adobe announced the official release of new version Adobe Experience Manager 6.2 on 21-Apr-16 after the release of AEM 6.1 which happened in 2015 year. 

It consists of all the Service pack and hotfixes of AEM 6.1 along with many more customer key fixes.

Highlights:-

  • UI interface enhancements.
  • Support for Mongo DB Enterprise 3.2 is added as a part of repository enhancement.
  • Procedural failover support is added for cold standby tarmk architecture.
    Note:- Currently it is manual. Click here to see how to setup cold standby in aem.
  • Priority-Queuing configuration is introduced to prioritize urgent activation with low priority activations.
  • Package replication can be done from package manager itself. No need to activate individual pages.

User Interface Improvements:-

  • Navigation has been moved from side rail to overlay, to provide more viewable area for actual work.
ui navigation improvment aem 6.2

  • Search is moved to top bar, for easy and quick searching in all areas of product.
ui search improvment aem 6.2

  • Dashboard for monitoring queries (http://localhost:4502/libs/granite/operations/content/monitoring/page.html).
live query dashboard monitoring aem 6.2

AEM Communities Enhancements:-

Few of key enhancements are:-
  • Blogs are enhanced for blogging and commenting on publish-nodes.
  • Q&A enhancement for questions and best answer identification.
  • Adobe Analytics integration with built-in reporting dashboard.

AEM Content Fragment Enhancements:-

Rich Text page editor in AEM Touch UI has been enhanced to support Content Fragments. Content Fragment a name suggests seperates the content into fragments that can be reused and provides the ability to manage text-based content and it’s associated assets.
  • Stored as Assets: Content fragments can be created and maintained from the AEM Assets console.
  • The Content Fragment component is available to page authors. It allows them to reference the required content fragment.
  • Content Fragment can contains –
    • Text elements
    • References to associated assets (for example, images, videos, other fragments)
content fragment enhancement aem 6.2

Template Editor and Policies AEM Site Enhancement:

Templates are used in aem to provide consistent page structure through out the project. Template console and Editor is one of the main feature that is shipped with aem 6.2.
  • Template console allows content  authors to:
    • Create a new template (either new or by copying an existing template).
    • Manage lifecycle of the template.
  • Template editor allows content authors to:
    • Add (available) components to the template and position them on a responsive grid.
    • Pre-configure the components.
    • Define which components can be edited on the resultant pages (created from the template).
aem 6.2 site template policy enhancement
Note:- Template console and editor is only available in Touch UI.

At last AEM 6.2 comes up with lot of UI and security enhancements.

Subscribe to: Posts (Atom)