Configuring and Deploying Screens

Search
Experience Manager 6.4 Sites Deploying User Guide

On this page

Applies to: Experience Manager 6.4 Sites

在中国购买的 Creative Cloud 产品不含 CC 桌面应用程序中的 Creative Cloud 移动应用程序和在线服务及相关功能。

You're viewing help content for version:

The AEM Screens player is available for iOS, OS X, and Android. This page describes the configuration and deployment of AEM Screens followed by Device Registration process.

This page shows how to install and configure the Screens players on your devices.

The AEM Screens players are available for iOS, OS X, and Android.

Note:

To download AEM Screens Player, click here.

AEM Screens is also available in Google Play, iTunes App Store, and Chrome OS. 

For implementation of Chrome OS Player, see Chrome Management Console for more information.

Server Configuration

Note:

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.

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
  2. Check the allow.empty option.
  3. Click Save.

AEM in NOSAMPLECONTENT runmode

Running AEM in production uses the NOSAMPLECONTENT runmode. Remove the the X-Frame-Options=SAMEORIGIN header (in the additional response header section) from

http://localhost:4502/system/console/configMgr/org.apache.sling.engine.impl.SlingMainServlet.

This is required for the AEM Screens Player to play online channels.

Password Restrictions

AEM Screens Player registration will fail, if the password restrictions are set.

Remove the following config to set it correctly,

http://localhost:4502/system/console/configMgr/org.apache.jackrabbit.oak.spi.security.user.action.DefaultAuthorizableActionProvider.

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.

Note:

Recommendation:

It is recommended to use HTTPS for AEM Screens Server in production use.

AEM Screens Player for iOS

To install the Screens player on your iPad:

  1. Click iTunes App Store to download AEM Screens for iPad.

    chlimage_1

  2. Once you install the AEM Screens player, you need to configure your Screens Player.

    chlimage_1

To configure the player:

  1. Open the Settings for AEMScreensPlayer.

    chlimage_1

  2. Change the URL field to contain the IP of your AEM server.

    Note:

    The Device Id, User and Password will be filled by the registration process.

The resolution field allows you to set the resolution you would like to simulate on the iPad.

Note:

If you leave the Resolution field empty, it will use the native resolution of the device.

AEM Screens Player for OS X

To install and configure the Screens player on your mac:

  1. Download OS X player from AEM Screens Player Downloads.

  2. Double-click on the DMG file and move AEMScreensPlayer to the Application folder.

  3. Start the application.

  4. Press Ctrl+Cmd+F to exit fullscreen mode.

  5. Click on AEMScreensPlayer and then Preferences.

    chlimage_1

  6. Enter the URL of your AEM server.

    chlimage_1

    Note:

    The Device Id, User and Password will be filled by the registration process.

  7. Restart the player for the new preferences to be applied.

AEM Screens Player for Android

To install and configure the Screens player on your Android device:

  1. Download Android Player from AEM Screens Player Downloads.

  2. Install the application and tap DONE.

    chlimage_1

  3. Find the AEM Settings widget and drag and drop it to the home screen.

    chlimage_1

  4. Open the settings widget from the home screen and configure it accordingly.

    chlimage_1

    Note:

    The device id, User and Password will be filled by the registration process.

Device Registration

The devices registration process is done on 2 separate machines:

  • The actual device to be registered, for example your Signage Display
  • The AEM server that is used to register your device

  1. On your device, start the AEM Screens Player. The registration UI is shown.

    chlimage_1

  2. In AEM, navigate to the Devices folder of your project.

    Note:

    To get more information on creating a new project for Screens in the AEM dashboard, see Creating and Managing Screens Project.

     

  3. Tap/click the Device Manager button in the action bar.

    chlimage_1

  4. Tap/click the Device Registration button on the top right.

    chlimage_1

  5. Select the required device (same as step 1) and tap/click Register Device.

    chlimage_1

  6. In AEM, wait for the device to send its registration code.

  7. In your device, check the Registration Code.

    chlimage_1

  8. If the Registration Code is the same on both machines, tap/click Validate button in AEM.

    chlimage_1

  9. Set the desired name for the device, and select Register button.

    chlimage_1

    Note:

    If you don't set a name, it will use its unique identifier as name.

  10. Tap/click Finish to complete the registration process .

    chlimage_1

    Note:

    The Go Back button would allow you to register a new device.

    The Assign Display button would let you directly add the device to a display.

In your device, the registration UI should be updated to show the device identifier.

chlimage_1

In AEM, the device should be added to the list and remain unassigned. To learn how to assign it, see Device Assignment.

Before, you learn device assignment, it is recommended you have prior knowledge on how to:

chlimage_1

Limitations on Device Registration

System wide user password restrictions might cause failure in the device registration. The device registration uses a random generated password to create the device user.

If the password is restricted by the AuthorizableActionProvider configuration, creating the device user might fail.

Note:

The current generated random password is composed of 36 ASCII characters, ranging from 33 - 122 (includes almost all special characters).

When the device registration fails, check the AuthorizableActionProvider configuration to see if there are any restrictions.

The following error logs show failed device registration:

25.09.2016 16:54:03.140 *ERROR* [59.100.121.82 [1474844043109] POST /content/screens/svc/registration HTTP/1.1] com.adobe.cq.screens.device.registration.impl.RegistrationServlet Error during device registration
javax.jcr.nodetype.ConstraintViolationException: Password violates password constraint (^(?=.*\d).{7,9}$).
        at org.apache.jackrabbit.oak.spi.security.user.action.PasswordValidationAction.validatePassword(PasswordValidationAction.java:105)
        at org.apache.jackrabbit.oak.spi.security.user.action.PasswordValidationAction.onPasswordChange(PasswordValidationAction.java:76)
        at org.apache.jackrabbit.oak.security.user.UserManagerImpl.onPasswordChange(UserManagerImpl.java:308)

Additional Resources

To learn about AEM Screens Player, see Working with Screens Player.

This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices   |   Online Privacy Policy