Show Menu
TOPICS×

Configuring and Deploying AEM Screens

This page shows how to install and configure the Screens players on your devices and covers the following topics:
  • Installing AEM Screens Player
  • Server Configuration
  • Hardware Selection Guidelines for Player Device
  • The Next Steps

Installing AEM Screens Player

The AEM Screens player is available for Android, Chrome OS, iOS, and Windows.
To download AEM Screens Player , visit the AEM 6.4 Player Downloads page.
Once you download the latest Player ( .exe ), follow the steps on the player to complete the ad-hoc installation:
  1. Long-press on the top left corner to open the admin panel.
  2. Navigate to Configuration from the left action menu and enter the location address of the AEM instance in Server and click Save .
  3. Click on the Registration link from the left action menu and the steps below to complete the device registation process.

Additional Resources

Refer to the following topics for an in-depth information:

Server Configuration

Important :
AEM Screens player does not make use of the Cross-Site Request Forgery (CSRF) token. Therefore, in order to configure and AEM server to be ready to use for AEM Screens, skip the referrer filter by allowing empty referrers.

Prerequisites

The following key points below helps to configure and AEM server to be ready to use for AEM Screens:

Allow Empty Referrer Requests

Follow the steps below to enable the Apache Sling Referrer Filter Allow Empty. This is required for optimal operation of the control protocol between AEM Screens Player and AEM Screens server.
  1. Navigate to **Adobe Experience Manager Web Console Configuration **via AEM instance --> hammer icon --> Operations --> Web Console .
  2. Adobe Experience Manager Web Console Configuration opens. Search for sling referrer.
    For searching the sling referrer property, press Command+F for Mac and Control+F for Windows .
  3. Check the Allow Empty option, as shown in the figure below.
  4. Click Save to enable the Apache Sling Referrer Filter Allow Empty.

Enable Touch UI for AEM Screens

AEM Screens requires TOUCH UI and will not work with CLASSIC UI of Adobe Experience Manager (AEM).
  1. Navigate to <yourAuthorInstance>/system/console/configMgr/com.day.cq.wcm.core.impl.AuthoringUIModeServiceImpl
  2. Ensure that the Default authoring UI mode is set to TOUCH , as shown in the figure below
Alternatively, you can also perform the same setting using*<yourAuthorInstance> -> tools (hammer icon)* -> Operations -> Web Console and search for WCM Authoring UI Mode Service .
You can always enable Classic UI for specific users using user preferences.

AEM in NOSAMPLECONTENT runmode

Running AEM in production uses the NOSAMPLECONTENT runmode. Remove the X-Frame-Options=SAMEORIGIN header (in the additional response header section) from
This is required for the AEM Screens Player to play online channels.

Password Restrictions

With latest changes to DeviceServiceImpl , you do not have to remove the password restrictions.
You can configure DeviceServiceImpl from the link below to enable password restriction while creating the password for the screens device users:
Follow the steps below to configure DeviceServiceImpl :
  1. Navigate to Adobe Experience Manager Web Console Configuration via AEM instance --> hammer icon --> Operations --> Web Console .
  2. Adobe Experience Manager Web Console Configuration opens. Search for deviceservice. For searching the property, press Command+F for Mac and Control+F for Windows .

Dispatcher Configuration

For **Dispatcher, **add client headers to .any file. Allow the following headers through:
  • "X-Requested-With"
  • "X-SET-HEARTBEAT"
  • "X-REQUEST-COMMAND"

Java encoding

Set the Java encoding to Unicode. For example, Dfile.encoding=Cp1252 will not work.
Recommendation:
It is recommended to use HTTPS for AEM Screens Server in production use.

Hardware Selection Guidelines for Player Device

The following section provides the hardware selection guidelines for a Screens Project:
  • Always source Commercial or Industrial Grade components for both PC player and Display Panel or Projector.
  • Always engage with vendors who serve the digital signage market.
  • Always consider environmental factors such as ambient temperature and relative humidity.
  • Always review power requirements and power conditioning.
  • Carefully review performance needs and I/O ports required for application.
The following table summarizes the hardware configurations with typical use cases for an AEM Screens project:
Player Configuration Processor Memory Storage SSD GPU Display I/O Typical Use Cases
Basic Dual Core, i3 or entry-level quad core Intel® Atom Processor
4GB of memory
2MB of cache
•ChromeOS 32 GB
•Windows 128GB
OnBoard 1920 x 1080 DVI, Ethernet / Wireless, 2xUSB
  • Standard Full Screen Looping
  • Day Parting
Standard Quad Core, Intel® Core i5 processor
8GB of memory
4MB of cache
128 GBB OnBoard 3840x2160 (4K) DVI, HDMI Ethernet / Wireless, 2xUSB
  • Single Source Dynamic Content
  • Simple Interactive
  • 1-3 Zone layouts
Advanced Quad Core with hyperthreading, Intel® Core i7 processor
16GB of memory
8MB of cache
256 GB Discreet GPU 3840x2160 (4K) DVI, HDMI Ethernet / Wireless, 4xUSB
  • 4 or more Content Zones, Concurrent Video Playback
  • Multi-Page Interactive
  • Multi-Source Data Triggers