DocumentationAEM as a Cloud ServiceUser Guide

About configuring Dynamic Media Cloud Service configuring-dynamic-media

Last update: Wed Sep 04 2024 00:00:00 GMT+0000 (Coordinated Universal Time)
  • Rubriques :

Créé pour :

  • Administration
  • Utilisateur ou utilisatrice
TIP
Are you new to Dynamic Media? For a quick, high-level overview of Dynamic Media, see Work with Dynamic Media.

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

See also Configure a Dynamic Media company alias account

Architecture diagram of Dynamic Media architecture-diagram-of-dynamic-media

The following architecture diagram describes how Dynamic Media works.

With the new architecture, Experience Manager is responsible for primary source assets and syncs with Dynamic Media for asset processing and publishing:

  1. When the primary source asset is uploaded to Adobe Experience Manager as a Cloud Service, it is replicated to Dynamic Media. At that point, Dynamic Media handles all asset processing and rendition generation, such as video encoding and dynamic variants of an image.
  2. After the renditions are generated, Experience Manager as a Cloud Service can securely access and preview the remote Dynamic Media renditions (no binaries are sent back to the Experience Manager as a Cloud Service instance).
  3. After content is ready to publish and approve, it triggers the Dynamic Media service to push content to delivery servers and cache content at the CDN (Content Delivery Network).

chlimage_1-550

NOTE
The following list of features requires you to use the out-of-the-box CDN that is bundled with Adobe Experience Manager - Dynamic Media. Any other custom CDN is not supported with these features.

Create a Dynamic Media Configuration in Cloud Services configuring-dynamic-media-cloud-services

  1. In Experience Manager as a Cloud Service, select the Experience Manager as a Cloud Service logo to access the global navigation console.

  2. On the left of the console, select the Tools icon, then go to Cloud Services > Dynamic Media Configuration.

  3. On the Dynamic Media Configuration Browser page, in the left pane, select global (do not select the folder icon to the left of global). Then select Create.

  4. On the Create Dynamic Media Configuration page, enter the title, Dynamic Media account email address, and password of the company administrator of the Dynamic Media account, then select your region. This information is provided to you by Adobe in the provisioning email. Contact Adobe Customer Support if you did not receive this email.

  5. Select Connect to Dynamic Media.

  6. In the Change Password dialog box, in the New Password field, enter a new password that consists of 8-25 characters. The password must contain at least one of each of the following:

    • Uppercase letter
    • Lowercase letter
    • Number
    • Special character: # $ & . - _ : { }

    The Current Password field is intentionally pre-filled and hidden from interaction.

    If necessary, you can check the spelling of a password you have typed or retyped by selecting the password eye icon to reveal the password. Select the icon again to hide the password.

  7. In the Repeat Password field, retype the new password, then select Done.

    The new password is saved when you select Save in the upper-right corner of the Create Dynamic Media Configuration page.

    If you selected Cancel in the Change Password dialog box, you must still enter a new password when you save the created Dynamic Media configuration.

    See also Change the password to Dynamic Media.

  8. When the connection is successful, you can set the following:

    table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2 5-row-2
    Property Description
    Company The name of the Dynamic Media account.
    Important: Only one Dynamic Media Configuration in Cloud Services is supported on an instance of Experience Manager; do not add more than one configuration. Multiple Dynamic Media Configurations on an Experience Manager instance is not supported or recommended by Adobe.
    See also Configure a Dynamic Media company alias account.
    Company Root Folder Path Your company’s root folder path.
    Publishing Assets You can choose from the following three options:
    Immediately - When assets are uploaded, the system ingests the assets and provides the URL/Embed instantly. There is no user intervention necessary to publish assets.
    On Activation - You must explicitly publish the asset first before a URL/Embed link is provided.
    Selective Publish - Assets are auto published for secure preview only. They can also be explicitly published to Experience Manager as a Cloud Service without publishing to DMS7 for delivery in the public domain. In the future, this option intends to publish assets to Experience Manager as a Cloud Service and publish assets to Dynamic Media, mutually exclusive of each other. That is, you can publish assets to DMS7 so you can use features such a Smart Crop or dynamic renditions. Or, you can publish assets exclusively in Experience Manager as a Cloud Service for previewing; those same assets are not published in DMS7 for delivery in the public domain.
    Secure Preview Server Lets you specify the URL path to your secure renditions preview server. That is, after renditions are generated, Experience Manager as a Cloud Service can securely access and preview the remote Dynamic Media renditions (no binaries are sent back to the Experience Manager as a Cloud Service instance).
    Unless you have a special arrangement to use your own company’s server or a special server, Adobe recommends that you leave this setting as specified.
    Sync all content Selected by default. Deselect this option if you want to selectively include or exclude assets from the sync to Dynamic Media. Deselecting this option lets you can choose from the following two Dynamic Media sync modes:
    Dynamic Media sync mode
    Enable by default - The configuration is applied to all folders by default unless you mark a folder specifically for exclusion.
    Disabled by default - The configuration is not applied to any folder until you explicitly mark a selected folder for sync to Dynamic Media.
    To mark a selected folder for sync to Dynamic Media, select an asset folder, then in the toolbar, select Properties. On the Details tab, in the Dynamic Media sync mode drop-down list, choose from the following three options. When you are done, select Save. Remember: these three options are not available if you selected Sync all content earlier. See also Work with Selective Publish at the folder level in Dynamic Media.
    Inherited - No explicit sync value on the folder. Instead, the folder inherits the sync value from one of its ancestor folders or the default mode in the cloud configuration. The detailed status for inherited shows by way of a tooltip.
    Enable for subfolders - Include everything in this subtree for sync to Dynamic Media. The folder-specific settings override the default mode in the cloud configuration.
    Disabled for subfolders - Exclude everything in this subtree from syncing to Dynamic Media.
    note note
    NOTE
    There is no support for versioning in Dynamic Media. Also, delayed activation applies only if Publish Assets in the Edit Dynamic Media Configuration page is set to Upon Activation. And then, only until the first time the asset is activated.
    After an asset is activated, any updates are immediately published live to S7 Delivery.

    dynamicmediaconfiguration2updated

  9. Select Save. The new Dynamic Media password and configuration is saved. If you selected Cancel instead, no password update occurs.

  10. In the Configuring Dynamic Media dialog box, select OK to begin the configuration.

    note important
    IMPORTANT
    When the new Dynamic Media configuration finishes its setup, you receive a status notification within Experience Manager as a Cloud Service’s Inbox.
    This Inbox notification informs you if the configuration was either successful or not.
    See Troubleshoot a new Dynamic Media configuration and Your Inbox for more information.

  11. To securely preview Dynamic Media content before it gets published, Experience Manager as a Cloud Service uses token-based validation and hence Experience Manager Author previews Dynamic Media content by default. However, you can allowlist more IPs to provide users access to securely preview content. To set up this action in Experience Manager as a Cloud Service, see Configure Dynamic Media Publish Setup for Image Server - Security tab.

