Local device registration not supported with AEM Screens Cloud AMS package on AEM LTS
This article explains why local device registration isn’t supported when using the Screens Cloud AMS package on Adobe Experience Manager (AEM) LTS and provides guidance for local development and testing workflows.
Description description
Environment
- Adobe Experience Manager (AEM) LTS
- Screens Cloud AMS package
Issue/Symptoms
- After migrating to AEM LTS and installing the Screens Cloud AMS package, attempts to register devices locally on the AEM instance fail.
- The
/screens/devices.htmlpage doesn’t provide local device management functionality. - Installing previous Screens bundles on AEM LTS fails because of missing dependencies.
- Errors occur when accessing device management pages on the local AEM instance.
Cause
Local device registration and Device Manager functionality aren’t supported on AEM LTS with the Screens Cloud AMS package. Device registration and management are handled exclusively in Screens Cloud, not on the local AEM instance.
Resolution resolution
Follow the steps below to resolve the issue:
-
Don’t install previous Screens bundles alongside the current Screens Cloud AMS package on AEM LTS because this can result in unresolved dependencies and isn’t supported.
-
Use your local AEM LTS instance for authoring and previewing channels only.
-
Register and manage players and devices in your Screens Cloud environment.
-
To sync content or test playback with Screens Cloud and players using your local AEM instance:
- Expose your local AEM instance through a reachable HTTPS endpoint, for example, by using a secure tunnel that maps an HTTPS URL to your local instance.
- In your Screens Cloud environment settings, set the HTTPS URL of your local AEM instance as the content provider.
- This allows Screens Cloud to sync channels and enables players to load content from your local instance.
-
To validate playback, assign channels to the player in Screens Cloud and confirm that content loads from your local AEM instance.