Prezeráte obsah pomocníka verzie:

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

Výstraha:

You must download and install Feature Pack 15207 to configure image replication. See Package Share.

Poznámka:

Watch How to Setup and Configure AEM Dynamic Media video (58:27).

In this recorded video training session you learn how to implement Dynamic Media. Topics covered include the following:

  • Dynamic Media use cases
  • Technical architecture
  • How to configure Dynamic Media in AEM 6.2
  • Setup and best practices for Dynamic Media imaging
  • Setup and best practices for Dynamic Media video

Learn more about working with video in Dynamic Media.

Poznámka:

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.

Poznámka:

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:

  • s7access.log
  • ImageServing.log

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. Note, however, that AEM publish nodes are still required so that other content, such as Dynamic Media viewers, Site pages, and static content, can still be served.

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

chlImage_1

Hybrid publishing architecture for images

chlImage_1

Supported Dynamic Media Configurations

The configuration tasks that follow reference the following terms:

Term Dynamic Media Enabled Description
AEM author node White check mark in a green circle The author node that you deploy to On-Premise or through Managed Services.
AEM publish node White "X" in a red square. The publish node that you deploy to On-Premise or through Managed Services.
Image Service publish node White check mark in a green circle. The publish node that you run on Data Centers that are managed by Adobe. Refers to the image service URL.

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. 

Scenario How it Works Configuration Steps
Deliver ONLY images in production Images are delivered through servers in Adobe’s worldwide data centers and then cached by a CDN for scalable performance and global reach.
  1. Download and install Feature Pack 15207 available here. See also Package Share.
  2. On the AEM author node, enable dynamic media.
  3. On AEM publish node, enable dynamic media.
  4. Configure imaging in Dynamic Media Cloud Services.
  5. Configure image replication.
  6. Replicate catalog settings.
  7. Replicate viewer presets.
  8. Use default asset filters for replication.
  9. Configure Dynamic Media Image Settings.
  10. Deliver assets.
Deliver ONLY images in pre-production (Dev, QE, Stage, etc.) Images are delivered through the AEM publish node. In this scenario, since traffic is minimal, there is no need to deliver images to Adobe’s data center.  An additional benefit is that this allows for secure preview of content before production launch
  1. On the AEM author node, enable dynamic media.
  2. On the AEM publish node, enable dynamic media.
  3. Replicate viewer presets.
  4. Set up asset filter for non-production images.
  5. Configure Dynamic Media Image Settings.
  6. Deliver assets.
Deliver ONLY video in any environment (production, Dev, QE, Stage, etc) Videos are delivered and cached by a CDN for scalable performance and global reach. The video poster image (thumbnail of video which shows before playback initiates) will be delivered by the AEM publish instance.
  1. On the AEM author node, enable dynamic media.
  2. On the AEM publish node, enable dynamic media (the publish instance serves the video poster image and provides metadata for video playback).
  3. Configure video in Dynamic Media Cloud Services.
  4. Configure video in dynamic media.
  5. Replicate viewer presets.
  6. Set up asset filter for video-only.
  7. Deliver assets.
Deliver BOTH images and video in production

Videos are delivered and cached by a CDN for scalable performance and global reach. Images and video poster images are delivered through servers in Adobe’s worldwide data centers and then cached by a CDN for scalable performance and global reach.

Please refer to previous sections to setup image or video in pre-production. 

  1. Download and install Feature Pack 15207 available here. See also Package Share.
  2. On the AEM author node, enable dynamic media.
  3. On the AEM publish node, enable dynamic media.
  4. Configure video in Dynamic Media Cloud Services.
  5. Configure imaging in Dynamic Media Cloud Services.
  6. Configure video in dynamic media
  7. Configure image replication.
  8. Replicate catalog settings.
  9. Replicate viewer presets.
  10. Use default asset filters for replication.
  11. Configure Dynamic Media Image Settings.
  12. Deliver assets.
Asset Share: Download Dynamic image Renditions  Dynamic Media generates image renditions on-the-fly without incurring any additional storage. You can use Asset Share in conjunction with Dynamic Media to download image renditions for different formats, sizes, quality, and so on.
  1. On the AEM publish node for Asset Share, enable dynamic media.
  2. Configure Dynamic Media Image Settings.

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.

Poznámka:

