Step 1: Prepare your Adobe Environment
- On-prem clients are required to have a Cloud SDK copy of their local AEM instance.
- It is required to have the Querybuilder API enabled.
- It is required to have customized and deployed the custom Sling Model Exporter to your desired environment.
Ensure that your AEM environment meets the above prerequisites. If you do not yet have a Cloud SDK, learn more about creating an AEM Project Archetype that is compatible with the Cloud SDK. An AEM Project Archetype is a specific directory structure format that is accepted by the Adobe Cloud Repository. The Project Archetype bundle should be pushed from local to the Adobe repository for cloud deployment.
Once you have a Cloud copy, you will need to ensure that you have the Querybuilder API enabled and your site’s content is exposed to it.
Finally, you will need to deploy a custom Sling Model Exporter. A starter Sling Model can be found in our Github repo https://github.com/YextSolutions/AEM-custom-sling-model-exporter. These exporter files are built off of the default model exporter, Apache Jackson Sling Model Exporter , and will override the Jackson Exporter.
This Exporter uses the default .model extension but specifies the fields that will be returned to Yext and includes all of the text elements on your AEM page. Remember that when updating the exporter files, you need to replace your package name to match your file structure. All instances of this use the name yext or yext/yextSite.
If you need more help check out these other AEM resources: