Typical stakeholder for this activity is an AEM Implementor.
Follow the sections below to set up AEM platform configurations to get started with AEM Screens.
To set up server configurations, refer to Server Configurations.
To set up author-publish, refer to Configuring Author and Publish in AEM Screens
If there is only one author and one publish you only need to follow the steps under Setting up Replication Agents on Author in Configuring Author and Publish in AEM Screens page.
Dispatcher is Adobe Experience Manager’s caching and/or load balancing tool. Using AEM’s Dispatcher also helps to protect your AEM server from attack. Therefore, you can increase the security of your AEM instance by using the Dispatcher in conjunction with an enterprise-class web server.
Refer to Dispatcher Configurations for AEM Screens that highlights guidelines for configuring dispatcher for an AEM Screens project.
Install FFMpeg following the steps for the appropriate OS (usually RHEL):
If installing by enabling EPEL and RPMFusion, you can install all the gstreamer codecs to broaden support for FFmpeg conversions
If the AAC codec is marked as experimental, ffmpeg conversions will fail. To avoid this add -strict -2 to the video profiles (/etc/dam/video%20in%20AEM%206.3%20and%20moved%20to%20/libs/settings/dam/video%20in%20AEM%206.4?lang=en)
Please note that -strict -2 needs to be the last parameters in the list of parameters. Additionally in AEM 6.4 you need to copy the nodes under /libs/settings/dam/video to /conf/global/settings/dam/video as mentioned in Video Renditions.
Verify that video conversions are happening and that renditions are being created.
The password policy of AEM needs to be disabled on the AMS instance. This can be alternately configured in the web console using the Screens device service com.adobe.cq.screens.device.impl.DeviceService
Refer to Password Restrictions section inConfiguring Author and Publish in AEM Screens
Install and run the most current versions of the following packages for your version of Adobe Experience Manager (AEM):
In addition to the above, identify any development packages (for example, WCM Core
components) or third-party toolkits (for example, SAP Hybris) that are required.
Install the same software packages on your local development environments. Instruct your client to adopt the same configuration on all of their QA, Stage, and Production servers. Mismatched server configurations will create problems when deploying and testing.
To install the latest Feature Pack for AEM Screens, refer to Release Notes.
Setting up ACLs explains how to segregate projects so that each individual or team handles their own project.
Refer to Setting up ACLs for more details.