Enabling dynamic media via the run mode replaces the previous functionality (in 6.1 and 6.0) where you enabled dynamic media by setting the dynamicMediaEnabled flag to true. This flag has no functionality in AEM 6.2 and later. In addition, you no longer need to restart the quickstart to enable dynamic media.

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 Scene7 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.

Renaming the jar file is the preferred method because it ensures that dynamic media is always enabled regardless of how the quickstart jar file is started (command line or double-clicking the jar file).

To enable dynamic media, do either one of the following:

  1. On the command line, when launching the quickstart, you can do either of the following:

    • Add -r dynamicmedia to the end of the command line when starting the jar file.
    java -Xmx2048m -XX:MaxPermSize=512m -jar cq-quickstart-6.2.0.jar -r dynamicmedia
    • Insert dynamicmedia within the name of the quickstart jar, such as cq-quickstart-dynamicmedia-6.2.0.jar. 
    java -Xmx2048m -XX:MaxPermSize=512m -jar cq-quickstart-dynamicmedia-6.2.0.jar
  2. After downloading the quickstart jar file, modify the filename of the jar itself by inserting dynamicmedia before you open the file.

    chlImage_1
  3. Request http://<host>:<port>/is/image and make sure Image Server is now running. 

    Poznámka:

    To troubleshoot issues with Dynamic Media, see the following logs in the crx-quickstart/logs/ directory:

    • ImageServer-<PortId>yyyy><mm>-<dd>.log - The ImageServer log provides statistics and analytical information used for analyzing the behavior of the internal ImageServer process.
    • s7access-<yyyy><mm><dd>.log - The s7access log records each request made to Dynamic Media through /is/image and /is/content.

    These logs are only used when Dynamic Media is enabled. They are not included in the Download Full package that is generated from the system/console/status-Bundlelist page; when calling Customer Support if you have a Dynamic Media issue, please append both these logs to the issue.

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:

  • The self domain in the externalizer is used to retrieve both the port number and context path.
  • If no self domain is configured, the port number and context path are retrieved from the Jetty HTTP service.

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.

Poznámka:

In an AEM Quickstart stand-alone deployment, a self domain generally does not need to be configured because the port number and context path can be auto-configured. However, if all network interfaces are turned off, you need to configure the self domain.

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 dynamicmedia from the file name and/or you remove the -r dynamicmedia run mode flag. 

To disable Dynamic Media after it has been enabled:

  1. On the command line, when launching the quickstart, you can do either of the following:

    • Do not add -r dynamicmedia to the end of the command line when starting the jar file.
    java -Xmx2048m -XX:MaxPermSize=512m -jar cq-quickstart-6.2.0.jar
    • Remove dynamicmedia within the name of the quickstart jar, such as cq-quickstart-6.2.0.jar. 
    java -Xmx2048m -XX:MaxPermSize=512m -jar cq-quickstart-6.2.0.jar
  2. Modify the filename of the jar itself by removing dynamicmedia before opening the file.

    chlImage_1
  3. Request http://<host>:<port>/is/image. You receive a message that Dynamic Media is disabled.

    Poznámka:

    After the Dynamic Media functionality is switched off, the workflow step that generates the cqdam.pyramid.tiff rendition will be skipped automatically. This also disables dynamic rendition support and other Dynamic Media features.

Configuring Video in Dynamic Media

Dynamic Media uses a cloud-based video encoding service; it does not use FFMPEG for encoding. As such, you must edit DAM Update Asset to remove "FFmpeg thumbnails" and "FFmpeg transcoding" from its workflow.

To configure video in Dynamic Media:

  1. In AEM, tap or click the AEM logo to access the global navigation console and tap or click the Tools icon and navigate to Workflow > Models.

  2. Hover over the DAM Update Asset workflow, and when the check mark appears, select it. 

  3. On the toolbar, tap or click Edit.

  4. In the DAM Update Asset screen, in the Flow Start list, right-click FFmpeg thumbnails, and then tap Delete.

  5. In the same Flow Start list, right-click FFmpeg transcoding, and then tap Delete.

  6. Near the top of the DAM Update Asset, tap Save. Close the DAM Update Asset page.

Configuring Image Replication

Poznámka:

You must download and install Feature Pack 15207 to set up image replication and authentication for AEM 6.2.

