Aem Rest Disable Workflows for Asset Uploading

championship	description	contentOwner	products	topic-tags	content-type	exl-id
Integrate Adobe Feel Manager with Dynamic Media Classic	Learn how to integrate Adobe Feel Manager with Dynamic Media Archetype.	Rick Brough	SG_EXPERIENCEMANAGER/half dozen.5/SITES	integration	reference	f244cfb5-5550-4f20-92f0-bb296e2bf76e

Integrate Adobe Experience Manager with Dynamic Media Classic {#integrating-with-dynamic-media-archetype-scene}

Adobe Dynamic Media Classic is a hosted solution for managing, enhancing, publishing, and delivering rich media assets to Web, mobile, email, and Internet-connected displays and print.

To apply Dynamic Media Classic, you lot must configure the cloud configuration so that Dynamic Media Classic and Adobe Feel Managing director Assets tin interact with one another. This document describes how to configure Experience Manager and Dynamic Media Archetype.

For information on using all the Dynamic Media Classic components on a page and working with video, see Use Dynamic Media Classic.

[!Note]

• Dynamic Media Archetype's DHTML viewer platform officially reached end-of-life on January 31, 2014. For more information, see the DHTML viewer end-of-life FAQ.
• Before configuring Dynamic Media Archetype to work with Feel Director, come across All-time Practices for integrating Dynamic Media Classic with Experience Manager.
• If y'all use Dynamic Media Classic with a custom proxy configuration, you must configure both HTTP Client proxy configurations because some functionalities of Experience Manager utilize the 3.10 APIs and others utilize the four.x APIs. 3.x is configured with http://localhost:4502/system/console/configMgr/com.day.commons.httpclient and 4.x is configured with http://localhost:4502/system/console/configMgr/org.apache.http.proxyconfigurator.

Feel Manager/Dynamic Media Classic integration versus Dynamic Media {#aem-scene-integration-versus-dynamic-media}

Experience Manager users accept a choice between two solutions to piece of work with Dynamic Media. You can use one of the following:

• Integrate your instance of Experience Manager with Dynamic Media Classic.
• Use Dynamic Media that is integrated into Experience Manager.

Apply the post-obit criteria to make up one's mind which solution to cull:

• Are you an existing Dynamic Media Classic customer whose assets reside in Dynamic Media Classic for publishing and delivery, but yous want to integrate those assets with Sites (WCM) authoring, or Experience Manager Assets, or both? If then, use the Experience Director/Dynamic Media Classic point-to-point integration described in this certificate.

• If yous are a new Experience Manager client who has rich media delivery needs, select the Dynamic Media option. This choice makes the most sense if you practice not have an existing S7 business relationship and many avails stored in that system.

• In sure cases, apply both solutions. The dual-use scenario describes that scenario.

Experience Managing director/Dynamic Media Classic point-to-bespeak integration {#aem-scene-point-to-indicate-integration}

When you lot work with assets in this solution, you practice one of the following:

• Upload assets straight to Dynamic Media Classic and and then access by way of the Dynamic Media Archetype content browser for page authoring or
• Upload to Experience Manager Assets and so enable automatic publishing to Dynamic Media Classic; y'all access via Assets content browser for folio authoring

The components you employ for this integration are found in the Dynamic Media Classic component area in Design way.

Experience Managing director Dynamic Media {#aem-dynamic-media}

Experience Manager Dynamic Media is the unification of Dynamic Media Classic features directly inside the Experience Director platform.

When you work with assets in this solution, you lot follow this workflow:

1. Upload single image and video assets direct to Experience Managing director.
2. Encode videos direct inside Experience Director.
3. Build paradigm-based sets directly inside Experience Manager.
4. If applicable, add interactivity to images or videos.

The components you use for Dynamic Media are institute in the [!UICONTROL Dynamic Media] component area in Pattern mode. They include the following:

• [!UICONTROL Dynamic Media] - The [!UICONTROL Dynamic Media] component is smart - depending on whether yous add an epitome or a video, you accept various options. The component supports image presets, image-based viewers such every bit image sets, spin sets, mixed media sets, and video. In addition, the viewer is responsive - the size of the screen changes automatically based on-screen size. All viewers are HTML5 viewers.

• [!UICONTROL Interactive Media] - The [!UICONTROL Interactive Media] component is for assets such every bit carousel banners, interactive images, and interactive video. Such assets accept interactivity in them such hotspots or image maps. This component is smart. That is, depending on whether you add an image or a video, you accept various options. In improver, the viewer is responsive - the size of the screen changes automatically based on-screen size. All viewers are HTML5 viewers.

Dual-Use Scenario {#dual-use-scenario}

Out of the box, you can utilize both Dynamic Media and Dynamic Media Classic integration features of Feel Director simultaneously. The following use cases tabular array describes when you turn certain areas on and off.

To use Dynamic Media and Dynamic Media Archetype simultaneously:

1. Configure Dynamic Media Archetype in Cloud Services.

2. Follow the specific instructions particular to your use case:

   		Dynamic Media		Dynamic Media Classic Integration
   If y'all are ...	Use Example Workflow	Imaging/Video	Dynamic Media Component	S7 Content Browser and Components	Automatic Upload from Assets to S7
   New to Sites and Dynamic Media	Upload assets to Experience Director and employ Experience Director Dynamic Media component to author assets on Sites pages	On (Meet stride iii)	On	Off	Off
   In retail, and new to Sites and Dynamic Media	Upload NON-product assets to Experience Manager for management and commitment. Upload Production assets to Dynamic Media Archetype and use Dynamic Media Classic content browser in Experience Manager and component to author Product Particular Pages on Sites.	On (Encounter step 3)	On	On	Off
   New to Assets and Dynamic Media	Upload assets to Experience Managing director Assets and use published URL/embed code from Dynamic Media	On (See pace 3)	Off	Off	Off
   New to Dynamic Media and Templating	Utilise Dynamic Media for imaging and video. Author epitome templates in Dynamic Media Classic and use Dynamic Media Archetype content finder to include templates in Sites pages.	On (See step 3)	On	On	Off
   An existing Dynamic Media Classic customer and are new to Sites	Upload assets to Dynamic Media Classic and apply Experience Manager Dynamic Media Classic content browser to search and author assets on Sites pages	Off	Off	On	Off
   An existing Dynamic Media Archetype client and are new to Sites and Assets	Upload assets to DAM and automatically publish to Dynamic Media Classic for delivery. Use Experience Manager Dynamic Media Classic content browser to search and author avails on Sites pages.	Off	Off	On	On (See pace 4)
   Existing Dynamic Media Classic customer and new to Assets	Upload assets to Experience Manager and use Dynamic Media to generate renditions for download/share. Automatically publish Feel Manager avails to Dynamic Media Classic for delivery. Important: Incurs indistinguishable processing and renditions generated in Experience Manager are not synchronized to Dynamic Media Archetype	On (See pace iii)	Off	Off	On (Meet pace iv)

3. (Optional; see utilize case table) - Ready the Dynamic Media cloud configuration and enable the Dynamic Media server.

4. (Optional; run across utilize case tabular array) - If yous cull to enable Automatic Upload from Assets to Dynamic Media Classic, then you must add together the post-obit:

   1. Fix up automatic upload to Dynamic Media Classic.
   2. Add together the Dynamic Media Classic upload step after all the Dynamic Media workflow steps at the stop of Dam Update Asset workflow ( https://<server>:<host>/cf#/etc/workflow/models/dam/update_asset.html)
   3. (Optional) Restrict Dynamic Media Classic asset upload by MIME type in https://<server>:<port>/organization/console/configMgr/com.day.cq.dam.scene7.impl.Scene7AssetMimeTypeServiceImpl. Asset MIME types not in this list are non uploaded to Dynamic Media Classic server.
   4. (Optional) Gear up up video in Dynamic Media Classic configuration. You can enable video encoding for either or both Dynamic Media and Dynamic Media Classic simultaneously. Dynamic renditions are used for preview and playback locally in Experience Manager instance, whereas Dynamic Media Archetype video renditions are generated and stored on Dynamic Media Classic servers. When setting upwardly video encoding services for both Dynamic Media and Dynamic Media Classic, apply a video processing profile to the Dynamic Media Archetype asset binder.
   5. (Optional) Configure Secure preview in Dynamic Media Classic.

Limitations {#limitations}

When you have both Dynamic Media Classic and Dynamic Media enabled, there are the following limitations:

• Manually uploading to Dynamic Media Classic past selecting an asset and dragging it to a Dynamic Media Classic component on an Feel Manager page does not work.
• Fifty-fifty though Experience Manager-Dynamic Media Classic synced assets are updated to Dynamic Media Archetype automatically when the asset is edited in Avails, a rollback action does not trigger a new upload. Every bit such, Dynamic Media Classic does not get the latest version immediately after a rollback. The workaround is to edit again after rollback is complete.
• Is information technology necessary for you to use Dynamic Media for one use instance and Dynamic Media Classic integration for another then that Dynamic Media assets exercise not collaborate with the Dynamic Media Classic organisation? If then, then practice not to use the Dynamic Media Archetype configuration to the Dynamic Media folder. And, practice not utilise the Dynamic Media configuration (processing profile) to a Dynamic Media Classic binder.

Best practices for integrating Dynamic Media Archetype with Experience Manager {#all-time-practices-for-integrating-scene-with-aem}

When integrating Dynamic Media Archetype with Experience Director, there are some important best practices that must exist observed in the following areas:

• Test-driving your integration
• Uploading assets directly from Dynamic Media Classic recommended for certain scenarios

See known limitations.

Test-bulldoze your integration {#exam-driving-your-integration}

Adobe recommends that you lot test-drive your integration past having your root binder pointing to a subfolder only rather than an unabridged company.

[!CAUTION]

Importing assets from an existing Dynamic Media Classic company account can take a long fourth dimension to show in Experience Manager. Ensure that y'all designate a binder in Dynamic Media Classic that does not have besides many avails (for case, the root folder often has too many assets and can crash your system).

Upload avails from Experience Manager Avails versus from Dynamic Media Classic {#uploading-assets-from-aem-avails-versus-from-scene}

You tin upload assets either by using the Avails (digital asset management) functionality or by accessing Dynamic Media Classic direct in Experience Manager by way of the Dynamic Media Archetype content browser. Which one y'all choose depends on the post-obit factors:

• Dynamic Media Classic asset types that Experience Manager Assets does not yet back up must be added to an Experience Manager website from Dynamic Media Classic directly, by fashion of the Dynamic Media Classic content browser. For example, image templates.

• For asset types that are supported by both Experience Managing director Assets and Dynamic Media Archetype, deciding how to upload them depends on the following:

  • Where the assets are today AND
  • How important managing them in a mutual repository is

Suppose that the assets are already in Dynamic Media Classic and managing them in a common repository is not important. If that is the case, then exporting the assets to Feel Manager Avails but to sync them back to Dynamic Media Archetype for delivery is an unnecessary roundtrip. Adobe recommends that yous keep assets in a unmarried repository and sync to Dynamic Media Classic for delivery but.

Configure Dynamic Media Classic integration {#configuring-scene-integration}

You tin configure Experience Managing director to upload assets to Dynamic Media Archetype. Avails from a CQ target binder can exist uploaded (automatically or manually) from Feel Manager to a Dynamic Media Archetype company account.

[!Note]

Adobe recommends that y'all apply merely the designated target folder for importing Dynamic Media Classic assets. Digital assets that reside outside of the target folder can but be used in Dynamic Media Classic components on pages where the Dynamic Media Archetype configuration has been enabled. In addition, they are placed in an on-demand folder in Dynamic Media Classic. The on-need folder is non synchronized with Experience Manager (but assets are discoverable in the Dynamic Media Classic content browser).

To configure Dynamic Media Classic to integrate with Feel Manager:

1. Ascertain a cloud configuration - Defines the mapping betwixt a Dynamic Media Classic folder and an Avails folder. Complete this pace even if yous only want i-mode (Experience Managing director Assets to Dynamic Media Classic) synchronization.
2. Enable the Adobe CQ s7dam Dam Listener - Done in the [!UICONTROL OSGi] panel.
3. If you want Experience Manager Avails to automatically upload to Dynamic Media Classic, yous must plow on that selection and add together Dynamic Media Classic to the [!UICONTROL DAM Update Asset] workflow. You can besides manually upload assets.
4. Adding Dynamic Media Classic components to the sidekick. This functionality lets users use Dynamic Media Archetype components on their Experience Director pages.
5. Map the configuration to the page in Experience Manager - This step is required to view whatsoever video presets that you lot have created in Dynamic Media Archetype. Information technology is besides required if you must perform a publish an asset from outside the CQ target folder to Dynamic Media Archetype.

This section covers how to perform all of these steps and lists important limitations.

How synchronization between Dynamic Media Classic and Experience Manager Assets works {#how-synchronization-between-scene-and-aem-assets-works}

When setting up Experience Manager Assets and Dynamic Media Classic synchronization, it is important to sympathize the following:

Upload to Dynamic Media Classic from Experience Manager Assets {#uploading-to-scene-from-aem-assets}

• At that place is a designated synchronization folder in Experience Manager for Dynamic Media Archetype uploads.
• Uploads to Dynamic Media Archetype can be automatic if the digital assets are placed in the designated synchronization binder.
• The binder and subfolder structure in Experience Managing director is replicated in Dynamic Media Classic.

[!NOTE]

Experience Director embeds all the metadata as XMP before uploading it to Dynamic Media Classic, and then all properties on the metadata node are bachelor in Dynamic Media Classic every bit XMP.

Known limitations and blueprint implications {#known-limitations-and-blueprint-implications}

With the synchronization between Experience Managing director Assets and Dynamic Media Classic, in that location are currently the post-obit limitations/blueprint implications:

Limitation/blueprint implication	Description
One designated synchronization (target) folder	You lot can only accept ane designated folder per visitor in Experience Manager for Dynamic Media Classic uploads. You can create multiple configurations if yous must have admission to more than one company account in Dynamic Media Classic.
Folder structure	If you delete a synced folder with avails, all Dynamic Media Archetype remote assets are deleted but the folder remains.
On-demand folder	Avails that reside outside the target folder that are manually uploaded to Dynamic Media Classic in WCM are automatically placed in a carve up on-need folder on Dynamic Media Classic. You configure this folder in the deject configuration in Experience Manager.
Mixed media	Mixed media sets appear in Experience Manager although they are not supported in Experience Manager.
PDFs	Generated PDFs from eCatalogs in Dynamic Media Classic become imported into the CQ target binder.
UI refreshing	When synchronizing between Experience Manager and Dynamic Media Classic, be sure to refresh the user interface to view changes.
Video thumbnails	If uploading a video to Feel Manager Assets for encoding via Dynamic Media Classic, the video thumbnails and encoded videos can take some fourth dimension to be available in Experience Manager Avails, depending on video processing time.
Target subfolders	If y'all utilize subfolders within the target folder, make sure you either use unique names for each asset (regardless of location). Also, make sure you configure Dynamic Media Classic (in the Setup area) to not overwrite assets, regardless of location. Otherwise, assets with the same name that are uploaded to a Dynamic Media Classic target subfolder are uploaded, simply the same-named asset in the target folder is deleted.

Configure Dynamic Media Classic servers {#configuring-scene-servers}

If yous run Experience Manager behind a proxy or have special firewall settings, you must explicitly enable the hosts of the different regions. Servers are managed in content in /etc/cloudservices/scene7/endpoints and tin be customized equally required. Select a URL and and then edit to change the URL, if necessary. In previous versions of Experience Manager, these values were hard-coded.

If you navigate to /etc/cloudservices/scene7/endpoints.html, you run into the servers listed (and tin edit them by tapping the URL):

Create a cloud configuration for Dynamic Media Classic {#creating-a-cloud-configuration-for-scene}

A cloud configuration defines the mapping between a Dynamic Media Classic folder and an Feel Manager Assets folder. Information technology must be configured to synchronize Experience Manager Avails with Dynamic Media Classic. Run into How Synchronization Works for more information.

[!Caution]

Importing assets from an existing Dynamic Media Classic visitor account tin take a long time to bear witness in Experience Manager. Ensure that you lot designate a folder in Dynamic Media Classic that does not have too many avails. For example, the root binder often has likewise many assets.

If you would like to test-bulldoze the integration, have the root folder indicate to a subfolder only, instead of the entire company.

[!NOTE]

You can have multiple configurations: one deject configuration represents ane user at a Dynamic Media Classic company. If you want to admission other Dynamic Media Classic companies or users, you must create multiple configurations.

To create a cloud configuration for Dynamic Media Classic:

1. Select the Experience Manager icon and navigate to [!UICONTROL Deployment] > [!UICONTROL Deject Services] so you can access Adobe Dynamic Media Classic.

2. Select [!UICONTROL Configure at present].

   

3. In the [!UICONTROL Title] field, and optionally in the [!UICONTROL Name] field, enter the advisable information. Select [!UICONTROL Create].

   [!Notation]

   When creating more configurations, the [!UICONTROL parent configuration] field displays.

   Practice not change the parent configuration. Changing the parent configuration tin break the integration.

4. Enter the email address, password, and region of your Dynamic Media Archetype account and select [!UICONTROL Connect to Dynamic Media Classic]. You lot are connected to the Dynamic Media Archetype server and the dialog expands with more options.

5. Enter the [!UICONTROL Company] proper noun and [!UICONTROL Root Path]. This data is the published server name together with any path you want to specify. If y'all do not know the published server name, in Dynamic Media Classic, go to [!UICONTROL Setup > Application Setup]).

   [!Annotation]

   The Dynamic Media Classic root path is the Dynamic Media Classic binder Feel Manager connects to. It can be narrowed downward to a specific binder.

   [!CAUTION]

   Depending on the size of the Dynamic Media Classic folder, importing a root binder tin can have a long fourth dimension. In add-on, Dynamic Media Classic data could exceed the Experience Manager storage. Ensure y'all are importing the correct folder. Importing too much information can cease your organization.

   

6. Select [!UICONTROL OK]. Experience Director saves your configuration.

[!NOTE]

If you lot are reconnecting:

• When reconnecting to Dynamic Media Classic on publish, reset the password on publish or reconnecting does not piece of work (not an issue on the Writer example).
• If you change values such every bit your region, company name, you lot must reconnect to Dynamic Media Classic. If configuration options accept been modified just non saved, Experience Managing director erroneously still indicates that the configuration is valid. Be certain to reconnect.

Enable the Adobe CQ Dynamic Media Classic Dam Listener {#enabling-the-adobe-cq-scene-dam-listener}

Enable the Adobe CQ Dynamic Media Classic Dam Listener, which is disabled by default.

To enable the Adobe CQ Dynamic Media Classic Dam Listener:

1. Select the [!UICONTROL Tools] icon, and so navigate to [!UICONTROL Operations] > [!UICONTROL Web Panel].

2. In the Web console, navigate to [!UICONTROL Adobe CQ Dynamic Media Classic Dam Listener] and select the [!UICONTROL Enabled] bank check box.

   

3. Select [!UICONTROL Save].

Add configurable timeout to Dynamic Media Classic Upload workflow {#adding-configurable-timeout-to-scene-upload-workflow}

When an Experience Managing director instance is configured to handle video encoding through Dynamic Media Classic, by default, there is a 35-infinitesimal timeout on any upload job. To accommodate potentially longer-running video encoding jobs, you lot can configure this setting.

1. Navigate to http://localhost:4502/system/console/configMgr/com.day.cq.dam.scene7.impl.Scene7UploadServiceImpl.

   

2. Change the number as desired in the [!UICONTROL Agile task timeout] field. Any non-negative number is accepted with the unit of measure out in seconds. Past default, this number is set to 2100.

   [!Note]

   Best practice: Nigh assets are ingested inside minutes at most (for case, images). But in certain instances - larger videos for example - increment the timeout value to 7200 seconds (two hours) to accommodate long processing time. Otherwise, this Dynamic Media Classic upload task is marked equally [!UICONTROL UploadFailed] in the JCR (Java™ Content Repository) metadata.

3. Select [!UICONTROL Save].

Autoupload from Feel Manager Avails {#autouploading-from-aem-avails}

Start with Feel Manager 6.3.2, Experience Manager Assets is configured and then that any uploaded digital avails are updated to Dynamic Media Archetype, if the assets are in a CQ target folder.

When an asset is added into Experience Manager Avails, information technology is automatically uploaded and published to Dynamic Media Classic.

[!NOTE]

The maximum file size for automated uploading from Experience Managing director Avails to Dynamic Media Classic is 500 MB.

To autoupload from Experience Manager Assets:

1. Select the Experience Manager icon and navigate to [!UICONTROL Deployment] > [!UICONTROL Cloud Services].

2. Nether the Dynamic Media heading, under Available Configurations, select [!UICONTROL dms7 (Dynamic Media]).

3. Select the [!UICONTROL Advanced] tab, select the [!UICONTROL Enable Automated Upload] check box, then select [!UICONTROL OK]. Y'all now must configure the DAM Asset workflow to include uploading to Dynamic Media Archetype.

   [!Notation]

   Meet Configuring the country (published/unpublished) of assets pushed to Dynamic Media Classic for information on pushing assets to Dynamic Media Classic in an unpublished state.

   

4. Navigate back to the Experience Manager welcome page and select [!UICONTROL Workflows]. Double-click the DAM Update Nugget workflow so information technology opens.

5. In the sidekick, navigate to the [!UICONTROL Workflow] components, and select [!UICONTROL Dynamic Media Classic]. Drag [!UICONTROL Dynamic Media Archetype] to the workflow and select [!UICONTROL Save]. Assets added to Experience Managing director Assets in the target folder are automatically uploaded to Dynamic Media Classic.

   

   [!Note]

   • When calculation assets after automating, if they are not placed in the CQ target folder, they are non uploaded to Dynamic Media Archetype.
   • Experience Managing director embeds all the metadata as XMP before uploading it to Dynamic Media Classic, so all properties on the metadata node are available in Dynamic Media Classic as XMP.

Configure the country (published/unpublished) of assets pushed to Dynamic Media Classic {#configuring-the-land-published-unpublished-of-assets-pushed-to-scene}

If you are pushing assets from Experience Manager Assets to Dynamic Media Classic, you lot can either publish them automatically (default behavior) or push them to Dynamic Media Archetype in an unpublished land.

Information technology is possible that you do non desire to publish assets immediately on Dynamic Media Classic if y'all desire to test them in a staging environment earlier going live. You tin can use Experience Manager with Dynamic Media Classic's Secure Test environment to push button avails directly from Assets into Dynamic Media Archetype in an unpublished country.

Dynamic Media Archetype avails remain available via secure preview. Only when assets are published within Experience Managing director exercise the Dynamic Media Classic assets too go live in production.

If you desire to publish avails immediately when pushing them to Dynamic Media Archetype, y'all practice not demand to configure whatever options. This functionality is the default behavior.

However, if you exercise non want avails pushed to Dynamic Media Classic to publish automatically, this section describes how to configure Feel Manager and Dynamic Media Archetype to do perform this functionality.

Prerequisites to button assets to Dynamic Media Classic unpublished {#prerequisites-to-button-assets-to-scene-unpublished}

Before you tin can push button assets to Dynamic Media Classic without publishing them, yous must set up up the following:

1. Employ the Admin Console to create a support case. In your support case, request the enabling of secure preview for your Dynamic Media Classic account.
2. Set secure preview for your Dynamic Media Classic account.

These steps are the same ones you would follow to create whatever secure exam setup in Dynamic Media Classic.

[!NOTE]

If your installation environs is a UNIX® 64-bit operating system, see https://helpx.adobe.com/experience-director/kb/enable-xmp-write-back-64-bit-redhat.html regarding other configuration options you must set.

Known limitations for pushing assets in unpublished state {#known-limitations-for-pushing-assets-in-unpublished-country}

If you use this characteristic, annotation the following limitations:

• In that location is no support for version control.
• If an nugget is already published in Feel Manager and a subsequent version is created, that new version is immediately published live to production. Publish upon activation but works with the initial publish of an nugget.

[!NOTE]

If you want to publish assets instantly, best practice is to continue [!UICONTROL Enable Secure Preview] set to [!UICONTROL Immediately] and utilize the [!UICONTROL Enable Automatic Upload] feature.

Set the state of assets pushed to Dynamic Media Classic as unpublished {#setting-the-state-of-avails-pushed-to-scene-equally-unpublished}

[!NOTE]

If a user publishes the asset in Feel Manager, it automatically triggers the S7 asset to the production/live nugget (the asset is no longer in secure preview/unpublished).

To set up the state of assets pushed to Dynamic Media Classic as unpublished:

1. Select the Feel Managing director icon and navigate to [!UICONTROL Deployment] > [!UICONTROL Cloud Services].

2. Select [!UICONTROL Dynamic Media Classic].

3. Select your configuration in Dynamic Media Classic.

4. Select the [!UICONTROL Advanced] tab.

5. In the [!UICONTROL Enable Secure View] drop-down menu, select [!UICONTROL Upon AEM Publish Activation] to push assets to Dynamic Media Archetype without publishing. (Past default, this value is fix to [!UICONTROL Immediately], where Dynamic Media Classic avails are published immediately.)

   Come across Dynamic Media Classic documentation for more information on testing assets before making them public.

   

6. Select [!UICONTROL OK].

Enabling Secure Preview means that your assets are pushed to the secure preview server unpublished.

To see if [!UICONTROL Secure Preview] is enabled, navigate to a Dynamic Media Archetype component on a page in Experience Director. Select [!UICONTROL Edit]. The nugget has the secure preview server listed in the URL. After publishing in Experience Managing director, the server domain in the file reference gets updated from the preview URL to the production URL.

Enable Dynamic Media Classic for WCM {#enabling-scene-for-wcm}

Enabling Dynamic Media Classic for WCM is required for two reasons:

• It enables the drop-downwards listing of universal video profiles for folio authoring. Without this list, the [!UICONTROL Universal Video Preset] drop-down is empty and cannot be gear up.
• If a digital nugget is not in the target folder, you can upload the nugget to Dynamic Media Classic if you enable Dynamic Media Classic for that page in the folio properties. Then drag and drop the asset on a Dynamic Media Archetype component. Normal inheritance rules apply (meaning that child pages inherit the configuration from the parent folio).

When enabling Dynamic Media Classic for the WCM, every bit with other configurations, inheritance rules apply. You can enable Dynamic Media Classic for WCM in either the affect-optimized or classic user interface.

Enable Dynamic Media Classic for WCM in the touch-optimized user interface {#enabling-scene-for-wcm-in-the-bear upon-optimized-user-interface}

1. Select the Experience Manager icon and navigate to [!UICONTROL Sites], then the root page of your web site (not language specific).

2. In the toolbar, select the [!UICONTROL settings] icon and select [!UICONTROL Open Properties].

3. Select [!UICONTROL Deject Services] and select [!UICONTROL Add Configuration] and select [!UICONTROL Dynamic Media Classic].

4. In the [!UICONTROL Adobe Dynamic Media Archetype] drop-down list, select the desired configuration and select [!UICONTROL OK].

   

   Video presets from that configuration of Dynamic Media Classic are bachelor for employ in Feel Director with the Dynamic Media Classic video component on that page and child pages.

Enable Dynamic Media Classic for WCM in the Archetype user interface {#enabling-scene-for-wcm-in-the-classic-user-interface}

1. In Experience Manager, select [!UICONTROL Websites] and navigate to the root folio of your web site (not language specific).

2. In the sidekick, select the [!UICONTROL Page] icon and select [!UICONTROL Page Properties].

3. Select [!UICONTROL Cloud Services] > [!UICONTROL Add services] > [!UICONTROL Dynamic Media Classic].

4. In the [!UICONTROL Adobe Dynamic Media Classic] drib-down listing, select the desired configuration and select [!UICONTROL OK].

   Video presets from that configuration of Dynamic Media Archetype are bachelor for employ in Feel Manager with the Dynamic Media Classic video component on that page and child pages.

Configure a default configuration {#configuring-a-default-configuration}

If you take multiple Dynamic Media Classic configurations, you can specify one of them as the default for the Dynamic Media Classic content browser.

Only one Dynamic Media Archetype configuration can be marked equally default at a given moment. The default configuration is the company assets that brandish by default in the Dynamic Media Classic Content Browser.

To configure a default configuration:

1. Select the Experience Manager icon and navigate to [!UICONTROL Deployment] > [!UICONTROL Cloud Services].

2. Select [!UICONTROL Dynamic Media Classic].

3. Select your configuration in Dynamic Media Classic.

4. To open the configuration, select [!UICONTROL Edit].

5. In the [!UICONTROL General] tab, select the [!UICONTROL Default Configuration] check box to brand it the default company and root path that appears in the Dynamic Media Classic content browser.

   

   [!NOTE]

   If in that location is merely one configuration, selecting the [!UICONTROL Default Configuration] check box has no outcome.

Configure the Advert-hoc folder {#configuring-the-ad-hoc-binder}

You lot tin configure the on-demand folder that assets are uploaded to in Dynamic Media Classic when the asset is not in the CQ target folder. Meet Publishing assets from outside the CQ target folder.

To configure the Advert-hoc folder:

1. Select the Feel Manager icon and navigate to [!UICONTROL Deployment] > [!UICONTROL Cloud Services].

2. Select [!UICONTROL Dynamic Media Classic].

3. Select your configuration in Dynamic Media Classic.

4. To open up the configuration, select [!UICONTROL Edit].

5. Select the [!UICONTROL Advanced] tab. In the [!UICONTROL Advert-hoc Binder] field, you lot tin modify the Advertizing-hoc folder. By default, it is the name_of_the_company/CQ5_adhoc.

   

Configure universal video presets {#configuring-universal-presets}

To configure universal video presets for the video component, run into Video.

Enable MIME blazon-based Assets/Dynamic Media Archetype upload chore parameter support {#enabling-mime-blazon-based-avails-scene-upload-job-parameter-support}

Y'all can enable configurable Dynamic Media Classic upload jobs parameters that are triggered past the synchronization of Digital Nugget Manager/Dynamic Media Classic assets.

Specifically, y'all configure the accepted file format past MIME type in the OSGi (Open Service Gateway initiative) area of the Experience Managing director Web Panel Configuration console. Then, you can customize the private upload job parameters that are used for each MIME type in the JCR (Coffee™ Content Repository).

To enable MIME type-based avails:

1. Select the Experience Manager icon and navigate to [!UICONTROL Tools] > [!UICONTROL Operations] > [!UICONTROL Web Console].

2. In the Adobe Experience Manager Spider web Console Configuration panel, on the [!UICONTROL OSGi] menu, select [!UICONTROL Configuration].

3. Under the Name column, find and select [!UICONTROL Adobe CQ Dynamic Media Classic Asset MIME type Service] to edit the configuration.

4. In the Mime Blazon Mapping area, select whatsoever plus sign (+) to add a MIME blazon.

   See Supported MIME types.

5. In the text field, blazon the new MIME type name.

   For case, yous would type a <file_extension>=<mime_type> equally in EPS=application/postscript OR PSD=image/vnd.adobe.photoshop.

6. In the lower-right corner of the configuration window, select [!UICONTROL Salvage].

7. Return to Experience Manager and in the left rail, select [!UICONTROL CRXDE Lite].

8. On the CRXDE Lite folio, in the left rail, navigate to /etc/cloudservices/scene7/<surroundings> (substitute <environment> for the actual name).

9. Expand <environment> (substitute <environment> for the actual name) to reveal the mimeTypes node.

10. Select the mimeType that you lot just added.

    For example, mimeTypes > application_postscript OR mimeTypes > image_vnd.adobe.photoshop.

11. On the right side of the CRXDE Lite page, select the [!UICONTROL Properties] tab.

12. Specify a Dynamic Media Classic upload job parameter in the [!UICONTROL jobParam] value field.

    For example, psprocess="rasterize"&psresolution=120 .

    See the Adobe Dynamic Media Classic Epitome Production Organisation API for more upload job parameters you can use.

    [!Annotation]

    If y'all are uploading PSD files, and you desire to procedure them as templates with layer extractions, enter the following in the [!UICONTROL jobParam] value field:

    process=MaintainLayers&layerNaming=AppendName&createTemplate=true

    Be sure that your PSD file has "layers." If it is strictly one image or an image with mask, it is processed as an prototype because at that place are no layers to process.

13. In the upper-left corner of the CRXDE Light page, select [!UICONTROL Salvage All].

Troubleshoot Dynamic Media Archetype and Feel Manager integration {#troubleshooting-scene-and-aem-integration}

If you are having trouble integrating Experience Manager with Dynamic Media Classic, meet the following scenarios for solutions.

If your digital nugget publishing to Dynamic Media Classic fails:

• Check that the nugget you are uploading is in the [!UICONTROL CQ target] binder (you lot specify this folder in the Dynamic Media Archetype cloud configuration).

• If it is not, you must configure the cloud configuration in [!UICONTROL Page Properties] for that page to allow uploading to the [!UICONTROL CQ ad hoc] folder.

• Check the logs for any information.

If your video presets do not appear:

• Ensure that y'all have configured the deject configuration of that folio through [!UICONTROL Page Properties]. Video presets are bachelor in the Dynamic Media Classic video component.

If your video assets practice non play in Experience Manager:

• Ensure that you lot used the right video component. Dynamic Media Archetype video component is dissimilar from the foundation Video component. See Foundation Video Component versus Dynamic Media Classic Video Component.

If new or modified assets in Experience Manager practice not automatically upload to Dynamic Media Archetype:

• Ensure that the assets are in the CQ target binder. Only avails that are in the CQ target binder are automatically updated (provided you lot configured Experience Managing director Assets to automatically upload assets).

• Ensure that y'all have configured the Cloud Services configuration to Enable Automatic Uploading and that you take updated and saved the DAM Nugget workflow to include Dynamic Media Classic uploading.

• When uploading an image into a subfolder of the Dynamic Media Archetype target folder, ensure you do one of the following:

  • Brand certain that the names of all avails regardless of location are unique. Otherwise the asset in the main target binder is deleted and only the nugget in the subfolder remains.
  • Change how Dynamic Media Classic overwrites assets in the Setup surface area of the Dynamic Media Classic account. Exercise not set Dynamic Media Classic to overwrite avails regardless of location if you lot use avails with the same name in subfolders.

If your deleted assets or folders are not synchronized betwixt Dynamic Media Classic and Feel Director:

• Assets and folders deleted in Experience Manager Assets still show upwards in the synchronized folder in Dynamic Media Classic. Delete them manually.

If your video upload fails:

• If your video upload fails and you are using Experience Manager to encode video through the Dynamic Media Classic integration, come across Add configurable timeout to Dynamic Media Archetype Upload workflow.

[!Circumspection]

Importing avails from an existing Dynamic Media Classic company account tin take a long time to show in Feel Managing director. Ensure that you designate a folder in Dynamic Media Classic that does not have also many assets. For case, the root binder often has too many assets.

If you would like to test the integration, accept the root folder indicate to a subfolder merely, instead of the entire visitor.

thompsonkinters.blogspot.com

Source: https://github.com/AdobeDocs/experience-manager-65.en/blob/main/help/sites-administering/scene7.md

Share this post