How to Disable the Minification for specific client libraries(Java Script/CSS) in AEM
Minification refers to the process of removing unnecessary or redundant data without affecting how the resource is processed by the browser — e.g. code comments and formatting, removing unused code, using shorter variable and function names, and so on.
Minfication helps to reduce the size of the resources(Java Script and CSS) and improves the performance of page loading.
Sometimes we may required to disable the minifcation for specific Java script files may be due to the files are already minified or the issue with minification process.
There are two options to disable the minification for Java Scripts and CSS in AEM
Disable through Adobe Granite HTML Library Manager — Disable the minification globally for JS and CSS, this will impact all the client libraries in the system(both default and custom)
Disable Minfication for specific client libraries — Disable the minification for specific client library — JS/CSS, this will impact only the specific client library where this configuration is enabled.
Disable through Adobe Granite HTML Library Manager
Un-select minify option in Adobe Granite HTML Library Manager through configMgr(http://localhost:4502/system/console/configMgr/com.adobe.granite.ui.clientlibs.impl.HtmlLibraryManagerImpl)
Please note this is a global configuration and it will impact all the client libraries, non of the client libraries will be minified now and this will impact the performance. This approach is not recommended as this will disable the minification for all the custom and default system level client libraries.
To disable CSS Minification — add cssProcessor String[] default:none, min:none
Disabling the minification at global level is not recommended as this will impact the over all impact the website performance, enable the configurations to required client libraries to disable the minification for JS/CSS.
This tutorial explains the details on AEM re-fetching flush agent and how to use to flush the content through re-fetching flush agent.
Re-Fetching Flush Agent
With regular flush agent, the agent flush the cache and the flushed content would only be retrieved from the publisher again after first time requested. This will create issue if the multiple parallel requests hit the dispatcher after flush as the new page is not yet cached in the dispatcher.
The re-fetching flush agent in AEM make sure the pages are requested and cached on the dispatcher immediately after replication.
Using a re-fetching flush agent allows to pre-populate the cache as it instructs the dispatcher to retrieve the pages from publish instance immediately after the flush occurs. Re-fetching flush agent works same as normal flush agent in dispatcher, additionally dispatcher sends a GET request for the content paths in the flush requests to fetch the content and update the cache.
Re-fetching flush is slow when activating lot of pages, enable the re-fetching only for specific content that is frequently accessed and activated.
The re-fetching feature is available in dispatcher since version 4.0.9
Configure Re-Fetching Flush agent
As a first step, develop a content builder that will send the flush URL’s into the flush request part of request body. The flush agent uses POST method to invoke dispatcher flush.
The sample content builder bundle can be downloaded from the below URL
The agent bundle is tested with AEM as Cloud Service Development Instance with aem-sdk-api dependency, the same can be modified to use uber-jar dependency.
Install the bundle to publisher as configuring the flush agent in the publish server is recommended— mvn clean install -PautoInstallBundle -Daem.port=4503
Now new serialization type “Re-fetch Dispatcher flush” is enabled while configuring the agents.
Define a re-fetching flush agent in publisher with required details, the process is same as normal flush agent with some additional configurations
In Settings tab select the “Serialization Type” as “Re-Fetch Dispatcher Flush”
In Extended tab add POST as the HTTP Method for sending the request to Dispatcher
In AEM Cloud Service, content is published using Sling Content Distribution . The replication agents used in previous versions of AEM are no longer used or provided, configure the required forward agent configurations to distribute the changes.
Refer the below URL for details on configuring forward distribution
Now distribute/activate a page and verify the Re-Fetching Flush Agent, the activated page is updated in dispatcher before first time requesting the page.
The re-fetching flush agent will helps to improve the performance of the frequently used critical pages, be cautious while using this feature as so many page activation will impact the AEM performance.
