Configure Dynamic Media - Scene7 mode

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.

Architecture diagram of Dynamic Media - Scene7 mode

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:

1. When the primary source asset is uploaded to Experience Manager, 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.
   (In Dynamic Media - Scene7 mode, the default upload file size is 2 GB or less. To enable upload file sizes of 2 GB up to 15 GB, see (Optional) Configure Dynamic Media - Scene7 mode for upload of assets larger than 2 GB.)
2. After the 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).
3. After content is ready to be published and approved, it triggers the Dynamic Media service to push content out to delivery servers and cache content at the CDN (Content Delivery Network).

Enable Dynamic Media in Scene7 mode

Dynamic Media is disabled by default. To take advantage of Dynamic Media features, you must enable it.

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

(Optional) Migrate Dynamic Media presets and configurations from 6.3 to 6.5 Zero Downtime

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.

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

Install feature pack 18912 for bulk asset migration

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 Install feature pack 18912 for bulk asset migration for more information.

Create a Dynamic Media Configuration in Cloud Services

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:

1. In Experience Manager Author mode, select the Experience Manager logo to access the global navigation console and select the Tools icon, then go to Cloud Services > Dynamic Media Configuration.

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

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

   Select Connect to Dynamic Media.

   NOTE

   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 Dynamic Media Cloud Service is set up with the correct credentials.

4. 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:

     • Immediately means that when assets are uploaded, the system ingests the assets and provides the URL/Embed instantly. There is no user intervention necessary to publish assets.

     • Upon Activation means that you must explicitly publish the asset first before a URL/Embed link is provided.
       From Experience Manager 6.5.8 onwards, Experience Manager Publish instance reflects accurate Dynamic Media metadata values, such as dam:scene7Domain and dam:scene7FileStatus in Upon Activation publish mode only. To enable this functionality, install Service Pack 8, then restart Experience Manager. Go to the Sling Config Manager. Find the configuration for Scene7ActivationJobConsumer Component or create new one). Select the checkbox Replicate Metadata after Dynamic Media publishing, then select Save.

       

     • Selective Publish This option lets you control which folders are published in Dynamic Media. It lets you use features such as Smart Crop or dynamic renditions, or determine which folders are published exclusively in Experience Manager for previewing. Those same assets are not published in Dynamic Media for delivery in the public domain.
       You can set this option here in the Dynamic Media Cloud Configuration or, if you prefer, you can choose to set this option at the folder level, in a folder’s Properties.
       See Work with Selective Publish in Dynamic Media.
       If you later change this configuration, or you later change it at the folder level, those changes affect only new assets that you upload from that point forward. The publish state of existing assets in the folder remain as-is until you manually change them from either Quick Publish or the Manage Publication dialog box.

   • 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

     • Enabled 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 on 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

   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.

5. Select Save.

6. 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, navigate to 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, select Add.

   • To enable (turn on) the address, select the check box. Enter the IP address of the Experience Manager Author instance (not Dispatcher IP).

   • Select 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.

(Optional) Configure 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) Configure Dynamic Media - Scene7 mode for upload of assets larger than 2 GB

• (Optional) Setup and configuration of Dynamic Media - Scene7 mode settings

• (Optional) Tune the performance of Dynamic Media - Scene7 mode

• (Optional) Filter assets for replication

(Optional) Configure Dynamic Media - Scene7 mode for upload of assets larger than 2 GB

In Dynamic Media - Scene7 mode, the default asset upload file size is 2 GB or less. However, you can optionally configure upload of assets larger than 2 GB and up to 15 GB.

If you intend to use this feature, be aware of the following prerequisites and points:

• You must be running Experience Manager 6.5 with Service Pack 6.5.4.0 or later in Dynamic Media - Scene7 mode.

• This large upload feature is only supported for Managed Services customers.

• Be sure that your Experience Manager instance is configured with Amazon S3 or Microsoft® Azure Blob storage.

  NOTE

  Configure the Azure Blob storage with an access key and secret key because this large upload feature is not supported with AzureSas in the Blob storage configuration.

• Oak’s Direct Binary Access download is enabled (Oak’s Direct Binary Access upload is not required).

  To enable Direct Binary Access download, set property presignedHttpDownloadURIExpirySeconds > 0 in the datastore configuration. The value should be long enough to download larger binaries and possibly retry.

• Assets larger than 15 GB do not get uploaded. (The size limit is set in step 8 below.)

