Você está visualizando o conteúdo de ajuda da versão:

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

To use Scene7, you need to configure the cloud configuration so that Scene7 and AEM Assets can interact with one another. This document describes how to configure AEM and Scene7.

For information on using all the Scene7 components on a page and working with video, see Using Scene7. 

Observação:

AEM/Scene7 integration versus Dynamic Media

AEM users have a choice between two solutions to work with dynamic media: Either integrating their instance of AEM with Scene7 or using the Dynamic Media solution that is integrated into AEM.

Use the following criteria to determine which solution to choose:

  • If you are an existing Scene7 customer whose rich media assets reside in S7 for publishing and delivery, but you want to integrate those assets with Sites (WCM) authoring and/or AEM Assets  for management, then use the AEM/Scene7 point-to-point integration described in this document.
  • If you are a new AEM customer who has rich media delivery needs, select the Dynamic Media option. This option makes the most sense if you do not have an existing S7 account and many assets stored in that system.
  • In certain cases, you may want to use both solutions. The dual-use scenario describes that scenario. 

AEM/Scene7 point-to-point integration

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

  • Upload assets directly to Scene7 and then access via the Scene7 content browser for page authoring or
  • Upload to AEM Assets and then enable automatic publishing to S7; you access via Assets content browser for page authoring
The components you use for this integration are found in the Scene7 component area in Design mode.

AEM Dynamic Media

AEM Dynamic Media is the unification of S7 features directly within the AEM platform.

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

  1. Upload single image and video assets directly to AEM.
  2. Encode videos directly within AEM.
  3. Build image-based sets directly within AEM.
  4. If applicable, add interactivity to images or videos.

The components you use for Dynamic Media are found in the Dynamic Media component area in Design mode. They include the following:

  • Dynamic Media - The Dynamic Media component is smart - depending on whether you add an image or a video, you have various options. The component supports image presets, image-based viewers such as 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.
  • Interactive Media - The Interactive Media component is for those assets, such as carousel banners, interactive images, and interactive video, that have interactivity on them such hotspots or image maps. This component is smart - depending on whether you add an image or a video, you have various options. In addition, the viewer is responsive - the size of the screen changes automatically based on screen size. All viewers are HTML5 viewers.

Dual-Use Scenario

Out of the box, you can use both Dynamic Media and Scene7 integration features of AEM simultaneously. The Use cases table that follows describes when you turn certain areas on and off.

To use Dynamic Media and Scene7 simultaneously:

  1. Configure Scene7 in cloud services.

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

        Dynamic Media Scene7 Integration
    If you are ... Use Case 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 AEM and use AEM Dynamic Media component to author assets on Sites pages

    On

    (See step 3)

    On Off Off
    In retail and are new to Sites and Dynamic Media Upload NON-product assets to AEM for management and delivery. Upload PRODUCT assets to Scene7 and use Scene7 content browser in AEM and component to author Product Detail Pages on Sites.

    On

    (See step 3)

    On On Off
    New to Assets and Dynamic Media Upload assets to AEM Assets and use published URL/embed code from Dynamic Media

    On

    (See step 3)

    Off Off Off
    New to Dynamic Media and Templating Use Dynamic Media for imaging and video.  Author image templates in Scene7 and use Scene7 content finder to include templates in Sites pages.

    On

    (See step 3)

    On On Off
    An existing Scene7 customer and are new to Sites Upload assets to Scene7 and use AEM Scene7 content browser to search and author assets on Sites pages Off Off On Off
    An existing Scene7 customer and are new to Sites and Assets Upload assets to DAM and automatically publish to Scene7 for delivery.  Use AEM Scene7 content browser to search and author assets on Sites pages. Off Off On

    On

    (See step 4)

    Existing Scene7 customer and new to Assets

    Upload assets to AEM and use Dynamic Media to generate renditions for download/share. Automatically publish AEM assets to Scene7 for delivery.

    Important: Incurs duplicate processing and renditions generated in AEM will not be synchronized to Scene7

    On

    (See step 3)

    Off Off

    On

    (See step 4)

  3. Optional (please see use case table) - Set up the Dynamic Media cloud configuration and enable the Dynamic Media server.

  4. Optional (please see use case table) -- If you choose to enable Automatic Upload from Assets to Scene7, then you need to add the following:

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

