AEM/CQ5

Component console in AEM 6.5

Use Case: Developers and Admin can centrally manage all components in a single place i.e component console.

Highlights/Features:

Component Overview - It will list of all installed components available on the current AEM instance.
Component Properties - this tab will displays metadata like the title, group ,icon, description of a component, resource type ,resourceSuperType, created date and created by.
Component Policies - It will display any existing policies for a given component and the template associated.
Live Usage - It shows the list of pages, content fragments, experience fragments in which the component is included.

URL to access the component console :
It can be accessed from Tools -> General -> Components

http://localhost:4502/libs/wcm/core/content/sites/components.html

How to Improve AEM Workflow Throughput

statement :

How to Improve AEM Workflow Throughput after change in hardware size upgrade.

step 1 tuning : http://localhost:4502/system/console/configMgr and search for Apache Sling Job Thread Pool

PID is org.apache.sling.event.impl.EventingThreadPool. The default value is 35.

Raise this default value to higher number say 65.

Step 2 tuning : navigate to /system/console/slingevent and search for Max Parallel attribute of Job Queue

Edit the [Job Queue Configuration] for [Granite Workflow Queue],
Edit the job queue [Granite Transient Workflow Queue],
[Granite Workflow External Process Job Queue] or
Edit the job queue of any other job queue of type ‘Topic Round Robin’ that is relevant to your workload.
Increase the value for ‘Max Parallel’. The default value is usually 0.5 (half the number of vCPUs of your instance).

to find out the numbe of processor of your instace: http://localhost:4502/system/console/vmstat

based on the no of processor, default value to be changed to the half the number of processor if processor value is 4 then Max parallel value would be 2.

AEM 6.5 New features

Top features of AEM 6.5

Connected DAM (Digital Asset Management) ...
Adobe Asset Link Extension with AEM Assets. ...
Integrate Adobe Assets with Adobe Stocks. ...
Brand Portal Capabilities. ...
Adobe Experience Manager SPA (Single Page Application) Editor. ...
Smart Crop. ...
Visual Search. ...
Headless Content Delivery.
Automated Forms Conversion
Reusing Workflow Across Multiple Adaptive Forms
Magneto and Experience cloud integration
Content and Experience fragments enhancements

1. Connected DAM

In a large scale enterprise, there may be two AEM instances running in parallel.
A common scenario where this happens is when one instance is used as an AEM Site Author, executed by the AEM Site Team,
while the second instance is used by the creative team to store assets, referred to as Assets Author instance.
With a connected DAM, Site authors can search, drag & drop, save, and publish assets directly even though the asset is on a different instance. It allows site authors to access from remote AEM assets instance.
A Digital Asset Management (DAM) platform gives you a central hub for organizing, storing, and retrieving rich media.
AEM Sites offer capabilities to create web pages and AEM Assets in the DAM system that supplies the required assets for websites.
AEM now provides the capability to use assets from a connected DAM which is running in a completely different AEM instance.

Seamless connection

Site Author(web,mobile) <--------connected dam--------=""> DAM Author (Image,video..etc)

Sites Team <--------------------------------------> Creative Team

It offers unified, easy-to-use access to all owned assets, no matter where they are stored.

This is ideal for a growing number of businesses that need a central, standalone DAM with AEM Assets.

Limitations:

This feature is only supported on Adobe Managed Services.

The AEM site can connect with only one AEM Assets repository.

License is required for remote Asset repository.

There is no API support to customize the integration