- Tutorial Overview
- Part 1 - Installing AEM Content Services
- Part 2 - Defining FAQ Content Fragment Models
- Part 3 - Authoring FAQ Content Fragments
- Part 4 - Defining Content Services Templates
- Part 5 - Authoring Content Services Pages
- Part 6 - Exposing the Content on AEM Publish
- Part 7 - Consuming AEM Content Services from a 3rd Party App
Content Fragment Models must be enabled via AEM's Configuration Browser.
If Content Fragment Models are not enabled for a configuration, the Create > Content Fragment button will not appear for the relevant AEM configuration.
AEM's configurations represent a set of context-aware tenant configurations stored under /conf. Typically AEM configurations correlate with a particular Web site managed in AEM Sites or a business unit responsible for a sub-set of content (Assets, Pages, etc.) in AEM.
In order for a configuration to affect a content hierarchy, the configuration must be referenced via the cq:conf property on that content hierarchy. (This is achieved for the We.Retail configuration in Step 5 below).
Wehn the global configuration is used, the configuration applies to all content, and cq:conf does not need to be set.
Select Content Fragment Models, and tap Save & Close in the top right.
This enables of Content Fragment Models on Asset Folder content trees that have the We.Retail configuration applied.
This configuration change is not reversible from the AEM Configuration Web UI. To undo this configuration:
- Open CRXDE Lite
- Navigate to /conf/we-retail/settings/dam/cfm
- Delete the models node
Any exising Content Fragment Models created under this configuration will be deleted as well as their defintions are stored under /conf/we-retail/settings/dam/cfm/models.
Apply the We.Retail configuration to the We.Retail Assets Folder to allow Content Fragments from Content Fragment Models to be created within that hierarchy:
- Navigate to AEM > Assets > Files
- Select the We.Retail folder
- Tap the Properties button in the top action bar to open Folder Properties
- In Folder Properties, tap the Cloud Services tab
- Verify the Cloud Configuration field is set to /conf/we-retail
- Tap Save & Close in the upper-right to persist changes
In earlier AEM 6.3 versions, this value had to be set via CRXDE Lite or via package deployment on the Asset folder's jcr:content node's cq:conf property.
The Property Name denotes the JCR property name where this value will be stored. This should be a semantic name that is will not change over the life of the Content Fragment Model.
Optionally, install the aem-content-service-tutorial.part2 solution package via AEM's Package Manager. This package contains the configurations and content outlined in this part of the tutorials