You are now finished with the basic configuration; you are ready to use Dynamic Media.

If you want to further customize your configuration, such as enabling ACL (Access Control List) permissions, you can optionally complete any of the tasks under Configure Advanced Settings in Dynamic Media.

Troubleshoot a new Dynamic Media configuration troubleshoot-dm-config

When a new Dynamic Media configuration finishes its setup, you receive a status notification within Experience Manager as a Cloud Service’s Inbox. This notification informs you if the configuration was either successful or not, as seen in the following respective images from the Inbox.

Experience Manager Inbox success

Experience Manager Inbox failure

See also Your Inbox.

To troubleshoot a new Dynamic Media configuration:

  1. Near the upper-right corner of the Experience Manager as a Cloud Service page, select the bell icon, then select View All.

  2. On the Inbox page, select the success notification to read an overview of the status and logs of the configuration.

    If the configuration failed, select the failure notification similar to the following screenshot.

    Dynamic Media setup failed

  3. On the DMSETUP page, review the configuration details that describe the failure. In particular, take note of any error messages or error codes. Contact Adobe Customer Support with this information.

    Dynamic Media Set up page

Change the password to Dynamic Media change-dm-password

Password expiration in Dynamic Media is set to 100 years from the current system date.

The password must contain at least one of each of the following:

  • Uppercase letter
  • Lowercase letter
  • Number
  • Special character: # $ & . - _ : { }

If necessary, you can check the spelling of a password you have typed or retyped by selecting the password eye icon to reveal the password. Select the icon again to hide the password.

