Invalidate the CDN cache by way of Dynamic Media Classic invalidating-your-cdn-cached-content

Dynamic Media assets are cached by the CDN (Content Delivery Network) for fast delivery. However, when you make updates to an asset, you want those changes to take effect immediately. Invalidating your CDN cached content lets you quickly update assets that are delivered by Dynamic Media, instead of waiting for the cache to expire.

This feature requires that you use the out-of-the-box CDN that is bundled with Adobe Experience Manager Dynamic Media. Any other custom CDN is not supported with this feature.
These steps apply only to Dynamic Media in Adobe Experience Manager 6.5, Service Pack 5 or earlier.

To invalidate your CDN cache by way of Dynamic Media Classic:

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

  2. Go to Setup > Application Setup > General Settings.

  3. On the Application General Settings page, under the Servers group heading, locate the CDN Invalidation Template text box.

  4. Specify the template that is used for invalidating the CDN (Content Delivery Network) cache.

    For example, suppose you enter an image URL (including image presets or modifiers) referencing <ID>, instead of a specific image ID as in the following example:<ID>?$product$

    If the Template just contains <ID>, then Dynamic Media fills in https://<server>/is/image where <server> is the Publish Server Name that is defined in General Settings and <ID> is the assets selected to be invalidated.

  5. In the lower-right corner of the page, select Close.

  6. In the Dynamic Media Classic (Scene7) UI, select one or more assets, then go to File > Invalidate CDN. You see a list of one or more URLs generated from the template you created and the assets you selected. It uses the server URL listed under “Published Server Name” under the Application General Settings.

    For example, with the CDN Invalidation Template set in the previous step, suppose you selected a single image asset image named Backpack_B. When you go to File > Invalidate CDN, it results in the following generated URL in the CDN Invalidation user interface:$product$

  7. In the URL list box, select Continue to clear the cache for each specific URL. You can edit a URL or you can add a URL by typing or pasting it into the URL list box; you do not need to set CDN Invalidate Template beforehand.

    After you select Continue, an indicator is displayed that gives you an estimate of how long it will take to clear the cache.

    If you selected multiple assets, then went to File > Invalidate CDN, each asset is referenced in the saved Template URL. Therefore, you can define a CDN Invalidate Template referencing each URL image preset that is referenced on your website such as product detail and search results. Then, when you select one or images for invalidation from cache, the URLs automatically populate the interface.

    note note
    When you select assets, and then go to File > Invalidate CDN, Dynamic Media uses an invalidate CDN template to automatically create URLs to invalidate from the CDN. If there is nothing in the CDN Invalidate Template text box, then you get a blank URL list. Caching at the CDN is not asset-based; it is URL-based. Therefore, it is necessary to be aware of the complete URLs that are on your website. After you determine those URLs, you can add them to the Invalidate CDN Template text box earlier in the steps. Then, you can select those assets, and invalidate the URLs in one step.
    Another option is to add complete URLs to the Invalidate CDN list. If you follow this approach, it is unnecessary to select assets in Dynamic Media Classic before going to the File > Invalidate CDN option.