DocumentationAEMAEM Screens Best Practices Guide

AEM Platform Configurations platform-configurations

Last update: Mon Apr 15 2024 00:00:00 GMT+0000 (Coordinated Universal Time)

CREATED FOR:

  • User
NOTE
Typical stakeholder for this activity is an AEM Implementor.

Get started with AEM Screens by following the sections below to set up AEM platform configurations

Server Configurations server-configurations

To set up server configurations, see Server Configurations.

Author-Publish author-publish

See Configuring Author and Publish in AEM Screens.

NOTE
If there is only one Author and one Publish, you only follow the steps under Setting up Replication Agents on Author in Configuring Author and Publish in AEM Screens page.

Dispatcher Configurations dispatcher-configurations

Dispatcher is Adobe Experience Manager’s caching and 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 with an enterprise-class web server.

See Dispatcher Configurations for AEM Screens that highlights guidelines for configuring Dispatcher for an AEM Screens project.

Installing FFMpeg and Video Renditions installing-ffmpeg

Install FFMpeg following the steps for the appropriate OS (usually RHEL):

  1. If installing by enabling EPEL and RPMFusion, you can install all the gstreamer codecs to broaden support for FFmpeg conversions

  2. If the AAC codec is marked as experimental, ffmpeg conversions fail. To avoid this add -strict -2 to the video profiles (https://experienceleague.adobe.com/etc/dam/video%20in%20AEM%206.3%20and%20moved%20to%20/libs/settings/dam/video%20in%20AEM%206.4?lang=en)

    note note
    NOTE
    The -strict -2 must be the last parameter in the list of parameters. Also, in AEM 6.4, copy the nodes under /libs/settings/dam/video to /conf/global/settings/dam/video as mentioned in Video Renditions.

    1. Verify that video conversions are happening and that renditions are being created.

Password Restrictions password-restrictions

The password policy of AEM must 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
See Password Restrictions section inConfiguring Author and Publish in AEM Screens

Setting up the Environments setting-up-environments

Install and run the most current versions of the following packages for your version of Adobe Experience Manager (AEM):

  • AEM Service Pack
  • Screens Feature Pack
  • AEM Cumulative Fix Pack

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 environment. Instruct your client to adopt the same configuration on all of their QA, Stage, and Production servers. Mismatched server configurations create problems when deploying and testing.

NOTE
To install the latest Feature Pack for AEM Screens, see Release Notes.

Setting up ACLs setting-up-acls

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.

recommendation-more-help
c90cc542-45c5-47bf-bda6-72a43c3bba05