Configuring Dynamic Media - Hybrid mode configuring-dynamic-media-hybrid-mode

Dynamic Media – Hybrid needs to be enabled and configured for use. Depending on your use case, Dynamic Media has several supported configurations.

Learn more about working with video in Dynamic Media.

If you use Adobe Experience Manager set up for different environments, such as one for development, one for staging, and one for live production, you need to configure Dynamic Media Cloud Services for each one of those environments.

If you are having issues with your Dynamic Media configuration, an important place to look are the log files specific to dynamic media. These are installed automatically when you enable dynamic media:

They are documented in Monitoring and maintaining your AEM instance.

Hybrid publishing and delivery is a core feature of the Dynamic Media addition to Adobe Experience Manager. Hybrid publishing lets you deliver Dynamic Media assets, such as images, sets and video, from the cloud instead of from the AEM publish nodes.

Other content, such as Dynamic Media viewers, Site pages, and static content will continue to be served from the AEM publish nodes.

If you are a customer of Dynamic Media, you are required to use hybrid delivery as the delivery mechanism for all Dynamic Media content.

Hybrid publishing architecture for videos hybrid-publishing-architecture-for-videos

Hybrid publishing architecture for images hybrid-publishing-architecture-for-images

Supported Dynamic Media configurations supported-dynamic-media-configurations

The configuration tasks that follow reference the following terms:

You may choose to implement Dynamic Media only for imaging, only for video, or for both imaging and video. To determine the steps for configuring Dynamic Media for your specific scenario, please reference the following table.

Enabling Dynamic Media enabling-dynamic-media

Dynamic media is disabled by default. To take advantage of Dynamic Media features, you need to enable dynamic media by using the dynamicmedia run mode as you would, for example, publish run mode. Before enabling, make sure to review the technical requirements.

By enabling Dynamic Media, the dynamic media features will be available in the UI and every uploaded image asset receives a cqdam.pyramid.tiff rendition that is used for fast delivery of dynamic image renditions. Those PTIFFs have significant advantages including (1) the ability to manage only a single master image and generate infinite renditions on-the-fly without any additional storage and (2) the ability to use interactive visualization such as zoom, pan, spin, and so on.

If you want to use Dynamic Media Classic in AEM, you should not enable Dynamic Media unless you are using a specific scenario. Dynamic Media is disabled unless you enable Dynamic Media by way of the runmode.

To enable dynamic media, you must enable the dynamic media runmode either from the command line or from the quickstart file name.

To enable dynamic media:

If you installed AEM to a different port or context path … if-you-installed-aem-to-a-different-port-or-context-path

If you are deploying AEM to an application server and have Dynamic Media enabled, you need to configure the self domain in the externalizer. Otherwise, thumbnail generation for assets will not work properly for dynamic media assets.

In addition, if you run quickstart on a different port or context path, you also have to change the self domain.

When Dynamic Media is enabled, the static thumbnail renditions for image assets are generated using Dynamic Media. For thumbnail generation to work properly for dynamic media, AEM must perform a URL request to itself and must know both the port number and the context path.

In AEM:

In an AEM QuickStart WAR deployment, the port number and context path cannot be derived, therefore you must configure a self domain. See externalizer documentation on how to configure the self domain.

Disabling Dynamic Media disabling-dynamic-media

Dynamic media is not enabled by default. However, if you have previously enabled dynamic media, you may want to turn it off at a later time.

To disable dynamic media after you have enabled it, you remove the -r dynamicmedia run mode flag.

To disable Dynamic Media after it has been enabled:

(Optional) Migrating Dynamic Media presets and configurations from 6.3 to 6.4 zero downtime optional-migrating-dynamic-media-presets-and-configurations-from-to-zero-downtime

If you are upgrading AEM Dynamic Media from 6.3 to 6.4 – which now includes the ability for zero downtime (also known as “Opt-in”) deployments – you are required to run the following curl command to migrate all your presets and configurations from /etc to /conf in CRXDE Lite.

Note: If you run your AEM instance in compatibility mode–that is, you have the compatibility packaged installed–you do not need to run these commands.

To migrate your custom presets and configurations from /etc to /conf, run the following Linux curl command:

curl -u admin:admin http://localhost:4502/libs/settings/dam/dm/presets.migratedmcontent.json

For all upgrades, either with or without the compatibility package, you can copy the out-of-the-box viewer presets by running the following command:

curl -u admin:admin http://localhost:4502/libs/settings/dam/dm/presets/viewer.pushviewerpresets

Configuring image replication configuring-image-replication