Limitations

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

  • Manually uploading to Scene7 by selecting an asset and dragging it to a Scene7 component on an AEM page does not work.
  • Even though AEM-Scene7 synced assets are updated to Scene7 automatically when the asset is edited in Assets, a rollback action does not trigger a new upload, hence Scene7 would not get the latest version immediately after a rollback. The workaround is to edit again once rollback is complete.
  • If you need to use Dynamic Media for one use case and Scene7 integration for another use case, so that the Dynamic Media assets do not interact with the Scene7 system, then do not to apply the Scene7 configuration to the Dynamic Media folder, or the Dynamic Media configuration (processing profile) to a Scene7 folder.

Best Practices for Integrating Scene7 with AEM

When integrating Scene7 with AEM, there are some important best practices that need to be observed in the following areas:

  • Test-driving your integration
  • Uploading assets directly from Scene7 recommended for certain scenarios

In addition, please see known limitations.

Test-driving your integration

Adobe recommends that you test-drive your integration by having your root folder pointing to a subfolder only rather than an entire company. 

Cuidado:

Importing assets from an existing Scene7 company account may take a long time to show in AEM. Ensure that you designate a folder in Scene7 that does not have too many assets (for example, the root folder will often have too many assets and may crash your system).

Uploading assets from AEM Assets versus from Scene7

You can upload assets either by using the Assets (digital asset management) functionality or by accessing Scene7 directly in AEM via the S7 content browser. Which one you choose depends on the following factors:

  • S7 asset types that AEM Assets does not yet support have to be added to an AEM website from Scene7 directly, via the S7 content browser, for example, image templates.
  • For asset types that are supported by both AEM Assets and Scene7, deciding how to upload them depends on the following:
    • Where the assets are today AND
    • How important managing them in a common repository is 

If the assets are already in Scene7 and managing them in a common repository is not as important, then exporting them to AEM Assets only to sync them back to Scene7 for delivery would be an unnecessary roundtrip. Otherwise, keeping assets in a single repository and syncing to Scene7 only for delivery may be preferable.

Configuring Scene7 integration

You can configure AEM to upload assets to Scene7. Assets from a CQ target folder can be uploaded (automatically or manually) from AEM to a Scene7 company account.

Observação:

Adobe recommends that you use only the designated target folder for importing Scene7 assets. Digital assets that reside outside of the target folder can only be used in Scene7 components on pages where the Scene7 configuration has been enabled. In addition, they are placed in an ad hoc folder in Scene7. The adhoc folder is not synchronized with AEM (but assets are discoverable in the Scene7 content browser).

To configure Scene7 to integrate with AEM, you need to complete the following steps:

  1. Define a cloud configuration, which defines the mapping between a Scene7 folder and an Assets folder. You need to complete this step even if you only want one-way (AEM Assets to Scene7) synchronization.
  2. Enable the Adobe CQ s7dam Dam Listener in the OSGi console.
  3. If you want AEM assets to automatically upload to Scene7, you need to turn that option on and add Scene7 to the DAM update asset workflow. You can also manually upload assets.
  4. Adding Scene7 components to the sidekick. This allows the users to use Scene7 components on their AEM pages.
  5. Map the configuration to the page in AEM. This step is required to view any video presets that you have created in Scene7. It is also required if you need to perform a publish an asset from outside the CQ target folder to Scene7.

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

How synchronization between Scene7 and AEM Assets works

When setting up AEM Assets and Scene7 synchronization, it is important to understand the following:

Uploading to Scene7 from AEM Assets

  • There is a designated synchronization folder in AEM for Scene7 uploads. 
  • Uploads to Scene7 can be automated if the digital assets are placed in the designated synchronization folder.
  • The folder and subfolder structure in AEM is replicated in Scene7.

Observação:

AEM embeds all the metadata as XMP before uploading it to Scene7, so all properties on the metadata node are available in Scene7 as XMP.