See Package Share.

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:

  1. Set up authentication
  2. Configure the replication agent

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.

Poznámka:

The Dynamic Media Agent publish has been deprecated in AEM 6.2. Instead, use Dynamic Media Hybrid Image Replication (s7delivery).

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 Care. 

To set up authentication:

  1. Contact Customer Care for your keystore file and password if you do not already have this. This is part of provisioning and it will associate the keys to your account.  

  2. In Tools > Security, tap or click Users. The User Management window opens.

  3. Navigate to the dynamic-media-replication user and tap or click to open.

    chlImage_1
  4. In the Account Settings section of the page, tap or click Create KeyStore.

    chlImage_1
  5. Enter a password and confirm the password in the Set KeyStore Password dialog box.

    Poznámka:

    Remember the password that you enter. You will need to enter it again when you configure the Replication Agent later.

    chlImage_1
  6. In the Account settings dialog box, click Manage KeyStore.

    chlImage_1
  7. In the KeyStore Management area, expand the Add Private Key from Key Store file area and add the following (see the images that follow for placement of fields):

    1. In the New Alias field, enter the name of an alias that you will later use in the replication configuration; for example, replication.
    2. In the KeyStore File Password field, enter the KeyStore File password. This is not the KeyStore File password that you created in Step 5, but is the KeyStore File password Adobe provides in the Welcome email sent to you during provisioning. Contact Adobe Customer Care if you did not receive a KeyStore File password.
    3. In the Private Key Password field, enter the private key password (may be the same private key password provided in the previous step). Adobe provides the private key password in the Welcome email sent to you during provisioning. Contact Adobe Customer Care if you did not receive a private key password.
    4. In the Private Key Alias field, enter the private key alias for example, companyname-alias. Adobe provides the private key alias in the Welcome email sent to you during provisioning. Contact Adobe Customer Care if you did not receive a private key alias.
    Enter New Alias field
    Enter Key Store Password field, Private Key Password field, and Enter Private Key Alias field
  8. Tap or click Select Key Store File and navigate to the KeyStore file provided to you by Adobe and tap or click Submit

Configuring the Replication Agent

  1. In AEM, tap or click the AEM logo to access the global navigation console and tap or click the Tools icon and navigate to Deployment > Replication > Agents on author.

  2. On the Agents on author page, tap or click Dynamic Media Hybrid Image Replication (s7delivery).

  3. Tap or click Edit.

  4. In the Agent Settings dialog box, in the Settings tab, select the Enabled check box to turn on the agent.

  5. Tap or click the Transport tab. In the Transport tab, enter the following:

    • URI - This value is the URI used to publish content from the AEM Author node to the Image Service for cloud-based delivery (for example, s7delivery:https://replicate-na.assetsadobe.com:443/is-publish). This URI is provided to you by Adobe in the provisioning email as the Replication Service URL. The URI must start with s7delivery:.
    • Tenant ID - This value is the name of your company/tenant that is publishing to the Replication Service. This value is the Tenant ID that Adobe provides in the Welcome email sent to you during provisioning. Contact Adobe Customer Care if you did not receive this.
    • User - This value should be replication-receiver.
    • Password - This is the KeyStore password that was created when you clicked/tapped Create KeyStore. Adobe does not provide this password. See step 5 of Setting Up Authentication.
    chlImage_1
    chlImage_1

    The following image shows the replication agent with sample data:

    chlImage_1
  6. Click or tap OK.

Validating the Replication Agent for Dynamic Media

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

Tap or click 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=weott-5502]
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

Poznámka:

You can also check by doing one of the following:

  • Check the replication logs to make sure the asset is replicated. 
  • Publish an image. Tap or click the image and select Viewers in drop-down menu. Then select a viewer preset, then click URL, and copy/paste the URL in the browser to verify that you can see the image.

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

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

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://s7bern.macromedia.com:8580/is-publish//publish-receiver?Cmd=Test&RootId=akshay]
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://s7bern.macromedia.com:8580/is-publish//publish-receiver?Cmd=Test&RootId=akshay':
 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://s7bern.macromedia.com:8580/is-publish//publish-receiver?Cmd=Test&RootId=akshay':
 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