The changed password is saved when you select Save in the upper-right corner of the Edit Dynamic Media Configuration page.

  1. In Experience Manager as a Cloud Service, select the Experience Manager as a Cloud Service logo to access the global navigation console.

  2. On the left of the console, select the Tools icon, then go to Cloud Services > Dynamic Media Configuration.

  3. On the Dynamic Media Configuration Browser page, in the left pane, select global. Do not select the folder icon to the left of global. Then, select Edit.

  4. On the Edit Dynamic Media Configuration page, directly below the Password field, select Change Password.

  5. In the Change Password dialog box, do the following:

    • In the New Password field, enter a new password.

      The Current Password field is intentionally pre-filled and hidden from interaction.

    • In the Repeat Password field, retype the new password, then select Done.

  6. In the upper-right corner of the Edit Dynamic Media Configuration page, select Save, then select OK.

(Optional) Configure Advanced Settings in Dynamic Media optional-configuring-advanced-settings-in-dynamic-media-scene-mode

To further customize the configuration and setup of Dynamic Media, or optimize its performance, you can complete one or more of the following optional tasks:

(Optional) Enable Access Control List permissions in Dynamic Media optional-enable-acl

When you run Dynamic Media on AEM, it currently forwards /is/image requests to Secure Preview Image Serving without checking ACL (Access Control List) permissions on the PlatformServerServlet. You can, however, enable ACL permissions. Doing so forwards the authorized /is/image requests. If a user is not authorized to access the asset, a “403 - Forbidden” error is displayed.

To enable ACL permissions in Dynamic Media:

  1. From Experience Manager, navigate to Tools > Operations > Web Console.

    2019-08-02_16-13-14

  2. A new browser tab opens to the Adobe Experience Manager Web Console Configuration page.

    2019-08-02_16-17-29

  3. On the page, scroll to the name Adobe CQ Scene7 PlatformServer.

  4. To the right of the name, select the pencil icon (Edit the configuration values).

  5. On the com.adobe.cq.dam.s7imaging.impl.ps.PlatformServerServlet.name page, select the check box for the following two settings:

    • com.adobe.cq.dam.s7imaging.impl.ps.PlatformServerServlet.cache.enable.name – When enabled, this setting caches permission results for two minutes (default) to save.
    • com.adobe.cq.dam.s7imaging.impl.ps.PlatformServerServlet.validate.userAccess.name – When enabled, this setting validates a user’s access while they preview assets by way of Dynamic Media Image Server.

    Enable Access Control List settings in Dynamic Media - Scene7 mode

  6. Near the lower-right corner of the page, select Save.

(Optional) Setup and configuration of Dynamic Media settings optional-setup-and-configuration-of-dynamic-media-scene-mode-settings

Use the Dynamic Media Classic user interface to change your Dynamic Media settings.

Setup and configuration tasks include the following:

Configure Dynamic Media Publish Setup for Image Server publishing-setup-for-image-server

The Dynamic Media Publish Setup page establishes default settings that determine how assets are delivered from Adobe Dynamic Media servers to web sites or applications.

See Configure Dynamic Media Publish Setup for Image Server.

Configure Dynamic Media General Settings configuring-application-general-settings

Configure the Dynamic Media Publish Server Name URL and the Origin Server Name URL. You can also specify Upload to Application settings and Default Upload Options all based on your particular use case.

See Configure Dynamic Media General Settings.

Configure color management configuring-color-management

Dynamic Media color management lets you color correct assets. With color correction, ingested assets retain their color space (RGB, CMYK, Gray) and embedded color profile. When you request a dynamic rendition, the image color is corrected into the target color space using CMYK, RGB, or Gray output.

See Configure Image Presets.

To configure the default color properties for enabling color correction when requesting images:

  1. Open the Dynamic Media Classic desktop application, then sign in to your account using credentials provided during provisioning.

  2. Go to Setup > Application Setup.

  3. Expand the Publish Setup area and select Image Server. Set Publish Context to Image Serving when setting defaults for publish instances.

  4. Scroll to the property that you must change, for example, a property in the Color Management Attributes area.
    You can set the following color correction properties:

    table 0-row-2 1-row-2 2-row-2 3-row-2 4-row-2
    Property Description
    CMYK Default Color Space Name of the default CMYK color profile.
    Grayscale Default Color Space Name of the default Gray color profile.
    RGB Default Color Space Name of the default RGB color profile.
    Color Conversion Rendering Intent Specifies the render intent. Acceptable values are: perceptual, relative colometric, saturation, absolute colometric. Adobe recommends relative as the default.

  5. Select Save.

For example, you could set the RGB Default Color Space to sRGB, and CMYK Default Color Space 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 are assumed to be in the sRGB color space.
  • CMYK images that do not have a color profile are assumed to be in WebCoated color space.
  • Dynamic renditions that return RGB output, return it in the sRGB color space.
  • Dynamic renditions that return CMYK output, return it in the WebCoated color space.