Known limitations and design implications

With the synchronization between AEM Assets and Scene7, there are currently the following limitations/design implications:

Limitation/design implication Description
1 designated synchronization (target) folder You can only have one designated folder per company in AEM for Scene7 uploads. You can create multiple configurations if you need to have access to more than one company account in Scene7.
Folder structure If you delete a synced folder with assets, all Scene7 remote assets are deleted but the folder remains.
Ad-hoc folder Assets that reside outside the target folder that are manually uploaded to Scene7 in WCM are automatically placed in a separate ad-hoc folder on Scene7. You configure this in the cloud configuration in AEM.
Mixed media Mixed media sets appear in AEM although they are not supported in AEM.
PDFs Generated PDFs from eCatalogs in Scene7 will get imported into the CQ target folder.
UI refreshing When synchronizing between AEM and Scene7, be sure to refresh the user interface to view changes. 
Video thumbnails If uploading a video to AEM Assets for encoding via Scene7, the video thumbnails and encoded videos may take some time to be available in AEM Assets, depending on video processing time.
Target subfolders

If you are using subfolders within the target folder, ensure that you either use unique names for each asset (regardless of location) or you configure Scene7 (in the Setup area) to not overwrite assets regardless of location.

Otherwise, assets with the same name that are uploaded to a Scene7 target subfolder are uploaded, but the same-named asset in the target folder is deleted. 

Configuring Scene7 servers

If you run AEM behind a proxy or have special firewall settings, you may need to explicitly enable the hosts of the different regions. Servers are managed in content in /etc/cloudservices/scene7/endpoints and can be customized as required. Click a URL and then edit to change the URL, if necessary. In previous versions of AEM, these values were hard-coded.

If you navigate to /etc/cloudservices/scene7/endpoints.html, you see the servers listed (and can edit them by clicking on the URL):

chlimage_1

Creating a cloud configuration for Scene7

A cloud configuration defines the mapping between a Scene7 folder and an AEM Assets folder. It needs to be configured to synchronize AEM Assets with Scene7. See How Synchronization Works for more information.

Cuidado:

Importing assets from an existing Scene7 company account may take a long time to show in AEM. Ensure that you designate a folder in Scene7 that does not have too many assets (for example, the root folder will often have too many assets).

If you would like to test drive the integration, you may want to have the root folder point to a subfolder only, instead of the entire company.

Observação:

You can have multiple configurations: one cloud configuration represents one user at a Scene7 company. If you want to access other Scene7 companies or users, you need to create multiple configurations.

To configure AEM to be able to publish assets to Scene7, perform the following steps:

  1. Tap or click the AEM icon and navigate to DeploymentCloud Services to access Adobe Scene7.

  2. Click Configure Now.

    chlimage_1
  3. In the Title field, and optionally in the Name field, enter the appropriate information. Click Create.

    Observação:

    When creating additional configurations, the parent configuration field displays. 

    Do not change the parent configuration. Changing the parent configuration can break the integration.

  4. Enter the email address, password, and region of your Scene7 account and click Connect to Scene7. You are connected to the Scene7 server and the dialog expands with more options.

  5. Enter the Company name and Root Path (this is the published server name together with any path you want to specify; if you do not know the published server name, in Scene7, go to Setup, then Application Setup.)

    Observação:

    The Scene7 root path is the Scene7 folder AEM connects to. It can be narrowed down to a specific folder. 

    Cuidado:

    Depending on the size of the Scene7 folder, importing a root folder can take a long time. In addition, Scene7 data could exceed the AEM storage. Ensure you are importing the correct folder. Importing too much data can stop your system.

    chlimage_1
  6. Click OK. AEM saves your configuration.

Observação:

If you are reconnecting:

  • When reconnecting to Scene7 on publish, you may need to reset the password on publish or reconnecting will not work. This is not an issue on the author instance.
  • If you modify values such as your region, company name, you must reconnect to Scene7. If configuration options have been modified but not saved, AEM erroneously still indicates that the configuration is valid. Be sure to reconnect.

Enabling the Adobe CQ Scene7 Dam Listener