Replication test to s7delivery:https://s7bern.macromedia.com: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

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://s7bern.macromedia.com:8580/is-publish/publish-receiver?Cmd=Test&RootId=cbrann-osx1': 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://s7bern.macromedia.com:8580/is-publish/publish-receiver?Cmd=Test&RootId=cbrann-osx1': java.lang.RuntimeException: Unexpected error: java.security.InvalidAlgorithmParameterException: the trustAnchors parameter must be non-empty

Or the error log:

07.04.2016 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=pbayol-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

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:

  1. Navigate to the User Management page:
    localhost:4502/libs/granite/security/content/useradmin.html

  2. Click/Tap the Manage KeyStore link.

  3. Verify that you do not need to initialize the keystore.

  4. Reconfigure the s7delivery Replication Agent.
    localhost:4502/etc/replication/agents.author/s7delivery.html

  5. Click/Tap Test Connection to verify the configuration is valid.

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.

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=altayerstaging': 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=altayerstaging': Server returned status code 401 with message: Authorization required.

Solution:

To fix this issue:

  1. In AEM, click Tools > General > CRXDE Lite.

    localhost:4502/crx/de/index.jsp

  2. Navigate to the s7delivery Replication Agent node.
    localhost:4502/crx/de/index.jsp#/etc/replication/agents.author/s7delivery

  3. Add this setting to the replication agent (Boolean with value set to True):

    enableOauth=true

  4. Near the upper-left corner of the page, click Save All.

Testing your Configuration

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

  1. Upload an image asset. (In Assets, tap or click Create > Files and select the file.)

  2. Wait for the workflow to finish.

  3. Publish the image asset. (Select the asset and tap or click Publish.)

  4. Navigate to the renditions for that image by opening the image, and tapping or clicking Renditions.

    chlImage_1
  5. Select any dynamic rendition.

  6. Click URL to obtain the URL for this asset.

  7. Navigate to the selected URL and check whether the image behaves as expected.

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

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. 

Poznámka:

Before setting up Dynamic Media Cloud services, be sure to have your publish instance set up. You must also have replication set up before configuring Dynamic Media Cloud services. 

To configure dynamic media cloud services:

  1. In AEM, tap or click the AEM logo to access the global navigation console and tap or click the Tools icon and navigate to Deployment > Cloud Services.

  2. On the Cloud Services page, under Dynamic Media Cloud Services, tap or click Configure Now.

  3. In the Create Configuration dialog box, enter a title and optional name for the configuration you are creating.

  4. Tap Create.

  5. If you are configuring Dynamic Media for video, in the Edit Component dialog box,

    • In the Registration ID field, type your registration ID.
    • In the Video Service URL field, enter the video service URL for the Dynamic Media Gateway.
  6. If you are configuring Dynamic Media for imaging in the Edit Component dialog box, in the Image Service URL field, enter the image service URL for the Dynamic Media Gateway.

  7. Tap OK.

  8. Near the upper-left corner of the page, touch Cloud Services to return to the Cloud Services page. Tap or click the AEM logo to access the global navigation console.

Replicating Catalog Settings

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

  1. In AEM, navigate to the following location in CRXDE Lite (requires admin privileges):

    http://<server>:<port>/crx/de/index.jsp#/etc/dam/imageserver/configuration/jcr%3Acontent/settings

  2. Tap or click the Replication tab.

  3. Tap or click Replicate.

    chlImage_1

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

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. Note, however, that AEM publish nodes are still required so that other content, such as Dynamic Media viewers, Site pages, and static content, can still be served.

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

  • Dynamic Media Delivery configuration: /etc/dam/imageserver/configuration/jcr:content/settings
  • Image Presets: /etc/dam/imageserver/macros
  • Viewer Presets: /etc/dam/presets/viewer

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

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:

  Filter Mimetype Renditions
Dynamic Media Image Delivery

filter-images

filter-sets

 

Starts with image/

Contains application/ and ends with set.

The out-of-the-box "filter-images" (applies to single images assets, including interactive images) and "filter-sets" (applies to Spin Sets, Image Sets, Mixed Media Sets, and Carousel Sets) will:
  • Include PTIFF images and Metadata for replication (Any rendition starting with cqdam).
  • Exclude from replication the original image and static image renditions.
