If you use Adobe Experience Manager set up for different environments, such as development, staging, and production, configure Dynamic Media Cloud Services for each one of those environments.
The following architecture diagram describes how Dynamic Media - Scene7 mode works.
With the new architecture, Experience Manager is responsible for primary source assets and synchs with Dynamic Media for asset processing and publishing:
The following list of features requires that you 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.
Dynamic Media is disabled by default. To take advantage of Dynamic Media features, you must enable it.
Dynamic Media - Scene7 mode is for the Experience Manager Author instance only. As such, you must configure runmode=dynamicmedia_scene7
on the Experience Manager Author instance, not the Experience Manager Publish instance.
To enable Dynamic Media, you must start up Experience Manager using the dynamicmedia_scene7
run mode from the command line by entering the following in a terminal window (example port used is 4502):
java -Xms4096m -Xmx4096m -Doak.queryLimitInMemory=500000 -Doak.queryLimitReads=500000 -jar cq-quickstart-6.5.0.jar -gui -r author,dynamicmedia_scene7 -p 4502
Upgrading Experience Manager Dynamic Media from 6.3 to 6.4 or 6.5 now includes the ability for zero downtime deployments. To migrate all your presets and configurations from /etc
to /conf
in CRXDE Lite, be sure you run the following curl command.
If you run your Experience Manager instance in compatibility mode – that is, you have the compatibility packaged installed – you do not need to run these commands.
For all upgrades, either with or without the compatibility package, you can copy the default, out-of-the-box viewer presets that originally came with Dynamic Media by running the following Linux curl command:
curl -u admin:admin -X POST https://<server_address>:<server_port>/libs/settings/dam/dm/presets/viewer.pushviewerpresets.json
To migrate any custom viewer presets and configurations that you have created from /etc
to /conf
, run the following Linux curl command:
curl -u admin:admin -X POST https://<server_address>:<server_port>/libs/settings/dam/dm/presets.migratedmcontent.json
The installation of feature pack 18912 is optional.
Feature pack 18912 lets you either bulk ingest assets by way of FTP, or migrate assets from either Dynamic Media - Hybrid mode or Dynamic Media Classic into Dynamic Media - Scene7 mode on Experience Manager. It is available from Adobe Professional Services.
See Installing feature pack 18912 for bulk asset migration for more information.
Before you configure Dynamic Media – After you receive your provisioning email with Dynamic Media credentials, you must open the Dynamic Media Classic desktop application, then sign in to your account to change your password. The password provided in the provisioning email is system-generated and intended to be a temporary password only. It is important that you update the password so that Dynamic Media Cloud Service is set up with the correct credentials.
To create a Dynamic Media Configuration in Cloud Services
In Experience Manager, tap the Experience Manager logo to access the global navigation console and tap the Tools icon, then tap Cloud Services > Dynamic Media Configuration.
On the Dynamic Media Configuration Browser page, in the left pane, tap global (do not tap or select the folder icon to the left of global), then tap Create.
On the Create Dynamic Media Configuration page, enter a title, the Dynamic Media account email address, password, then select your region. This information is provided to you by Adobe in the provisioning email. Contact Adobe Customer Care if you did not receive the email.
Tap Connect to Dynamic Media.
After you receive your provisioning email with Dynamic Media credentials, open the Dynamic Media Classic desktop application, then sign in to your account to change your password. The password provided in the provisioning email is system-generated and intended to be a temporary password only. It is important that you update the password so that the Dynamic Media Cloud Service is set up with the correct credentials.
When the connection is successful, set the following. Headings with an asterisk (*) are required:
Company - the name of the Dynamic Media account. You have multiple Dynamic Media accounts. For example, you could have different subbrands, divisions, staging, or production environments.
Company Root Folder Path
Publishing Assets - You can choose from the following three options:
Secure Preview Server - lets you specify the URL path to your secure renditions preview server. That is, after renditions are generated, Experience Manager can securely access and preview the remote Dynamic Media renditions (no binaries are sent back to the Experience Manager 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
There is no support for versioning in DMS7. 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.
Tap Save.
To securely preview Dynamic Media content before it gets published, you must “allowlist” the Experience Manager author instance to connect to Dynamic Media:
Open the Dynamic Media Classic desktop application, then sign in to your account. Your credentials and sign-in details were provided by Adobe at the time of provisioning. If you do not have this information, contact Technical Support.
On the navigation bar near the top right of the page, tap Setup > Application Setup > Publish Setup > Image Server.
On the Image Server Publish page, in the Publish Context drop-down list, select Test Image Serving.
For the Client Address Filter, tap Add.
To enable (turn on) the address, select the check box. Enter the IP address of the Experience Manager Author instance (not Dispatcher IP).
Tap Save.
You are now finished with the basic configuration; you are ready to use Dynamic Media - Scene7 mode.
If you want to further customize your configuration, you can optionally complete any of the tasks under (Optional) Configuring Advanced Settings in Dynamic Media - Scene7 mode.
If you want to further customize the configuration and setup of Dynamic Media - Scene7 mode, or optimize its performance, you can complete one or more of the following optional tasks:
(Optional) Setup and configuration of Dynamic Media - Scene7 mode settings
(Optional) Tuning the performance of Dynamic Media - Scene7 mode
When you are in run mode dynamicmedia_scene7
, use the Dynamic Media Classic user interface to change your Dynamic Media settings.
Some of the tasks above require that you open the Dynamic Media Classic desktop application, then sign in to your account.
Setup and configuration tasks include the following:
The Publish Setup settings determine how assets are delivered by default from Dynamic Media. If no setting is specified, Dynamic Media delivers an asset according to the default settings defined in Publish Setup. For example, a request to deliver an image that does not include a resolution attribute yields an image with the Default Object Resolution setting.
To configure Publish Setup: in Dynamic Media Classic, tap Setup > Application Setup > Publish Setup > Image Server.
The Image Server screen establishes default settings for delivering images. See the UI screen for description of each setting.
To open the Application General Settings page, in Dynamic Media Classic Global Navigation bar, tap Setup > Application Setup > General Settings.
**Servers - **On account provisioning, Dynamic Media automatically provides the assigned servers for your company. These servers are used to construct URL strings for your web site and applications. These URL calls are specific to your account. Do not change any of the server names unless explicitly instructed to do so by Adobe Customer Care.
Overwrite Images - Dynamic Media does not allow two files to have the same name. Each item’s URL ID (the filename minus the extension) must be unique. These options specify how replacement assets are uploaded: whether they replace the original or become duplicate. Duplicate assets are renamed with a “-1” (for example, chair.tif is renamed chair-1.tif). These options affect assets uploaded to a different folder than the original or assets with a different filename extension from the original (such as JPG, TIF, or PNG).
To maintain consistency with Experience Manager, always choose this setting: Overwrite in current folder, same base image name/extension
Default Color Profiles - See Configuring Color Management for additional information.
By default, the system shows 15 renditions when you select Renditions and 15 viewer presets when you select Viewers in the asset’s detail view. You can increase this limit. See Increasing the number of image presets that display or Increasing the number of viewer presets that display.
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 Configuring Image Presets.
To configure the default color properties so color correction is enabled when images are requested:
Open the Dynamic Media Classic desktop application, then sign in to your account using credentials provided during provisioning.
Navigate to Setup > Application Setup.
Expand the Publish Setup area and select Image Server. Set Publish Context to Image Serving when setting defaults for publish instances.
Scroll to the property you want to change. For example, a property in the Color Management Attributes area.
You can set the following color correction properties:
Tap 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:
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:
See Uploading Assets.
To edit MIME types for supported formats
In Experience Manager, tap the Experience Manager logo to access the global navigation console, then tap Tools > General > CRXDE Lite.
In the left rail, navigate to the following:
/conf/global/settings/cloudconfigs/dmscene7/jcr:content/mimeTypes
Under the mimeTypes folder, select a mime type.
On the right side of the CRXDE Lite page, in the lower portion:
double-click the enabled field. By default all asset mime types are enabled (set to true), which means the assets are synched to Dynamic Media for processing. If you wish to exclude this asset mime type from being processed, change this setting to false.
double-tap jobParam to open its associated text field. See Supported Mime Types for a list of permitted processing parameter values you can use for a given mime type.
Do one of the following:
In the upper-left corner of the page, tap CRXDE Lite to return to Experience Manager.
You can add custom MIME types for unsupported formats in Experience Manager Assets. Ensure that any new node you add in CRXDE Lite is not deleted by Experience Manager by moving the MIME type before image_
. Also, be sure that its enabled value is set to false.
To add MIME types for unsupported formats
From Experience Manager, tap Tools > Operations > Web Console.
A new browser tab opens to the Adobe Experience Manager Web Console Configuration page.
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, tap the Edit the configuration values (pencil icon).
On the Adobe CQ Scene7 Asset MIME type Service page, tap any plus sign icon <+>. The location in the table where you tap the plus sign to add the new mime type is trivial.
Type DWG=image/vnd.dwg
in the empty text field that you just added.
The example DWG=image/vnd.dwg
is for illustration purposes only. The MIME type that you add here can be any other unsupported format.
In the lower-right corner of the page, tap Save.
At this point, you can close the browser tab that has the open Adobe Experience Manager Web Console Configuration page.
Return to the browser tab that has your open Experience Manager console.
From Experience Manager, tap Tools > General > CRXDE Lite.
In the left rail, navigate to the following:
conf/global/settings/cloudconfigs/dmscene7/jcr:content/mimeTypes
Drag the mime type image_vnd.dwg
and drop it directly above image_
in the tree as seen in the following screenshot.
With the mime type image_vnd.dwg
still selected, from the Properties tab, in the enabled row, under the Value column header, double-tap the value to open the Value drop-down list.
Type false
in the field (or select false from the drop-down list).
Near the upper-left corner of the CRXDE Lite page, tap Save All.
Use batch set presets to automate the creation of image sets or spin sets while assets are uploaded to Dynamic Media.
First, define the naming convention for how assets are grouped in a set. Then create a batch set preset that is a uniquely named, self-contained set of instructions. It must define how to construct the set using images that match the defined naming conventions in the preset recipe.
When you upload files, Dynamic Media automatically creates a set with all files that match the defined naming convention in the active presets.
Configuring default naming
Create a default naming convention that is used in any batch set preset recipe. The default naming convention selected in the batch set preset definition is likely all that is needed by your company to batch-generate sets. A batch set preset is created to use the default naming convention that you define. You are able to create as many Batch Set presets with alternate, custom naming conventions needed for a particular set of content in cases where there is an exception to the company-defined default naming.
While setting up a default naming convention is not required to use batch set preset functionality, best practice recommends that you use the default naming convention. It lets you define as many elements of your naming convention that you want grouped in a set so you can streamline batch set creation.
As an alternative, you can use View Code with no form fields available. In this view, you create your naming convention definitions entirely using regular expressions.
Two elements are available for definition, Match and Base Name. These fields let you define all elements of a naming convention and identify the part of the convention used to name the set in which they are contained. A company’s individual naming convention often uses one or more lines of definition for each of these elements. You can use as many lines for your unique definition and group them into distinct elements, such as for Main Image, Color element, Alternate View element, and Swatch element.
To configure default naming
Open the Dynamic Media Classic desktop application, then sign in to your account.
Your credentials and sign-in details were provided by Adobe at the time of provisioning. If you do not have this information, contact Technical Support.
On the navigation bar near the top of the page, tap Setup > Application Setup > Batch Set Presets > Default Naming.
Select View Form or View Code to specify how you want to view and enter information about each element.
You can select the View Code check box to view the regular expression value building alongside your form selections. You are able to enter or alter these values to help define the elements of the naming convention, if the form view limits you for any reason. If your values are unable to be parsed in the form view, the form fields become inactive.
De-activated form fields perform no validation that your regular expressions are correct. You see results of the regular expression you are building for each element after the Result line. The complete regular expression is visible at the bottom of the page.
Expand each element as necessary and enter the naming conventions you want to use.
As necessary, do any of the following:
Do one of the following:
Creating a Batch Set Preset
Dynamic Media uses batch set presets to organize assets into sets of images (alternate images, color options, 360 spin) for display in viewers. The batch set presets automatically run alongside the asset upload processes in Dynamic Media.
You can create, edit, and manage your batch set presets. There are two forms of batch set preset definitions: one for a default naming convention that you can set up, and one for custom naming conventions that you create on the fly.
You can use either the form field method to define a batch set preset or the code method, which lets you use regular expressions. As in Default Naming, you can choose View Code at the same time you are defining in the Form View and use regular expressions to build your definitions. Alternately, you can uncheck either view to use one or the other exclusively.
To create a Batch Set Preset
Open the Dynamic Media Classic desktop application, then sign in to your account.
Your credentials and sign-in details were provided by Adobe at the time of provisioning. If you do not have this information, contact Technical Support.
On the navigation bar near the top of the page, tap Setup > Application Setup > Batch Set Presets > Batch Set Preset.
View Form, as set in the upper-right corner of the Details page, is the default view.
In the Preset List panel, tap Add to activate the definition fields in the Details panel on the right-hand side of the screen.
In the Details panel, in the Preset Name field, type a name for the preset.
In the Batch Set Type drop-down menu, select a preset type.
Do one of the following:
If you are using a default naming convention that you previously set up under Application Setup > Batch Set Presets > Default Naming, expand Asset Naming Conventions, and then in the File Naming drop-down list, tap Default.
To define a new naming convention as you set up the preset, expand Asset Naming Conventions, and then in the File Naming drop-down list, tap Custom.
For Sequence order, define the order in which images are displayed after the set is grouped in Dynamic Media.
By default, your assets are ordered alphanumerically. However, you can use a comma-separated list of regular expressions to define the order.
For Set Naming and Creation Convention, specify the suffix or prefix to the base name you defined in the Asset Naming Convention. Also, define where the set is created within the Dynamic Media folder structure.
If you define large numbers of sets, keep the sets separate from the folders that contain the assets themselves. For example, create an Image Sets folder and put generated sets here.
In the Details panel, tap Save.
Tap Active next to the new preset name.
Activating the preset ensures that when you upload assets to Dynamic Media, the batch set preset is applied to generate the set.
Creating a Batch Set Preset for the auto-generation of a 2D Spin Set
You can use the Batch Set Type Multi-Axis Spin Set to create a recipe that automates the generation of 2D Spin Sets. The grouping of images uses Row and Column regular expressions so that the image assets are properly aligned in the corresponding location in the multi-dimensional array. There is no minimum or maximum number of rows or columns that you must have in a multi-axis spin set.
As an example, suppose you want to create a multi-axis spin set named spin-2dspin
. You have a set of spin set images that contain three rows, with 12 images per row. The images are named as follows:
spin-01-01
spin-01-02
…
spin-01-12
spin-02-01
…
spin-03-12
With this information, your Batch Set Type recipe can be created as follows:
Grouping for the shared asset name part of the spin set is added to the Match field (as highlighted). The variable part of the asset name containing the row and column is added to the Row and Column fields, respectively.
When the Spin Set is uploaded and published, you would activate the name of the 2D Spin Set recipe that is listed under Batch Set Presets in the Upload Job Options dialog box.
To create a Batch Set Preset for the auto-generation of a 2D Spin Set
Open the Dynamic Media Classic desktop application, then sign in to your account.
Your credentials and sign-in details were provided by Adobe at the time of provisioning. If you do not have this information, contact Technical Support.
On the navigation bar near the top of the page, tap Setup > Application Setup > Batch Set Presets > Batch Set Preset.
View Form, as set in the upper-right corner of the Details page, is the default view.
In the Preset List panel, tap Add to activate the definition fields in the Details panel on the right-hand side of the screen.
In the Details panel, in the Preset Name field, type a name for the preset.
In the Batch Set Type drop-down menu, select Asset Set.
In the Sub Type drop-down list, select Multi-Axis Spin Set.
Expand Asset Naming Conventions, and then in the File Naming drop-down list, tap Custom.
Use the Match and, optionally, Base Name attributes to define a regular expression for the naming of image assets that make up the grouping.
For example, your literal Match regular expression can look like the following:
(w+)-w+-w+
Expand Row Column Position, and then define the name format for the position of the image asset within the 2D Spin Set array.
Use the parenthesis to embrace the row or column position in the file name.
For example, for your row regular expression, it can look like the following:
\w+-R([0-9]+)-\w+
or
\w+-(\d+)-\w+
For your column regular expression, it can look like the following:
\w+-\w+-C([0-9]+)
or
\w+-\w+-C(\d+)
The samples above are for illustration purposes only. You can create your regular expression however you want to suit your needs.
If the combination of row and column regular expressions is unable to determine the position of the asset within the multi-dimensional spin set array, the asset is not added to the set. An error is also logged.
For Set Naming and Creation Convention, specify the suffix or prefix to the base name you defined in the Asset Naming Convention.
Also, define where the spin set is created within the Dynamic Media Classic folder structure.
If you define large numbers of sets, keep the sets separate from the folders that contain the assets themselves. For example, create a Spin Sets folder to put generated sets here.
In the Details panel, tap Save.
Tap Active next to the new preset name.
Activating the preset ensures that when you upload assets to Dynamic Media, the batch set preset is applied to generate the set.
To keep Dynamic Media - Scene7 mode running smoothly, Adobe recommends the following synchronization performance/scalability fine-tuning tips:
You can tune job parameters for faster processing when you upload files. For example, if you are uploading 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 would appear as process=None&createTemplate=false
.
Adobe recommends using the following “tuned” job parameters for PDF, PostScript®, and PSD files:
File type | Recommended job parameters |
---|---|
pdfprocess=Thumbnail&resolution=150&colorspace=Auto&pdfbrochure=false&keywords=false&links=false |
|
PostScript® | psprocess=Rasterize&psresolution=150&pscolorspace=Auto&psalpha=false&psextractsearchwords=false&aiprocess=Thumbnail&airesolution=150&aicolorspace=Auto&aialpha=false |
PSD | process=None&layerNaming=Layername&anchor=Center&createTemplate=false&extractText=false&extendLayers=false |
To update any of these parameters, follow the steps in Enabling MIME type-based Assets/Dynamic Media Classic upload job parameter support.
The Granite Transit Workflow queue is used for the DAM Update Asset workflow. In Dynamic Media, it is used for image ingestion and processing.
To update the Granite transient workflow queue
Navigate to https://<server>/system/console/configMgr and search for Queue: Granite Transient Workflow Queue.
A text search is necessary instead of a direct URL because the OSGi PID is dynamically generated.
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 – that is, 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.
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.
To update the Granite workflow queue
Navigate to https://<server>/system/console/configMgr
and search for Queue: Granite Workflow Queue.
A text search is necessary instead of a direct URL because the OSGi PID is dynamically generated.
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 – that is, 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.
Tap Save.
The Scene7 Upload Connection setting synchronizes Experience Manager assets to Dynamic Media Classic servers.
To update the Dynamic Media Classic upload connection
Navigate to https://<server>/system/console/configMgr/com.day.cq.dam.scene7.impl.Scene7UploadServiceImpl
In the Number of connections field and/or the Active job timeout field, 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.
Tap Save.
In non-Dynamic Media deployments, you replicate all assets (both images and video) from your Experience Manager author environment to the Experience Manager publish node. This workflow is necessary because the Experience Manager publish servers also deliver the assets.
However, in Dynamic Media deployments, because assets are delivered by way of the Cloud Service, there is no need to replicate those same assets to Experience Manager publish nodes. Such a “hybrid publishing” workflow avoids extra storage costs and longer processing times to replicate assets. Other content, such as Site pages, continue to be served from the Experience Manager publish nodes.
The filters provide a way for you to exclude assets from being replicated to the Experience Manager publish node.
If you use Dynamic Media for imaging, or video, or both, you can use the default filters that Adobe provides 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:
|
Dynamic Media Video Delivery | filter-video | Starts with video/ | The out-of-the-box "filter-video" will:
|
Filters apply to MIME types and cannot be path-specific.
In Experience Manager, tap the Experience Manager logo to access the global navigation console and tap the Tools > General > CRXDE Lite.
In the left folder tree, navigate to /etc/replication/agents.author/publish/jcr:content/damRenditionFilters
to review the filters.
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
.
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
.
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.
If you only wanted to replicate the original, then you would enter +original
.