You must enable the Adobe CQ Scene7 Dam Listener, which is disabled by default.

To enable it:

  1. Tap or click the Tools icon, then navigate to Operations > Web Console. The Web console opens.

  2. Navigate to Adobe CQ Scene7 Dam Listener and select the Enabled check box. 

    chlimage_1
  3. Tap or click Save.

Adding configurable timeout to Scene7 Upload workflow

When an AEM instance is configured to handle video encoding through Dynamic Media Classic (Scene7), by default, there is a 35-minute timeout on any upload job. To accommodate potentailly longer-running video encoding jobs, you can configure this setting:

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

    chlimage_1
  2. Change the number as desired in the Active job timeout field. Any non-negative number is accepted with the unit of measure in seconds. By default, this is set to 2100.

    Observação:

    Best practice: Most assets are ingested within minutes at most (for example, images). But in certain instances - larger videos for example - the timeout value should be increased to 7200 seconds (2 hours) to accommodate long processing time. Otherwise, this Scene7 upload job is marked as UploadFailed in the JCR metadata.

  3. Tap or click Save.

Autouploading from AEM Assets

Beginning with AEM 6.3.2, AEM Assets is now configured for you so that any digital assets that you upload to the digital asset manager are automatically updated to Scene7 if the assets are in a CQ target folder.

When an asset is added into AEM Assets, it is automatically uploaded and published to Scene7.

Observação:

The maximum file size for automatic uploading from AEM Assets to Scene7 is 500 MB.

To configure autouploading from AEM Assets:

  1. Tap or click the AEM icon and navigate to Deployment > Cloud Services then, under the Dynamic Media heading, under Available Configurations, tap or click dms7 (Dynamic Media)

  2. Click the Advanced tab and select the Enable Automatic Upload check box and click OK. You now need to configure the DAM Asset workflow to include uploading to Scene7.

    Observação:

    See Configuring the state (published/unpublished) of assets pushed to Scene7 for information on pushing assets to Scene7 in an unpublished state.

    screen_shot_2018-03-15at52501pm
  3. Navigate back to the AEM welcome page and click Workflows. Double-click the DAM Update Asset workflow to open it.

  4. In the sidekick, navigate to the Workflow components, and select Scene7. Drag Scene7 to the workflow and click Save. Assets added to AEM Assets in the target folder will automatically be uploaded to Scene7.

    chlimage_1

    Observação:

    • When adding assets after automating, if they are not placed in the CQ target folder, they are not uploaded to Scene7.
    • AEM embeds all the metadata as XMP before uploading it to Scene7, so all properties on the metadata node are available in Scene7 as XMP.

Configuring the state (published/unpublished) of assets pushed to Scene7

If you are pushing assets from AEM Assets to Scene7, you can either publish them automatically (default behavior) or push them to Scene7 in an unpublished state.

You may not want to publish assets immediately on Scene7 if you want to test them in a staging environment before going live. You can use AEM with Scene7's Secure Test environment to push assets directly from Assets into Scene7 in an unpublished state.

S7 assets remain available via secure preview. Only when assets are published within AEM do the S7 assets also go live in production.

If you want to publish assets immediately when pushing them to Scene7, you do not need to configure any options. This is the default behavior.

However, if you do not want assets pushed to Scene7 to publish automatically, this section describes how to configure AEM and Scene7 to do this. 

Prerequisites to push assets to Scene7 unpublished

Before you can push assets to Scene7 without publishing them, you must set up the following:

  1. Contact Scene7 Customer Care (s7support@adobe.com) to enable secure preview for your Scene7 account. 
  2. Follow directions to setup secure preview for your Scene7 account.

These are the same steps you would follow to create any secure test setup in Scene7.

Observação:

If your installation environment is a Unix 64-bit operating system, see http://helpx.adobe.com/experience-manager/kb/enable-xmp-write-back-64-bit-redhat.html regarding additional configuration options you need to set.

Known Limitations for pushing assets in unpublished state

If you use this feature, please note the following limitations:

  • There is no support for version control.
  • If an asset is already published in AEM and a subsequent version is created, that new version will be immediately published live to production. Publish upon activation only works with the initial publish of an asset.