Dynamic Media Video Delivery filter-video Starts with video/ The out-of-the-box "filter-video" will:
  • Include proxy video renditions, video thumbnail/poster image, metadata (both at parent video and video renditions) for replication (Any rendition starting with cqdam).
  • Exclude from replication the original video and static thumbnail renditions.

    Note: The proxy video renditions do not contain binaries, but instead are just node properties. Hence, there is no impact on publisher repository size.
Scene7 integration

filter-images

filter-sets

filter-video

Starts with image/

Contains application/ and ends with set.

Starts with video/

You configure the Transport URI to point to your AEM publish server instead of the Adobe Dynamic Media Cloud Replication Service URL. Setting up this filter will allow Scene7 to deliver assets instead of the AEM publish instance.

The out-of-the-box "filter-images," "filter-sets" and "filter-video" will:

  • Include PTIFF image, proxy video renditions, and metadata for replication. However, because they do not exist in the JCR-for those running AEM - Scene7 integration-it effectively does nothing.
  • Exclude from replication the original image, static image renditions, original video, and static thumbnail renditions. Instead, Scene7 will be delivering image and video assets.

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:

  1. In AEM, tap or click the AEM logo to access the global navigation console and tap or click the Tools icon and navigate to Deployment > Replication Agents on author.

  2. On the Agents on author page, touch Default Agent (publish).

  3. Touch Edit.

  4. In the Agent Settings dialog box, in the Settings tab, check Enabled to turn on the agent.

  5. Tap OK.

  6. In AEM, touch Tools > GeneralCRXDE Lite.

  7. In the left folder tree, navigate to/etc/replication/agents.author/dynamic_media_replication/jcr:content/damRenditionFilters

  8. Locate filter-video, right-click it and select Copy.

  9.  In the left folder tree, navigate to /etc/replication/agents.author/publish

  10. Locate jcr:content, right-click it and select Paste.

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

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

  1. In AEM, tap or click the AEM logo to access the global navigation console and tap or click the Tools icon and navigate to Deployment > Replication Agents on author.

  2. On the Agents on author page, touch Default Agent (publish).

  3. Touch Edit.

  4. In the Agent Settings dialog box, in the Settings tab, check Enabled to turn on the agent.

  5. Tap OK.

  6. In AEM, touch Tools > GeneralCRXDE Lite.

  7. In the left folder tree, navigate to/etc/replication/agents.author/dynamic_media_replication/jcr:content/damRenditionFilters

  8. Locate filter-images, right-click it and select Copy.

  9.  In the left folder tree, navigate to /etc/replication/agents.author/publish

  10. Locate jcr:content, right-click it and select Paste.

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