Dynamic Media image delivery works by publishing image assets, including video thumbnails, from AEM Author and replicating them to Adobe’s on-demand replication service (the Replication Service URL). Assets are then delivered by way of the on-demand image delivery service (the Image Service URL).

You must do the following:

The Replication Agent publishes Dynamic Media assets such as images, video metadata, and sets to the Adobe-hosted Image Service. The Replication Agent is not enabled by default.

After you have configured the replication agent, you need to validate and test that it has been successfully set up. This section describes these procedures.

Setting up Authentication setting-up-authentication

You need to set up replication authentication on author in order to replicate images to the Dynamic Media image delivery service. You do this by obtaining a KeyStore and then saving it under the dynamic-media-replication user and configuring it. Your company administrator should have received a welcome email with the KeyStore file and necessary credentials during the provisioning process. If you did not receive this, please contact Customer Support.

To set up authentication:

Configuring the Replication Agent configuring-the-replication-agent

Validating the Replication Agent for Dynamic Media validating-the-replication-agent-for-dynamic-media

To validate the replication agent for dynamic media, do the following:

Tap Test Connection. Example output is as follows:

11.03.2016 10:57:55 - Transferring content for ReplicationAction{type=TEST, path[0]='/content/dam', time=1457722675402, userId='admin', revision='null'}
11.03.2016 10:57:55 - * Auth User: replication-receiver
11.03.2016 10:57:55 - * HTTP Version: 1.1
11.03.2016 10:57:55 - * Using OAuth 2.0 Authorization Grants
11.03.2016 10:57:55 - * OAuth 2.0 User: dynamic-media-replication
11.03.2016 10:57:55 - * OAuth 2.0 Token: '*****' initialized
11.03.2016 10:57:55 - Publishing: POST[https://replicate-na.assetsadobe.com:8580/is-publish/publish-receiver?Cmd=Test&RootId=xfpuu-6613]
11.03.2016 10:57:55 - Publish response: OK[]
11.03.2016 10:57:55 - Transfer succeeded in 141 ms for ReplicationAction{type=TEST, path[0]='/content/dam', time=1457722675402, userId='admin', revision='null'}
-------------------------------------------------------------------------------------------------------------------------------
Replication test succeeded

Troubleshooting Authentication troubleshooting-authentication

When setting up authentication, here are some issues you may run into with their solutions. Before checking these, make sure you have set up replication.

Problem: HTTP Status Code 401 with Message - Authorization Required problem-http-status-code-with-message-authorization-required

This issue can be caused by a failure to set up the KeyStore for dynamic-media-replication user.

Replication test to s7delivery:https://s7bern.macromedia.com:8580/is-publish/
17.06.2016 18:54:43 - Transferring content for ReplicationAction{type=TEST, path[0]='/content/dam', time=1466214883309, userId='admin', revision='null'}
17.06.2016 18:54:43 - * Auth User: replication-receiver
17.06.2016 18:54:43 - * HTTP Version: 1.1
17.06.2016 18:54:43 - * Using OAuth 2.0 Authorization Grants
17.06.2016 18:54:43 - * OAuth 2.0 User: dynamic-media-replication
17.06.2016 18:54:43 - No OAuth token available. OAuth not initialized
17.06.2016 18:54:43 - * Using Client Auth SSL alias - replication-alias *
17.06.2016 18:54:43 - Publishing: POST[https://<localhost>:8580/is-publish//publish-receiver?Cmd=Test&RootId=brough]
17.06.2016 18:54:43 - Transfer failed for ReplicationAction{type=TEST, path[0]='/content/dam', time=1466214883309, userId='admin', revision='null'}. java.io.IOException: Failed to execute request
'https://<localhost>:8580/is-publish//publish-receiver?Cmd=Test&RootId=brough':
 Server returned status code 401 with message: Authorization required.
17.06.2016 18:54:43 - Error while replicating: com.day.cq.replication.ReplicationException: Transfer failed for ReplicationAction{type=TEST, path[0]='/content/dam', time=1466214883309,
 userId='admin', revision='null'}. java.io.IOException: Failed to execute request
'https://<localhost>:8580/is-publish//publish-receiver?Cmd=Test&RootId=brough':
 Server returned status code 401 with message: Authorization required.

Solution: Check that the KeyStore is saved to dynamic-media-replication user and is provided with the correct password.

Problem: Could Not Decrypt Key - Could Not Decrypt Data problem-could-not-decrypt-key-could-not-decrypt-data

Replication test to s7delivery:https://<localhost>:8580/is-publish/
17.06.2016 19:00:16 - Transferring content for ReplicationAction{type=TEST, path[0]='/content/dam', time=1466215216662, userId='admin', revision='null'}
17.06.2016 19:00:16 - * Auth User: replication-receiver
17.06.2016 19:00:16 - * HTTP Version: 1.1
17.06.2016 19:00:16 - * Using OAuth 2.0 Authorization Grants
17.06.2016 19:00:16 - * OAuth 2.0 User: dynamic-media-replication
17.06.2016 19:00:16 - No OAuth token available. OAuth not initialized
17.06.2016 19:00:16 - * Using Client Auth SSL alias - replication-alias *
17.06.2016 19:00:16 - Transfer failed for ReplicationAction{type=TEST, path[0]='/content/dam', time=1466215216662, userId='admin', revision='null'}. java.lang.SecurityException: java.security.UnrecoverableKeyException: Could not decrypt key: Could not decrypt data.

Solution: Check the password. The password saved in the replication agent is not the same password that was used to create keystore.

Problem: InvalidAlgorithmParameterException problem-invalidalgorithmparameterexception

This issue is caused by a configuration error in your AEM Author instance. The java process on the Author is not getting the correct javax.net.ssl.trustStore. You see this error in the replication log:

14.04.2016 09:37:43 - Transfer failed for ReplicationAction{type=TEST, path[0]='/content/dam', time=1460651862089, userId='admin', revision='null'}. java.io.IOException: Failed to execute request 'https://<localhost>:8580/is-publish/publish-receiver?Cmd=Test&RootId=rbrough-osx2': java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
14.04.2016 09:37:43 - Error while replicating: com.day.cq.replication.ReplicationException: Transfer failed for ReplicationAction{type=TEST, path[0]='/content/dam', time=1460651862089, userId='admin', revision='null'}. java.io.IOException: Failed to execute request 'https://<localhost>:8580/is-publish/publish-receiver?Cmd=Test&RootId=rbrough-osx2': java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

Or the error log:

07.25.2019 12:00:59.893 *ERROR* [sling-threadpool-db2763bb-bc50-4bb5-bb64-10a09f432712-(apache-sling-job-thread-pool)-90-com_day_cq_replication_job_s7delivery(com/day/cq/replication/job/s7delivery)] com.day.cq.replication.Agent.s7delivery.queue Error during processing of replication.

java.io.IOException: Failed to execute request 'https://replicate-na.assetsadobe.com:8580/is-publish/publish-receiver?Cmd=Test&RootId=rbrough-osx': java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty
        at com.scene7.is.catalog.service.publish.atomic.PublishingServiceHttp.executePost(PublishingServiceHttp.scala:195)

Solution: Make sure the java process on the AEM Author has the system property -Djavax.net.ssl.trustStore= set to a valid truststore.

Problem: KeyStore is either not set up or it is not initialized problem-keystore-is-either-not-set-up-or-it-is-not-initialized

This issue may be caused by a hot fix, or a feature pack overwriting the dynamic-media-user or keystore node.

Replication log example:

Replication test to s7delivery:https://replicate-na.assetsadobe.com/is-publish
02.08.2016 14:37:44 - Transferring content for ReplicationAction{type=TEST, path[0]='/content/dam', time=1470173864834, userId='admin', revision='null'}
02.08.2016 14:37:44 - * Auth User: replication-receiver
02.08.2016 14:37:44 - * HTTP Version: 1.1
02.08.2016 14:37:44 - * Using OAuth 2.0 Authorization Grants
02.08.2016 14:37:44 - * OAuth 2.0 User: dynamic-media-replication
02.08.2016 14:37:44 - Transfer failed for ReplicationAction{type=TEST, path[0]='/content/dam', time=1470173864834, userId='admin', revision='null'}. com.adobe.granite.keystore.KeyStoreNotInitialisedException: Uninitialised key store for user dynamic-media-replication

Solution:

Problem: Publish Agent is using SSL instead of OAuth problem-publish-agent-is-using-ssl-instead-of-oauth

This issue may be caused by a hot fix or a feature pack that did not install correctly or overwrote the settings.

Replicate log example:

01.08.2016 18:42:59 - Transferring content for ReplicationAction{type=TEST, path[0]='/content/dam', time=1470073379634, userId='admin', revision='null'}
01.08.2016 18:42:59 - * Auth User: replication-receiver
01.08.2016 18:42:59 - * HTTP Version: 1.1
01.08.2016 18:42:59 - * Using Client Auth SSL alias - replication-receiver *
01.08.2016 18:42:59 - Publishing: POST[https://replicate-eu.assetsadobe2.com:443/is-publish/publish-receiver?Cmd=Test&RootId=altayerstaging]
01.08.2016 18:42:59 - Transfer failed for ReplicationAction{type=TEST, path[0]='/content/dam', time=1470073379634, userId='admin', revision='null'}. java.io.IOException: Failed to execute request 'https://replicate-eu.assetsadobe2.com:443/is-publish/publish-receiver?Cmd=Test&RootId=rbroughstaging': Server returned status code 401 with message: Authorization required.
01.08.2016 18:42:59 - Error while replicating: com.day.cq.replication.ReplicationException: Transfer failed for ReplicationAction{type=TEST, path[0]='/content/dam', time=1470073379634, userId='admin', revision='null'}. java.io.IOException: Failed to execute request 'https://replicate-eu.assetsadobe2.com:443/is-publish/publish-receiver?Cmd=Test&RootId=rbroughstaging': Server returned status code 401 with message: Authorization required.

Solution:

Testing your configuration testing-your-configuration

Adobe recommends that you perform an end-to-end test of the configuration.

Be sure you have already done the following prior to beginning this test:

To test your configuration:

Another way to test that your assets were delivered is to append req=exists to your URL.

Configuring Dynamic Media Cloud Services configuring-dynamic-media-cloud-services

The Dynamic Media Cloud service provides support for cloud services such as hybrid publishing and delivery of images and video, video analytics, and video encoding, among other things.

As part of the configuration, you need to enter a registration ID, video service URL, image service URL, replication service URL and set up authentication. You should have received all this information as part of the account provisioning process. If you did not receive this information, contact your Adobe Experience Manager Administrator or Adobe Technical Support to obtain the information.

To configure dynamic media cloud services:

Configuring video reporting configuring-video-reporting

You can configure video reporting across multiple installations of AEM using Dynamic Media – Hybrid mode.

When to use: At the time you configure Dynamic Media Configuration (Pre 6.3), numerous features are started including video reporting. The configuration creates a report suite in a regional Analytics company. If you configure multiple Author nodes, you create a separate report suite for each one. As a result, reporting data is inconsistent among installations. Furthermore, if each Author node refers to the same Hybrid Publish server, the last Author installation changes the destination report suite for all video reporting. This issue overloads the Analytics system with too many report suites.

Get started: Configure video reporting by completing the following three tasks.

Creating a Video Analytics preset package after configuring the first Author node creating-a-video-analytics-preset-package-after-configuring-the-first-author-node

When you have finished this task, you will have a package file that contains the Video Analytics presets. These presets contain a report suite, the tracking server, the tracking namespace, and the Marketing Cloud Organization ID, if available.

Installing the Video Analytics preset package before you configure additional Author nodes installing-the-video-analytics-preset-package-before-you-configure-additional-author-nodes

Be sure that you complete this task before you configure Dynamic Media Configuration (Pre 6.3). Failure to do so results in the creation of another unused report suite. In addition, even though video reporting will continue to work correctly, the gathering of data is not optimized.

Make sure that the Video Analytics preset package from the first Author node is accessible on the new Author node.

Verifying and debugging the package installation verifying-and-debugging-the-package-installation

Troubleshooting the video reporting configuration troubleshooting-the-video-reporting-configuration

About the Video Analytics preset about-the-video-analytics-preset

The Video Analytics preset—sometimes known simply as analytics preset–is stored next to the Viewer presets in Dynamic Media. It is basically the same as a Viewer preset but with information used to configure AppMeasurement and Video Heartbeat reporting.

The preset’s properties are the following:

AEM 6.4 and newer versions save this preset at /conf/global/settings/dam/dm/presets/analytics/jcr:content/userdata

Replicating Catalog Settings replicating-catalog-settings

You must publish your own default catalog settings as part of the setup process through the JCR. To replicate catalog settings:

Replicating Viewer Presets replicating-viewer-presets

To deliver an asset with a viewer preset, you must replicate/publish the viewer preset. (All viewer presets must be activated and replicated to obtain the URL or embed code for an asset.) See Publishing Viewer Presets for more information.

Filtering Assets for Replication filtering-assets-for-replication

In non-Dynamic Media deployments, you replicate all assets (both images and video) from your AEM author environment to the AEM publish node. This workflow is necessary because the AEM publish servers also deliver the assets.

However, in Dynamic Media deployments, because assets are delivered by way of the cloud, there is no need to replicate those same assets to AEM publish nodes. Such a “hybrid publishing” workflow avoids extra storage costs and longer processing times to replicate assets. Other content, such as Dynamic Media viewers, Site pages, and static content continue to be served from the AEM publish nodes.

Besides replicating the assets, the following non-assets are also replicated:

The filters provide a way for you to exclude assets from being replicated to the AEM publish node.

Using default Asset Filters for replication using-default-asset-filters-for-replication

If you are using Dynamic Media for 1) imaging in production or 2) imaging and video, then you can use the default filters that we provide as-is. The following filters are active by default:

Setting up Asset Filters for video-only deployments setting-up-asset-filters-for-video-only-deployments

If you are using Dynamic Media for video-only, follow these steps to set up asset filters for replication:

This sets up the AEM publish instance to deliver the video poster image as well as the video metadata required for playback, while the video itself is delivered by the Dynamic Media cloud service. The filter will also exclude from replication the original video and static thumbnail renditions, which are not needed on the publish instance.

Setting up Asset Filters for Imaging in non-production deployments setting-up-asset-filters-for-imaging-in-non-production-deployments

If you are using Dynamic Media for imaging in non-production deployments, follow these steps to set up asset filters for replication:

This sets up the AEM publish instance to deliver the images to your non-production environment. The filter will also exclude from replication the original image and static renditions, which are not needed on the publish instance.

Customizing Asset Filters for replication customizing-asset-filters-for-replication

To optionally customize asset filters for replication:

Navigate to content/dam/<locate_your_asset>/jcr:content/renditions.

The following graphic is an example of an asset’s renditions.

Using the example above, if you only wanted to replicate the PTIFF (Pyramid TIFF), then you would enter +cqdam,* which includes all the renditions that start with cqdam. Inthe example, that rendition is cqdam.pyramid.tiff.

If you only wanted to replicate the original, then you would enter +original.

Configuring Dynamic Media Image Server settings configuring-dynamic-media-image-server-settings

Configuring the Dynamic Media Image Server involves editing the Adobe CQ Scene7 ImageServer bundle and the Adobe CQ Scene7 PlatformServer bundle.

Prerequisite: Before you configure Dynamic Media Image Server, ensure that your VM of Windows includes an installation of the Microsoft Visual C++ Libraries. The libraries are necessary to run Dynamic Media Image Server. You can download the Microsoft Visual C++ 2010 Redistributable Package (x64) here.

To configure Dynamic Media Image Server settings:

Default Manifest settings default-manifest-settings

The default manifest lets you configure the defaults that are used to generate the Dynamic Media Delivery responses. You can fine tune quality (JPEG quality, resolution, resampling mode), caching (expiration), and prevent the rendering of images that are too large (defaultpix, defaultthumbpix, maxpix).

The location of the default manifest configuration is taken from the Catalog root default value of the Adobe CQ Scene7 PlatformServer bundle. By default this value is located at the following path within Tools > General > CRXDE Lite:

/conf/global/settings/dam/dm/imageserver/

You can change the values of the properties, as described in the table below, by entering new values.

When you are finished making changes to the default manifest, in the upper-left corner of the page, tap Save All.

Be sure you tap the Access Control tab (to the right of the Properties tab), then set the access control privileges to jcr:read for the everyone and dynamic-media-replication users.

Table of Manifest settings and their default values:

Configuring Dynamic Media Color Management configuring-dynamic-media-color-management

Dynamic media color management lets you color correct assets for previewing.

With color correction, ingested assets retain their color space (RGB, CMYK, Gray) and embedded color profile in the generated pyramid TIFF rendition. When you request a dynamic rendition, the image color is corrected into the target color space. You configure the output color profile in the dynamic media publish settings in the JCR.

Adobe color management uses ICC profiles, a format defined by the International Color Consortium (ICC).

You can configure dynamic media color management and configure image presets using CMYK, RGB, or Gray output. See Configuring Image Presets.

Advanced use cases could use a manual configure icc= modifier to explicitly select an output color profile:

Installing feature pack 12445 installing-feature-pack

You must install feature pack 12445 to use the dynamic media color management capabilities.

To install feature pack 12445:

Configuring the default color profiles configuring-the-default-color-profiles

After you install the feature pack, you need to configure the appropriate default color profiles to enable color correction when requesting RGB or CMYK image data.

To configure the default color profiles:

For example, you could set iccprofilergb to sRGB, and iccprofilecmyk to WebCoated. Doing so would do the following:

Delivering Assets delivering-assets

After you complete all the tasks above, activated Dynamic Media assets are served from the Image or Video Service. In AEM, this ability shows up in a Copy Image URL, Copy Viewer URL, Embed Viewer Code, and in the WCM.

See Delivering Dynamic Media Assets.

WCM Dynamic Media and Interactive Media Components wcm-dynamic-media-and-interactive-media-components

WCM pages that reference Dynamic Media and Interactive Media components reference the delivery service.