Chapter 6 of the AEM Headless tutorial covers ensuring all the necessary packages, configuration and content are on AEM Publish to allow consumption by the Mobile App.
The configuration and content created to drive the Events through AEM Content Services must be published to AEM Publish so the Mobile App can access it.
Because AEM Content Services is built from Configuration (Content Fragment Models, Editable Templates), Assets (Content Fragments, Images), and Pages all of these pieces automatically enjoy AEM’s content management capabilities, including:
Ensure the WKND Mobile Application Packages, listed in Chapter 1, are installed on AEM Publish using Package Manager.
Publish the WKND Mobile Events API Editable Template
Publish the WKND Mobile Events content fragments.
Note that this is required as the Events API uses the Content Fragment List component, which does not specifically reference Content Fragments.
Publish the Events API page.
In a new Web browser, ensure you are logged out of AEM Publish and request the following URLs (substituting
http://localhost:4503 for whatever host:port AEM Publish is running on).
These requests should return the same JSON response as when the corresponding AEM Author end-points were reviewed. If they do not, ensure all publications succeeded (check the Replication queues), the WKND Mobile
ui.apps package is installed on AEM Publish, and review the
error.log for AEM Publish.
There are no extra packages to install. Ensure that the content and configuration outlined in this section is published to AEM Publish, else subsequent chapters will not work.