Edit MIME types for supported formats editing-mime-types-for-supported-formats

You can define which asset types are processed by Dynamic Media and customize advanced asset processing parameters. For example, you can specify asset processing parameters to do the following:

  • Convert an Adobe PDF to an eCatalog asset.
  • Convert an Adobe Photoshop Document (.PSD) to a banner template asset for personalization.
  • Rasterize an Adobe Illustrator file (.AI) or an Adobe Photoshop Encapsulated PostScript® file (.EPS).
  • Video Profiles and Image Profiles can be used to define processing of videos and images, respectively.

See Upload assets.

To edit MIME types for supported formats:

  1. Sign in to your Experience Manager as a Cloud Service as the product administrator.

  2. In Experience Manager as a Cloud Service , select the Experience Manager as a Cloud Service logo to access the global navigation console, then go to General > CRXDE Lite.

    If you do not have access to CRXDE Lite, see Using CRXDE Lite.

  3. In the left rail, navigate to the following:

    /conf/global/settings/cloudconfigs/dmscene7/jcr:content/mimeTypes

    MIME types

  4. Under the mimeTypes folder, select a MIME type.

  5. On the right side of the CRXDE Lite page, in the lower portion:

    • Double-select the enabled field. By default all asset MIME types are enabled (set to true), which means the assets are synced to Dynamic Media for processing. If you want to exclude this asset MIME type from being processed, change this setting to false.

    • Double-select jobParam to open its associated text field. See Supported MIME Types for a list of permitted processing parameter values that you can use for a given MIME type.

  6. Do one of the following:

    • Repeat steps 3-4 to edit more MIME types.
    • On the menu bar of the CRXDE Lite page, select Save All.

  7. In the upper-left corner of the page, select CRXDE Lite to return to Experience Manager as a Cloud Service.

Add MIME types for unsupported formats adding-mime-types-for-unsupported-formats

You can add custom MIME types for unsupported formats in Experience Manager Assets. To ensure any new node that you add in CRXDE Lite is not deleted by Experience Manager, move the MIME type before image_. Also, ensure that its enabled value is set to false.

To add MIME types for unsupported formats:

  1. Sign in to your Experience Manager as a Cloud Service as the product administrator.

  2. From Experience Manager as a Cloud Service, go to Tools > Operations > Web Console.

    2019-08-02_16-13-14

  3. A new browser tab opens to the Adobe Experience Manager Web Console Configuration page.

    2019-08-02_16-17-29

  4. On the page, scroll down to the name Adobe CQ Scene7 Asset MIME type Service as seen the following screenshot. To the right of the name, select the Edit the configuration values (pencil icon).

    Edit the configuration values

  5. On the Adobe CQ Scene7 Asset MIME type Service page, select any plus sign icon <+>. The location in the table where you select the plus sign to add the new MIME type is trivial.

    Adobe CQ Scene7 Asset Mime Type Service

  6. Type DWG=image/vnd.dwg in the empty text field that you just added.

    The DWG=image/vnd.dwg MIME type is for sample purposes only. The MIME type that you add here can be any other unsupported format.

    Adding DWG mime type

  7. In the lower-right corner of the page, select Save.

    At this point, you can close the browser tab that has the open Adobe Experience Manager Web Console Configuration page.

  8. Return to the browser tab that has your open Experience Manager as a Cloud Service console.

  9. From Experience Manager as a Cloud Service, go to Tools > General > CRXDE Lite.

    If you do not have access to CRXDE Lite, see Using CRXDE Lite.

    Tools > General > CRXDE Lite

  10. In the left rail, navigate to the following:

    conf/global/settings/cloudconfigs/dmscene7/jcr:content/mimeTypes

  11. Drag the MIME type image_vnd.dwg and drop it directly above image_ in the tree as seen in the following screenshot.

    Editing a DWG file in CRXDE Lite

  12. With the MIME type image_vnd.dwg still selected, from the Properties tab, in the enabled row, under the Value column header, double-select the value. The Value drop-down list is opened.

  13. Type false in the field (or select false from the drop-down list).

    Editing mime types in CRXDE Lite

  14. Near the upper-left corner of the CRXDE Lite page, select Save All.

(Optional) Tune the performance of Dynamic Media optional-tuning-the-performance-of-dynamic-media-scene-mode

To keep Dynamic Media running smoothly, Adobe recommends the following synchronization performance/scalability fine-tuning tips:

Update the predefined Job parameters for processing of different file formats update-job-para