• When the Dynamic Media Reprocess assets workflow is triggered on a folder, it reprocesses any large assets that are already in sync with the Dynamic Media company. However, if any large assets are not yet synced in the folder, it does not upload the asset. Therefore, to sync existing large assets in Dynamic Media, you can run Dynamic Media Reprocess assets workflow on individual assets.

To configure Dynamic Media - Scene7 mode for upload of assets larger than 2 GB:

1. In Experience Manager, select the Experience Manager logo to access the global navigation console, then navigate to Tools > General > CRXDE Lite.

2. In CRXDE Lite window, do either one of the following:

   • In the left rail, navigate to the following path:

     /libs/dam/gui/content/assets/jcr:content/actions/secondary/create/items/fileupload

   • Copy and paste the path above into the CRXDE Lite path field below the toolbar, then press Enter.

3. In the left rail, right-click on fileupload, then from the pop-up menu, select Overlay Node.

   

4. On the Overlay Node dialog box, select the Match Node Types check box to enable (turn on) the option, then select OK.

   

5. From the CRXDE Lite window, do either one of the following:

   • In the left rail, navigate to the following overlay node path:

     /apps/dam/gui/content/assets/jcr:content/actions/secondary/create/items/fileupload

   • Copy and paste the path above into the CRXDE Lite path field below the toolbar, then press Enter.

6. In the Properties tab, under the Name column, locate sizeLimit.

7. To the right of the sizeLimit name, under the Value column, double-click the value field.

8. Enter the appropriate value in bytes so you can increase the size limit to the maximum desired upload size. For example, to increase the upload asset size limit to 10 GB, enter 10737418240 in the value field.
   You can enter a value up to 15 GB (2013265920 bytes). In this case, uploaded assets that are larger than 15 GB do not get uploaded.

   

9. Near the upper-left corner of the CRXDE Lite window, select Save All.

   Now set the timeout for the Adobe Granite Workflow External Process Job Handler by doing the following:

10. In Experience Manager, select the Experience Manager logo to access the global navigation console.

11. Do either one of the following:

    • Navigate to the following URL path:

      localhost:4502/system/console/configMgr/com.adobe.granite.workflow.core.job.ExternalProcessJobHandler

    • Copy and paste the path above into the URL field of your browser. Be sure you replace localhost:4502 with your own Experience Manager instance.

12. In the Adobe Granite Workflow External Process Job Handler dialog box, in the Max Timeout field, set the value to 18000 minutes (five hours). Default is 10800 minutes (three hours).

    

13. In the lower-right corner of the dialog box, select Save.

    Now set the timeout for the Scene7 Direct Binary Upload process step by doing the following:

14. In Experience Manager, select the Experience Manager logo to access the global navigation console.

15. Navigate to Tools > Workflow > Models.

16. On the Workflow Models page, select Dynamic Media Encode Video.

17. On the toolbar, select Edit.

18. On the workflow page, double-click the Scene7 Direct Binary Upload process step.

19. In the Step Properties dialog box, under the Common tab, under the Advanced Settings heading, in the Timeout field, enter a value of 18000 minutes (five hours). The default is 3600 minutes (one hour).

20. Select OK.

21. Select Sync.

22. Repeat steps 14-21 for the DAM Update Asset workflow model and the Dynamic Media Reprocess workflow model.

(Optional) Setup and configuration of Dynamic Media - Scene7 mode settings

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:

• Publish setup for Image Server
• Configure application general settings
• Configure color management
• Edit MIME types for supported formats
• Add MIME types for unsupported formats
• Create batch set presets to auto-generate Image Sets and Spin Sets

Publish setup for Image Server

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, navigate to 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.

• Request Attributes - These settings impose limits on images that can be delivered from the server.
• Default Request Attributes - These settings pertain to the default appearance of images.
• Common Thumbnail Attributes - These settings pertain to the default appearance of thumbnail images.
• Defaults for Catalog Fields- These settings pertain to the resolution and default thumbnail type of images.
• Color Management Attributes - These settings determine which ICC color profiles are used.
• Compatibility Attributes - This setting enables leading and trailing paragraphs in text layers to be treated as they were in version 3.6 for backwards compatibility.
• Localization Support - These settings let you manage multiple locale attributes. It also lets you specify a locale map string so you can define which languages you want to support for the various tooltips in Viewers. For more information about setting up [Localization Support], see Considerations when setting up localization of assets.

Configure application general settings

To open the Application General Settings page, in Dynamic Media Classic Global Navigation bar, navigate to 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).

• Overwrite in current folder, same base image name/extension - This option is the strictest rule for replacement. It requires that you upload the replacement image to the same folder as the original, and that the replacement image has the same filename extension as the original. If these requirements are not met, a duplicate is created.