Observação:

If you want to publish assets instantly, best practice is to keep Enable Secure Preview set to Immediately and use the Enable Automatic Upload feature. 

Setting the state of assets pushed to Scene7 as unpublished

Observação:

If a user publishes the asset in AEM, it automatically triggers the S7 asset to the production/live asset (the asset will no longer be in secure preview/unpublished).

To set the state of assets pushed to Scene7 as unpublished:

  1. Tap or click the AEM icon and navigate to Deployment > Cloud Services, click Scene7, and select your configuration in Scene7.

  2. Click the Advanced tab. In the Enable Secure View drop-down menu, select Upon AEM Publish Activation to push assets to Scene7 without publishing. (By default, this value is set to Immediately, where Scene7 assets are published immediately.)

    See Scene7 documentation for more information on testing assets before making them public.

    chlimage_1
  3. Click OK.

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

You can check this by navigating to a Scene7 component on a page in AEM and clicking Edit. The asset will have the secure preview server listed in the URL. After publishing in AEM, the server domain in the file reference gets updated from the preview URL to the production URL.

Enabling Scene7 for WCM

Enabling Scene7 for WCM is required for two reasons:

  • To enable the drop-down list of universal video profiles for page authoring. Without this, the Universal Video Preset drop-down is empty and cannot be set.
  • If a digital asset is not in the target folder, you can upload the asset to Scene7 if you enable Scene7 for that page in the page properties and drag and drop the asset on a Scene7 component. Normal inheritance rules apply (meaning that child pages will inherit the configuration from the parent page).

When enabling Scene7 for the WCM, note that as with other configurations, inheritance rules apply. You can enable Scene7 for WCM in either the touch-optimized or classic user interface.

Enabling Scene7 for WCM in the Touch-Optimized User Interface

To enable Scene7 for WCM in the touch-optimized UI:

  1. Tap or click the AEM icon and navigate to Sites and then the root page of your web site (not language specific).

  2. In the toolbar, select the settings icon and tap or click Open Properties

  3. Tap or click Cloud Services and tap or click Add Configuration and select Scene7.

  4. In the Adobe Scene7 drop-down list, select the desired configuration and click OK.

    chlimage_1

    Video presets from that configuration of Scene7 are available for use in AEM with the Scene7 video component on that page and child pages.

Enabling Scene7 for WCM in the Classic User Interface

To enable Scene7 for WCM in the classic UI:

  1. In AEM, click Websites and navigate to the root page of your web site (not language specific).

  2. In the sidekick, click the Page icon and click Page Properties.

  3. Click Cloud Services and click Add services and select Scene7.

  4. In the Adobe Scene7 drop-down list, select the desired configuration and click OK.

    Video presets from that configuration of Scene7 are available for use in AEM with the Scene7 video component on that page and child pages.

Configuring a default configuration

If you have multiple Scene7 configurations, you can specify one of them as the default for the Scene7 content browser.

Only one Scene7 configuration can be marked as default at a given moment. The default configuration is the company assets that display by default in the Scene7 Content Browser.

To configure the default configuration:

  1. Tap or click the AEM icon and navigate to Deployment > Cloud Services, tap or click Scene7, and select your configuration in Scene7.

  2. Click Edit to open the configuration.

  3. In the General tab, select the Default Configuration check box to make this the default company and root path that appears in the Scene7 Content Browser.

    chlimage_1

    Observação:

    If there is only one configuration, selecting the Default Configuration check box has no effect.

Configuring the Ad-hoc folder

You can configure the folder that assets are uploaded to in Scene7 when the asset is not located in the CQ target folder. See Publishing assets from outside the CQ target folder.

To configure the adhoc folder:

  1. Tap or click the AEM icon and navigate to Deployment > Cloud Services, tap or click Scene7, and select your configuration in Scene7.

  2. Tap or click Edit to open the configuration.

  3. Tap or click the Advanced tab. In the Ad-hoc Folder field, you can modify the Ad-hoc folder. By default, it is the name_of_the_company/CQ5_adhoc.

    chlimage_1

