Since AEM 6.1 Adobe recommends to not longer place the AEM Client Libraries below /etc/clientlibs
or /etc/designs
, but to place them below /apps
and set allowProxy=true
on it (see AEM documentation).
On the publish side there is usually no direct access to /apps
possible, thus the clientlibs are services using a proxy service via the URL /etc.clientlibs
(note the dot instead of the slash).
This article describes how to switch your AEM Client Library to this proxy mode, with a focus on applications based on the wcm.io stack.
Steps to switch an AEM Client Library to Proxy Mode
/apps/<yourapp>/clientlibs
author
and publish
below this folderSling-Initial-Content
instruction in the POM as wellfilter.xml
of the package as wellfilter.xml
of the complete
AEM package, without any content behind it.allowProxy=true
on your client libraryallowProxy=true
on all of them as well - otherwise static files from the resources
folder of the embedded libraries will not be available on publishpackage.json
or js configuration file and re-generate the client librarieslongCacheKey
property with the current project version/build number of your project, make sure to update the path to the client library for this in the POM as well./etc
and switch it to the new path below /apps
.resources
folder, and do not use full pathsio.wcm.handler.url
1.3.0io.wcm.testing.wcm-io-mock.handler
1.1.0io.wcm.handler.url
(new since 1.3.0) - see https://wcm.io/handler/url/configuration.htmlWith this in place:
/etc.clientlibs
/etc.clientlibs
The content by label feature displays related articles automatically, based on labels you choose. To edit options for this feature, select the placeholder below and tap the pencil icon.
|