You can tune job parameters for faster processing when you upload files. For example, if you upload PSD files, but do not want to process them as templates, you can set layer extraction to false (off). In such case, the tuned job parameter appears as follows: process=None&createTemplate=false.

In case you do want to turn on template creation, use the following parameters: process=MaintainLayers&layerNaming=AppendName&createTemplate=true.

Adobe recommends using the following “tuned” job parameters for PDF, PostScript®, and PSD files:

File type
Recommended job parameters
PDF
pdfprocess=Rasterize&resolution=150&colorspace=Auto&pdfbrochure=false&keywords=false&links=false
PostScript®
psprocess=Rasterize&psresolution=150&pscolorspace=Auto&psalpha=false&psextractsearchwords=false&aiprocess=Rasterize&airesolution=150&aicolorspace=Auto&aialpha=false
PSD
process=None&layerNaming=AppendName&anchor=Center&createTemplate=false&extractText=false&extendLayers=false

To update any of these parameters, see Editing MIME types for supported formats.

See also Adding MIME types for unsupported formats.

Update the predefined Granite Workflow Queue (video assets) worker threads update-granite-workflow-queue-worker-threads-video

The Granite Workflow queue is used for non-transient workflows. In Dynamic Media, it used to process video with the Dynamic Media Encode Video workflow.

NOTE
You must be signed in to Experience Manager as a Cloud Service as the product administrator to complete this task.

If you do not have access to OSGi, see OSGi Configuration.

To update the predefined Granite Workflow Queue (video assets) worker threads:

  1. Navigate to https://<server>/system/console/configMgr and search for Queue: Granite Workflow Queue.

    note note
    NOTE
    A text search is necessary instead of a direct URL because the OSGi PID is dynamically generated.

  2. In the Maximum Parallel Jobs field, change the number to the desired value.

    By default, the maximum number of parallel jobs depends on the number of available CPU cores. For example, on a 4-core server, it assigns two worker threads. (A value between 0.0 and 1.0 is ratio-based, or any numbers greater than one assigns the number of worker threads.)

    For most use cases, the 0.5 default setting is sufficient.

    Configuration of a job processing queue

  3. Select Save.

Update the predefined Granite Transient Workflow Queue worker threads update-granite-transient-workflow-queue-worker-threads-images

The Granite Transit Workflow queue is used for the DAM Update Asset workflow. In Dynamic Media, it is used for image and non-video asset ingestion and processing.

NOTE
You must be signed in to Experience Manager as a Cloud Service as the product administrator to complete this task.

To update the predefined Granite Transient Workflow queue worker threads:

  1. Navigate to the Adobe Experience Manager Web Console Configuration at http://<host>:<port>/system/console/configMgr

  2. Search for Queue: Granite Transient Workflow Queue.

    note note
    NOTE
    A text search is necessary instead of a direct URL because the OSGi PID is dynamically generated.

  3. In the Maximum Parallel Jobs field, change the number to the desired value.

    You can increase Maximum Parallel Jobs to adequately support heavy upload of files to Dynamic Media. The exact value depends on hardware capacity. In certain scenarios, such as an initial migration or a one-time bulk upload, you can use a large value. Be aware, however, that using a large value (such as two times the number of cores) can have negative effects on other concurrent activities. As such, test and adjust the value based on your particular use case.

    chlimage_1

  4. Select Save.

Update the maximum upload connections to the Dynamic Media Classic (Scene7) server update-max-s7-upload-connections

The Dynamic Media Classic (Scene7) Upload Connection setting synchronizes Experience Manager assets to Dynamic Media Classic servers.

NOTE
You must be signed in to Experience Manager as a Cloud Service as the product administrator to complete this task.

To update the maximum upload connections to the Dynamic Media Classic (Scene7) server:

  1. Navigate to https://<server>/system/console/configMgr/com.day.cq.dam.scene7.impl.Scene7UploadServiceImpl

  2. In the Number of connections field, or the Active job timeout field, or both, change the number as desired.

    The Number of connections setting controls the maximum number of HTTP connections allowed for Experience Manager to Dynamic Media upload. Typically, the predefined value of ten connections is sufficient.

    The Active job timeout setting determines the wait time for uploaded Dynamic Media assets to be published in delivery server. This value is 2100 seconds or 35 minutes by default.

    For most use cases, the setting of 2100 is sufficient.

    Adobe Scene7 Upload Service

  3. Select Save.

recommendation-more-help
fbcff2a9-b6fe-4574-b04a-21e75df764ab