This section describes how to install AEM Screens players that are registered to on-premise AEM instances. Additionally, you must do a factory reset of the existing player and then register the new player against AEM Screens as a Cloud Service.
This document helps you understand how to setup your player before registering the players. After reading you should be able to understand:
Once you have downloaded the latest player from AEM Screens Player Downloads,you are now ready to update your player to Cloud mode.
Follow the steps below to update your player:
Open AEM Screens player.
You can choose to test with dedicated hardware devices or with a web extension on your own player.
Click the Configuration tab and click on To Factory button under Reset option.
Click on Confirm to reset your player.
Again from the Configuration tab and click on Change to Cloud Mode button under Toggle Runmode option.
Click on Confirm that prompts when switching to cloud mode will un-register the player.
The player reports various playback metrics with each
ping that defaults to 30 seconds. Based on these metrics, we can detect various edge cases such as stuck experience, blank screen, and scheduling issues. This lets us understand and troubleshoot issues on the device, and thus expedites an investigation and corrective measures with you.
Basic Playback monitoring in an AEM Screens player allows us to:
Remotely monitor, if a player is properly playing content.
Improve reactivity to blank screens or broken experiences in the field.
Decreases the risk of showing a broken experience to the end user.
The following properties are included in each
|id||the player identifier|
|activeChannel||currently playing channel path, or null if nothing is scheduled|
|activeElements||comma-separated string, currently visible elements in all playing sequence channels (multiple in case of a multi-zone layout)|
|isDefaultContent||true if the playing channel is considered a default or fallback channel (that is, has priority 1 and no schedule)|
|hasContentChanged||true if the content changed in the last 5 minutes, false otherwise|
|lastContentChange||timestamp of the last content change|
Optionally, a more advanced property can be enabled from the player preferences (Enable Playback Monitoring) and that is:
|isContentRendering||true if the GPU can confirm it is playing actual content (based on pixel analysis)|
Few limitations to basic playback monitoring are listed below:
The player reports its own playback state to the server, so it requires an active connection.
isContentRendering property that checks the GPU is currently too resource intensive to be enabled by default and requires explicit opt-in from the player preferences. It is recommended not to use it in conjunction with videos in production.
This feature is only supported for sequence channels and does not yet cover the interactive channels (SPA) use case.
The metrics are not yet fully exposed to our customers, we are working hard on enabling dashboard-like reporting and alerting mechanism in the near future.
Now, that you have installed and configured the player to Cloud mode, you should continue your Screens as a Cloud Service journey by next reviewing the document, Registering Players in Screens as a Cloud Service from Screens Services Provider.