Instructions

1. Create a cq:ClientLibraryFolder node

JCR Path: /apps/sourcedcode/clientlibs/cllienlib-site
Separate code from content and configuration to maximize project file oranization and separation of concerns, Adobe recommends to place client libraries under /apps and expose these client libraries via the path, /etc.clientlibs, by leveraging the allowProxy property.

When allowedProxy is enabled, we instead of accessing the client library from /apps/sourcedcode/clientlibs/cllienlib-site, we can access the cliebt library from the proxy servlet via /etc.clientlibs/sourcedcode/clientlibs/cllienlib-site.

2. Create a nt:folder node named “resources”

JCR Path: /apps/sourcedcode/clientlibs/cllienlib-site/resources
By convention, the client library “resource” folder is named as “resources”; which the naming is very important if structural static assets are planned be served from a client library. This setup allowes structural static assets to be accessed via the proxy.
Example: /etc.clientlibs/sourcedcode/clientlibs/cllienlib-site/resources/tick.svg

3. Place the assets under the “resources” folder

In this example, we will only insert one asset image, tick.svg.
JCR Path: /apps/sourcedcode/clientlibs/cllienlib-site/resources/tick.svg

4. Build and Upload into AEM

This default maven profile should be a part of the maven AEM Project Archetype.

Results: Review the JCR

A successful project build and deploy should make JCR node resources available in the AEM environment.

Results: Access the Asset(s)

The images can be resolvable via the proxy servlet, replacing /apps with /etc.clientlibs.
Visit: http://localhost:4502/etc.clientlibs/sourcedcode/clientlibs/cllienlib-site/resources/tick.svg

The post How to Serve Static Assets in AEM as Client Library Resources appeared first on Sourced Code.

Structural assets should be stored and managed within the client library’s resources folder by the code package, and not in AEM Digital Assets Manager (DAM) “as content”. The AEM DAM is a very flexible AEM product where it allows users & groups to freely manage (based on ACL permissions) assets to make available for the public. Sometimes developers may find the ease of storing structural assets in the DAM (with the help of content authors), so they can quickly make the structural asset publically available for consumption. But, in fact, this is the wrong pattern to follow.

The reason why structural assets should not be stored “as content” and managed as DAM assets because:

• It would be surfaced to AEM content authors (the customers) during image selection when they are editing an AEM page that requires an AEM DAM asset; they can be confused, and they can potentially select on the structural asset (because it’s available for selection).
• It opens opportunities for interruption of our CSS styles or JavaScript view logic; where authors can actually delete/update a structural asset, and the website may look like its broken.
• It would kickstart workflows; creating thumbnails, preview renditions, meta-data extractions, and other workflow processes… These are unnecessary asset processing… we do not want any thumbnails or renditions for the structural asset.
• Code like CSS styles or JavaScript logic referenced assets “as content” is not ideal, as DAM assets are maintained by authors, and can be unpredictability changed at any time.

The post Structural Static Assets in AEM as Client Library Resources appeared first on Sourced Code.

Every time when a new asset is installed (via the package manager) or uploaded into AEM, the OOTB (out of the box) AEM workflow launchers will be triggered. During the operation/processing of these assets, the author instance will start consuming the CPU, and the environment may be slowed down, depending on the number of assets being processed at the time.

Since all your assets have already been processed by another AEM author environment, it would not make sense for each asset to again be processed; this will be a waste of usage of the CPU.

I am recommending that if a large amount of AEM DAM assets (that already been processed, zipped in a content package) are being installed via package manager into a production live environment, to inform or disable all authors to stop authoring within a time frame. Within the time frame, disable the workflow launchers and install the assets into the production AEM instance. Finally, re-enable the workflow launchers after all assets have been successfully installed.

To enable/disable workflow launchers, check out this article. How to enable/disable AEM Workflow Launchers

The post Strategy to Consider when Migrating a Large Amount of Assets into an AEM author Instance appeared first on Sourced Code.

During appropriate understanding, we may need to disable workflow launchers services; always remember to re-enable after disabling these services.

1. Disable AEM Workflow Launchers

a. Open the AEM system console component page:

b. Use Google Chrome, Firefox, or other browsers to quickly find text on a page. Control(or CMD on Mac) + F to find the fully qualified java name below. Click on the “stop” button to disable each workflow service.

This is an example of how the services will look when they are found:

You will be redirected to the services detail page when 
the stop button have been clicked on. Refresh the package, 
and you will be redirected back to the component services list page:

2. Disable AEM Workflow Launchers with cURL

Use the cUrl command to “disable” AEM workflow launchers:

3. Enable AEM Workflow Launchers

a. Open the AEM system console component page:

b. Use Google Chrome, Firefox, or other browsers to quickly find text on a page. Control(or CMD on Mac) + F to find the fully qualified java name below. Click on the “start” (play) button to disable each workflow service.

This is an example of how the services will look when they are found:

You will be redirected to the services detail page when 
the start button have been clicked on. Refresh the package, 
and you will be redirected back to the component services list page:

4. Enable AEM Workflow Launchers with cURL

Use the cUrl command to “enable” AEM workflow launchers:

The post How to enable/disable AEM Workflow Launchers appeared first on Sourced Code.