Configuring universal presets

To configure Universal Presets for the video component, see Video.

Enabling MIME type-based Assets/Scene7 upload job parameter support

You can enable configurable Scene7 upload jobs parameters that are triggered by the synchronization of Digital Asset Manager/Scene7 assets.

Specifically, you configure the accepted file format by MIME type in the OSGi (Open Service Gateway initiative) area of the AEM Web Console Configuration panel. Then, you can customize the individual upload job parameters that are used for each MIME type in the JCR (Java Content Repository).

To enable MIME type-based assets:

  1. Tap or click the AEM icon and navigate to Tools > OperationsWeb Console.

  2. In the Adobe Experience Manager Web Console Configuration panel, on the OSGi menu, tap Configuration.

  3. Under the Name column, find and tap Adobe CQ Scene7 Asset MIME type Service to edit the configuration.

  4. In the Mime Type Mapping area, tap any plus sign (+) to add a MIME type.

    See Supported MIME types.

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

    For example, you would type a <file_extension>=<mime_type> as in EPS=application/postscript OR PSD=image/vnd.adobe.photoshop.

  6. In the lower-right corner of the configuration window, tap Save.

  7. Return to AEM and in the left rail, tap CRXDE Lite.

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

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

  10. Tap the mimeType that you just added.

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

  11. On the right side of the CRXDE Lite page, tap the Properties tab.

  12. Specify a Scene7 upload job parameter in the jobParam value field.

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

    See the Adobe Scene7 Image Production System API for additional upload job parameters you can use.

    Observação:

    If you are uploading PSD files, process them as templates with layer extractions. To do so, enter the following in the jobParam value field:

    process=MaintainLayers&createTemplate=true

    Be sure that your PSD file has “layers”. If it is strictly one image or an image with mask, it will only be processed as an image because there are no layers to process.

  13. In the upper-left corner of the CRXDE Lite page, tap Save All.

Troubleshooting Scene7 and AEM integration

If you are having trouble integrating AEM with Scene7, see the following scenarios for solutions.

If your digital asset publishing to Scene7 fails:

  • Check that the the asset you are trying to upload is in the CQ target folder (you specify this folder in the Scene7 cloud configuration). 
  • If it is not, you need to configure the cloud configuration in Page Properties for that page to allow uploading to the CQ adhoc folder.
  • Check the logs for any information.

If your video presets do not appear:

  • Ensure that you have configured the cloud configuration of that page through Page Properties. Video presets are avaialble in the Scene7 video component.

If your video assets do not play in AEM:

If new or modified assets in AEM do not automatically upload to Scene7:

  • Ensure that the assets are in the CQ target folder. Only assets that are in the CQ target folder are automatically updated (provided you configured AEM Assets to automatically upload assets).
  • Ensure that you have configured the Cloud Services configuration to Enable Automatic Uploading and that you have updated and saved the DAM Asset workflow to include Scene7 uploading.
  • When uploading an image into a subfolder of the Scene7 target folder, ensure you do one of the following:
    • Make sure that the names of all assets regardless of location are unique. Otherwise the asset in the main target folder is deleted and only the asset in the subfolder remains.
    • Change how Scene7 overwrites assets in the Setup area of the Scene7 account. Do not set Scene7 to overwrite assets regardless of location if you use assets with the same name in subfolders.

If your deleted assets or folders are not synchronized between Scene7 and AEM:

  • Assets and folders deleted in AEM Assets still show up in the synchronized folder in Scene7. You must delete them manually.

If video upload fails

Cuidado:

Importing assets from an existing Scene7 company account may take a long time to show in AEM. Ensure that you designate a folder in Scene7 that does not have too many assets (for example, the root folder will often have too many assets).

If you would like to test drive the integration, you may want to have the root folder point to a subfolder only, instead of the entire company.

Esta obra está licenciada sob uma licença não adaptada da Creative Commons Attribution-Noncommercial-Share Alike 3.0  As publicações do Twitter™ e do Facebook não são cobertas pelos termos do Creative Commons.

Avisos legais   |   Política de privacidade online