CRXDE Lite is ONLY available on AEM as a Cloud Service Development environments (as well as the local AEM SDK).
CRXDE Lite is only accessible on AEM as a Cloud Service Development environments, and is not available on Stage or Production environments.
To access CRXDE Lite on AEM Author:
This will open CRXDE Lite using the credentials and permissions used to log in to AEM Author.
CRXDE Lite provides direct access to the JCR. The content visible via CRXDE Lite is limited by the permissions granted to your user, meaning you may not be able to see or modifying everything in the JCR depending on your access.
Note that /apps
, /libs
and /oak:index
are immutable, meaning they cannot be changed at runtime by any user. These locations in the JCR can only be modified via code deployments.
Making changes to mutable content at runtime in AEM as a Cloud Service development environments via CRXDE Lite must be done with care.
Any changes made directly to AEM via CRXDE Lite may be difficult to track and govern. As appropriate, ensure changes made via CRXDE Lite make their way back to the AEM project’s mutable content packages (ui.content
) and committed to Git, in order to ensure the issue is resolved. Ideally, all application content changes originate from the code base and flow into AEM via deployments, rather than making changes directly to the AEM via CRXDE Lite.
CRXDE Lite provides a way to test and evaluate access control on a specific node for a specific user or group (aka principal).
To access the Test Access Control console in CRXDE Lite, navigate to:
The results display below:
The following are debugging activities that can not be performed in CRXDE Lite.
Deployed OSGi configurations cannot be reviewed via CRXDE Lite. OSGi configurations are maintained in the AEM Project’s ui.apps
code package at /apps/example/config.xxx
, however upon deployment to AEM as a Cloud Service environments, the OSGi configurations resources are not persisted to the JCR, therefore not visible via CRXDE Lite.
Instead, use the Developer Console > Configurations to review deployed OSGi configurations.