• Overwrite in any folder, same base asset name/extension - Requires that the replacement image has the same filename extension as the original image (for example, chair.jpg must replace chair.jpg, not chair.tif). However, you can upload the replacement image to a different folder than the original. The updated image resides in the new folder; the file can no longer be found in its original location
• Overwrite in any folder, same base asset name regardless of extension - This option is the most inclusive replacement rule. You can upload a replacement image to a different folder than the original, upload a file with a different filename extension, and replace the original file. If the original file is in a different folder, the replacement image resides in the new folder to which it was uploaded.

Default Color Profiles - See Configure Color Management for additional information.

Configure 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 so color correction is enabled when images are requested:

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

2. Navigate 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 you want to change. For example, a property in the Color Management Attributes area.

   You can set the following color correction properties:

   • CMYK Default Color Space - Name of the default CMYK color profile
   • Gray-Scale 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

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 Imaging profiles can be used to define processing of videos and images, respectively.

See Uploading Assets.

To edit MIME types for supported formats:

1. In Experience Manager, select the Experience Manager logo to access the global navigation console, then navigate to Tools > General > CRXDE Lite.

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

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

   

3. Under the mimeTypes folder, select a mime type.

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

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

6. In the upper-left corner of the page, select CRXDE Lite to return to Experience Manager.

Adding MIME types for unsupported formats

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:

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

   

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

   

3. 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).

   

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

   

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

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

   

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

7. Return to the browser tab that has your open Experience Manager console.

8. From Experience Manager, navigate to Tools > General > CRXDE Lite.

   

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

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

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

    

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

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

    

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

Create batch set presets to auto-generate Image Sets and Spin Sets

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.

Configure 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:

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

2. On the navigation bar near the top of the page, navigate to Setup > Application Setup > Batch Set Presets > Default Naming.

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

   NOTE

   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.

4. Expand each element as necessary and enter the naming conventions you want to use.

5. As necessary, do any of the following:

   • Select Add to add another naming convention for an element.
   • Select Remove to delete a naming convention for an element.

6. Do one of the following:

   • Select Save As and type a name for the preset.
   • Select Save if you are editing an existing preset.

Create 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:

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

2. On the navigation bar near the top of the page, navigate to 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.

3. In the Preset List panel, select Add to activate the definition fields in the Details panel on the right-hand side of the screen.

4. In the Details panel, in the Preset Name field, type a name for the preset.

5. In the Batch Set Type drop-down menu, select a preset type.

6. 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, select 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, select Custom.

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

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

9. In the Details panel, select Save.

10. Select 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.

Create 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:

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

2. On the navigation bar near the top of the page, navigate to 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.

3. In the Preset List panel, select Add to activate the definition fields in the Details panel on the right-hand side of the screen.

4. In the Details panel, in the Preset Name field, type a name for the preset.

5. In the Batch Set Type drop-down menu, select Asset Set.

6. In the Sub Type drop-down list, select Multi-Axis Spin Set.

7. Expand Asset Naming Conventions, and then in the File Naming drop-down list, select Custom.

8. 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+

9. 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 demonstration purposes only. You can create your regular expression however you want to suit your needs.

   NOTE

   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.

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

11. In the Details panel, select Save.

12. Select 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.

(Optional) Tune the performance of Dynamic Media - Scene7 mode

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

• Updating the predefined Job parameters for processing of different file formats.
• Updating the predefined Granite workflow (video assets) queue worker threads.
• Updating the predefined Granite transient workflow (images and non-video assets) queue worker threads.
• Updating the maximum upload connections to the Dynamic Media Classic server.

Update the predefined Job parameters for processing of different file formats

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:

To update any of these parameters, follow the steps in Enabling MIME type-based Assets/Dynamic Media Classic upload job parameter support.

Update the Granite transient workflow queue

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:

1. Navigate to https://localhost:4502/system/console/configMgr and search for Queue: Granite Transient Workflow Queue.

   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.

   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.

1. Select Save.

Update the Granite workflow queue

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:

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

   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.

   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.

   

3. Select Save.

Update the Dynamic Media Classic upload connection

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

To update the Dynamic Media Classic upload connection:

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

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

   

3. Select Save.

(Optional) Filter assets for replication

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.

Use default asset filters for replication

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:

Customize asset filters for replication

1. In Experience Manager, select the Experience Manager logo to access the global navigation console and navigate to Tools > General > CRXDE Lite.

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

   

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.

   

   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.

   

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