To optionally customize the filtering of assets for replication:

  1. In AEM, tap or click the AEM logo to access the global navigation console and tap or click the Tools icon and navigate to General CRXDE Lite.

  2. In the left folder tree, navigate to /etc/replication/agents.author/dynamic_media_replication/jcr:content/damRenditionFilters to review the filters.

    chlImage_1
  3. To define the Mime Type for the filter, you can locate the Mime Type as follows:

    In the left rail, expand content > dam > <locate_your_asset> > jcr:content > metadata, and then in the table, locate dc:format.

    The following graphic is an example of an asset's path to dc:format.

    chlImage_1

    Notice that the dc:format for the asset Fiji Red.jpg is image/jpeg.

    To have this filter apply to all images, regardless of their format, set the value to image/*  where * is a regular expression that is applied to all images of any format.

    To have the filter apply only to images of the type JPEG, enter a value of image/jpeg.

  4. Define what renditions you want to include or exclude from replication.

    Characters that you can use to filter for replication include the following:

    Character to use How it filters assets for replication
    * Wildcard character
    + Includes assets for replication.
    - Excludes assets from replication.

    Navigate to content/dam/<locate your asset>/jcr:content/renditions

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

    chlImage_1

    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 Settings

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

Poznámka:

Dynamic Media works out-of-the-box after it is enabled. However, you can optionally choose to fine tune your installation by configuring Dynamic Media Image Delivery servers to meet certain specifications or requirements.

Prerequisite: Before you configure Dynamic Media Image Delivery 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 Delivery server. You can download the Microsoft Visual C++ 2010 Redistributable Package (x64) here.

To configure Dynamic Media Image Delivery servers:

  1. In AEM, tap or click the AEM logo to access the global navigation console and tap or click the Tools icon and navigate to  In AEM (Adobe Experience Manager), tap or click Operations > Web Console.

  2. On the Adobe Experience Manager Web Console Configuration page, click or tap OSGi > Configuration to list all the bundles that are currently running within AEM.

    The Dynamic Media Delivery Servers are found under the following names in the list:

    • Adobe CQ Scene7 ImageServer
    • Adobe CQ Scene7 PlatformServer
  3. In the list of bundles, to the right of Adobe CQ Scene7 ImageServer, tap the Edit icon.

  4. In the Adobe CQ Scene7 ImageServer dialog box, set the following default value options:

    Poznámka:

    In most cases, there is no need to change the default values. However, if you do change the default values, you must restart the bundle for the changes to take affect.

    Property Default value Description
    TcpPort.name empty Port number to use for communication with the ImageServer process. By default free port is automatically detected.
    AllowRemoteAccess.name empty

    Allow or disallow remote access to ImageServer process. If false, the image server listens only on localhost.

    Default externalizer settings that point to the localhost need to specify the actual domain or IP address of the specific VM instance. The reason for this is because  the localhost may be pointing to the parent system of the VM.

    Domains or IP addresses for the VM may need to have a host file entry so that it can resolve itself.

    MaxRenderRgnPixels 16 MPixels Maximum size in megapixels that is rendered.
    MaxMessageSize 16 MBytes Maximum message size in megabytes that is delivered.
  5. Tap Save.

  6. In the list of bundles, to the right of Adobe CQ Scene7 PlatformServer, tap the Edit icon.

  7. In the Adobe CQ Scene7 PlatformServer dialog box, set the following default value options:

    Poznámka:

    The Dynamic Media Delivery Servers use their own disk cache to cache responses. The AEM HTTP cache and the Dispacher cannot be used to cache responses from the Dynamic Media Delivery Server.

    Property Default value Description
    Catalog root /etc/dam/imageserver/configuration/jcr:content/settings Default manifest settings. See Default Manifest below.
    Cache enabled Checked Whether or not the response cache is enabled
    Cache roots cache One or more paths to the response cache folders. Relative paths are resolved against the internal s7imaging bundle folder.
    Cache Max Size 200000000 Maximum size of response cache in bytes.
    Cache Max Entries 100000 Maximum number of entries allowed in the cache.

    Default Manifest

    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 > GeneralCRXDE Lite:

    /etc/dam/imageserver/configuration/jcr:content/settings

    You can change the values of the properties described in the following table by entering new values and clicking Save All.

    chlImage_1
    Property Default value Description
    bkgcolor FFFFFF

    Default background color. RGB value used to fill in any area of a reply image which does not contain actual image data.

    See also BkgColor in the Image Serving API.

    defaultpix 300,300

    Default view size. The server constrains reply images to be no larger than this width and height, if the request does not specify the view size explicitly using wid=, hei=, or scl=.

    Specified as two integer numbers, 0 or larger, separated by a comma. Width and height in pixels. Either or both values may be set to 0 to keep them unconstrained. Does not apply to nested/embedded requests.

    See also DefaultPix in the Image Serving API.

    Usually, however, you are using a viewer preset or image preset to deliver the asset. Defaultpix only applies to an asset that is not using a viewer preset or image preset.

    defaultthumbpix 100,100

    Default thumbnail size. Used instead of attribute::DefaultPix for thumbnail requests (req=tmb).

    The server constrains reply images to be no larger than this width and height, if a thumbnail request (req=tmb) does not specify the size explicitly not specify the view size explicitly using wid=, hei=, or scl=.

    Specified as two integer numbers, 0 or larger, separated by a comma. Width and height in pixels. Either or both values may be set to 0 to keep them unconstrained. 

    Does not apply to nested/embedded requests.

    See also DefaultThumbPix in the Image Serving API. 

    expiration 36000000

    Default client cache time to live. Provides a default expiration interval in case a particular catalog record does not contain a valid catalog::Expiration value.

    Real number, 0 or greater. Number of milliseconds until expiration since the reply data was generated. Set to 0 to always expire the reply image immediately, which effectively disables client caching. By default, this value is set to 10 hours, which means that if a new image is published, it takes 10 hours for the old image to leave the user's cache. Contact Customer Care if you need the cache cleared sooner.

    See also Expiration in the Image Serving API.

    jpegquality 80

    Default JPEG encoding attributes. Specifies the default attributes for JPEG reply images.

    Integer number and flag, separated by a comma. The first value is in the range 1..100 and defines the quality. The second value may be 0 for normal behavior, or 1 to disable the RGB chromaticity down-sampling usually employed by JPEG encoders.

    See also JpegQuality in the Image Serving API.

    maxpix 2000,2000

    Reply image size limit. Maximum reply image width and height that is returned to the client.

    The server returns an error if a request causes a reply image whose width or height is larger than attribute::MaxPix.

    See also MaxPix in the Image Serving API.

    resmode SHARP2

    Default resampling mode. Specifies the default resampling and interpolation attributes to be used for scaling image data.

    Used when resMode= is not specified in a request.

    Allowed values include BILIN, BICUB, or SHARP2.

    Enum. Set to 2 for bilin, 3 for bicub, or 4 for sharp2 interpolation mode. Use sharp2 for best results.

    See also ResMode in the Image Serving API.

    resolution 72

    Default object resolution. Provides a default object resolution in case a particular catalog record does not contain a valid catalog::Resolution value.

    Real number, larger than 0. Typically expressed as pixels per inch, but may also be in other units, such as pixels per meter.

    See also Resolution in the Image Serving API.

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 managment uses ICC profiles, a format defined by the International Color Consortium (ICC).

To configure dynamic media color managment, you must install one feature pack and configure the default color profiles. See Installing the Feature Pack for information on how to install it.

You can also 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:

Poznámka:

This functionality is only available if you have Feature Pack 12692 installed. All feature packs and service packs are available via Package Share.

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:

  1. In Tools > GeneralCRXDE Lite, navigate to /etc/dam/imageserver/configuration/settings which contains the default Adobe Color Profiles.

    chlImage_1
  2. Add a color correction property by scrolling to the bottom of the Properties tab and manually entering the property name, type, and value, which are described in the following tables. After you enter the values, click Add and then Save All to save your values.

    Color correction properties are described in the Color Corrections Properties table. Values that you can assign to color correction properties are in the Color Profile table.

    For example, in Name, add iccprofilecmyk, select Type String, and add WebCoated as a Value. Then click Add and then Save All to save your values.

    chlImage_1

    Color Correction Properties Table

    Property Type Default Description
    iccprofilergb String <empty> Name of the default RGB color profile.
    iccprofilecmyk String <empty> Name of the default CMYK color profile.
    iccprofilegray String <empty> Name of the default Gray color profile.
    iccprofilesrcrgb String <empty> Name of the default RGB color profile used for RGB images that do not have an embedded color profile
    iccprofilesrccmyk String <empty> Name of the default CMYK color profile used for CMYK images that do not have an embedded color profile.
    iccprofilesrcgray String <empty> Name of the default Gray color profile used for CMYK images that do not have an embedded color profile.
    iccblackpointcompensation Boolean True Specifies whether black point compensation should be done during color correction. Adobe recommends this to be on.
    iccdither Boolean False Specifies whether dithering should be done during color correction.
    iccrenderintent String relative

    Specifies the render intent. Acceptable values are: perceptual, relative, saturation, absolute. Adobe recommends relative as the default.

    Poznámka:

    Property names are case sensitive and need to be all lowercase.

    Color Profile Table

    The following color profiles are installed with the feature packs:

    Name

    Colorspace

    Description

    AdobeRGB RGB Adobe RGB (1998)
    AppleRGB RGB Apple RGB
    CIERGB RGB CIE RGB
    CoatedFogra27 CMYK Coated FOGRA27 (ISO 12647-2:2004)
    CoatedFogra39 CMYK Coated FOGRA39 (ISO 12647-2:2004)
    CoatedGraCol CMYK Coated GRACoL 2006 (ISO 12647-2:2004)
    ColorMatchRGB RGB ColorMatch RGB
    EuropeISOCoated CMYK Europe ISO Coated FOGRA27
    EuroscaleCoated CMYK Euroscale Coated v2
    EuroscaleUncoated CMYK Euroscale Uncoated v2
    JapanColorCoated CMYK Japan Color 2001 Coated
    JapanColorNewspaper CMYK Japan Color 2002 Newspaper
    JapanColorUncoated CMYK Japan Color 2001 Uncoated
    JapanColorWebCoated CMYK Japan Color 2003 Web Coated
    JapanWebCoated CMYK Japan Web Coated (Ad)
    NewsprintSNAP2007 CMYK US Newsprint (SNAP 2007)
    NTSC RGB NTSC (1953)
    PAL RGB PAL/SECAM
    ProPhoto RGB ProPhoto RGB
    PS4Default CMYK Photoshop 4 Default CMYK
    PS5Default CMYK Photoshop 5 Default CMYK
    SheetfedCoated CMYK U.S. Sheetfed Coated v2
    SheetfedUncoated CMYK U.S. Sheetfed Uncoated v2
    SMPTE RGB SMPTE-C
    sRGB RGB sRGB IEC61966-2.1
    UncoatedFogra29 CMYK Uncoated FOGRA29 (ISO 12647-2:2004)
    WebCoated CMYK U.S. Web Coated (SWOP) v2
    WebCoatedFogra28 CMYK Web Coated FOGRA28 (ISO 12647-2:2004)
    WebCoatedGrade3 CMYK Web Coated SWOP 2006 Grade 3 Paper
    WebCoatedGrade5 CMYK Web Coated SWOP 2006 Grade 5 Paper
    WebUncoated CMYK U.S. Web Uncoated v2
    WideGamutRGB RGB Wide Gamut RGB
  3. Tap or click Save All.

For example, you could set the iccprofilergb to sRGB, and iccprofilecmyk to WebCoated. 

Doing so would do the following:

  • Enables color correction for RGB and CMYK images.
  • RGB images that do not have a color profile will be assumed to be in the sRGB color space.
  • CMYK images that do not have a color profile will be assumed to be in WebCoated color space.
  • Dynamic renditions that return RGB output, will return it in the sRGB color space.
  • Dynamic renditions that return CMYK output, will return it in the WebCoated color space.

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.

When you... Result
Copy an image URL

The Copy URL dialog box displays a URL similar to following (link is for demonstration purposes only; it is not an active link): 

http://IMAGESERVICEPUBLISHNODE/is/image/content/dam/path/to/Image.jpg?$preset$

Where IMAGESERVICEPUBLISHNODE refers to the Image Service URL.

See also Delivering Dynamic Media Assets.

Copy a viewer URL

The Copy URL dialog box displays a URL similar to the following (link is for demonstration purposes only; it is not an active link):

http://PUBLISHNODE/etc/dam/viewers/s7viewers/html5/BasicZoomViewer.html?asset=/content/dam/path/to/Image.jpg&config=/etc/dam/presets/viewer/Zoom_dark&serverUrl=http://IMAGESERVICEPUBLISHNODE/is/image/&contentRoot=%2F

Where PUBLISHNODE refers to the regular AEM publish node and IMAGESERVICEPUBLISHNODE refers to the Image Service URL.

See also Delivering Dynamic Media Assets.

Copy a viewer's embed code

The Copy Embed Code dialog box displays a code snippet similar to the following:

<style type="text/css">
    #s7basiczoom_div.s7basiczoomviewer{
         width:100%;
         height:auto;
    }
</style>
<script
 type="text/javascript" src="http://PUBLISHNODE/etc/dam/viewers/s7viewers/html5/js/BasicZoomViewer.js"></script>
<div id="s7basiczoom_div"></div>
<script type="text/javascript">
    var s7basiczoomviewer = new s7viewers.BasicZoomViewer({
        "containerId" : "s7basiczoom_div",
        "params" : {
            "serverurl" : "http://IMAGESERVICEPUBLISHNODE/is/image/",
            "contenturl" : "http://PUBLISHNODE/",
            "config" : "/etc/dam/presets/viewer/Zoom_dark",
            "asset" : "/content/dam/path/to/Image.jpg" }
    }).init();
</script>

Where PUBLISHNODE refers to the regular AEM publish node and IMAGESERVICEPUBLISHNODE refers to the Image Service URL.

See also Delivering Dynamic Media Assets.

WCM Dynamic Media and Interactive Media Components

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

Licencia na používanie tohto diela sa poskytuje v súlade s podmienkami licencie Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License  Na príspevky v sociálnych sieťach Twitter™ a Facebook sa nevzťahujú podmienky licencií Creative Commons.

Právne upozornenia   |   Zásady ochrany osobných údajov online