Publish files publishing-files

You publish your assets to Dynamic Media Image Servers. You can publish assets on a one-time basis or arrange for Adobe Dynamic Media Classic to publish assets on a recurring schedule. After your assets are published, they are available to you for delivery. You can copy the URL calls from Adobe Dynamic Media Classic and add them to your website or application.

Adobe Dynamic Media Classic now supports the delivery of all images and video over HTTP/2. That is, a published URL or embed code for the image or video is available to be integrated with any application that accepts a hosted asset. That published asset is then delivered by way of HTTP/2 protocol. This method of delivery improves the way browsers and servers communicate, allowing for better response and load times of all your Adobe Dynamic Media Classic assets. See HTTP2 Delivery of Content FAQ.

Publish After Uploading publish-after-uploading

Assets either in a published or unpublished state. By default, any assets that you upload into Adobe Dynamic Media Classic are automatically marked for publishing.

For more information, see the Instant Publish Notice PDF.

Use these techniques to mark assets for publish:

Some “child” assets are automatically marked for publish when their parents are marked for publish. This table lists child assets that are marked for publish automatically.

Derived images are also automatically marked for publish when their parent images are being published. Derived images include images you adjusted with image-editing options. You can see these derived images in Detail View under Built & Derivatives.

Create a publish job creating-a-publish-job

Create a publish job to publish assets you have uploaded to Adobe Dynamic Media Classic servers but do not want to automatically publish them yet. You can perform a one-time publish job or schedule jobs to recur regularly. Adobe Dynamic Media Classic offers advanced publishing options for publishing to specific servers and options for republishing assets that have already been published.

To create a publish job:

Adobe Dynamic Media Classic tracks publish jobs on the Jobs page. You can review publish jobs on that page.

Create a one-time publish job creating-a-one-time-publish-job

Create a one-time publish job by selecting the One-Time option on the Publish page.

If you want the publish job to occur later, in the Publish page, select One-Time, then select Schedule For Later from the drop-down list. Use the Calendar and the Time slider to select a day and time to run the publish job.

Create a recurring publish job creating-a-recurring-publish-job

Create a recurring publish job by selecting Recurring on the Publish page.

Then choose a Repeat option of Daily, Weekly, Monthly, or Custom, then specify when you want the publishing job to recur. Adobe Dynamic Media Classic presents calendar tools for scheduling the recurring publish job. You can select Custom option and enter a rule in the Rule text field to describe a custom job interval.

See Create a custom upload or publish job time interval.

Advanced publish options advanced-publish-options

You can display the Advanced options on the Publish page and choose these options for handling a publish job:

HTTP Notification - Enter a URL to trigger subsequent publish jobs.

See Use an upload or publish job as a trigger.)

Cancel a publish job canceling-a-publish-job

You can cancel a publish job that is in progress. Moreover, if you are an administrator, you can cancel an in-progress publishing job from the company Jobs page.

To cancel a publishing job, go to the Jobs page and select Cancel. On the Scheduled tab of the Jobs page, you can pause or resume a job by deselecting or selecting the check box in the job’s Active column.

Manually publish assets manually-publishing-assets

You can publish individual assets manually instead of creating a publishing job. When you publish sets, such as an Image Set or an Adaptive Video Set, the set (or “parent”) and all members (or “children”) within that set get published.

Unpublished assets are indicated in the user interface by a gray, round icon with a slash through it (unpublished state), to the left of the asset’s name. After an asset is published, the icon turns green and has a white check mark in the center (published state).

To manually publish assets:

Manually unpublish assets manually-unpublishing-assets

You can unpublish individual assets manually. When you unpublish sets, such as a Swatch Set or an eCatalog, the set (or “parent”) itself goes into an unpublished state. However, the members (or “children”) within that set are not affected; instead, they each retain their existing published or unpublished state.

Published assets are indicated in the user interface by a round, green icon with a white check mark in the center (published state), to the left of the asset’s name. After an asset is unpublished, the icon turns gray with a slash through it (unpublished state),

To manually unpublish assets:

Get an asset’s publish history getting-an-asset-s-publish-history

The last date that an asset was published is shown in Detail View at the top of the panel. You can get more details about the publishing history by opening the History & Published Servers panel in Detail View. From there, you can see when the asset was published and to which servers it was published.

Republished assets and CDN delays republished-assets-and-cdn-delays

Adobe Dynamic Media Classic assets are distributed on the content delivery network (CDN). CDN is a system of computer servers networked together that cooperate transparently to deliver content, especially large media content, to end users. In the CDN system, web content is stored in web caches across the Internet (called the edge cache network). Web content is delivered from the web caches to end users to make for faster deliveries.

The first time someone downloads a web page, the assets are delivered to a CDN web cache server. They are stored on this server so that the next time someone in the same area accesses the web page, the same cached content can be delivered faster. The content is delivered faster because it is located closer to the end user. CDN makes for faster web page displays. It decreases bandwidth demands on the central server because content is delivered from the edge cache network, not from a central server in every instance.

Newly published Adobe Dynamic Media Classic content is available immediately to the end user and quickly populates the edge cache network. However, newly republished content—images that have the exact same names as images previously published to an image server—is not updated on CDN for up to ten hours. Instead, end users see what is in a web cache on the CDN network. For this reason, your Adobe Dynamic Media Classic republished assets do not appear to end users for ten hours.

If you want your newly republished image assets to be available sooner than the ten-hour delay, you can flush web caches on CDN. Flushing these web caches removes old content from CDN web caches and replaces it with your most recently published assets.

To flush the cache, on the Global Navigation bar, go to File > Invalidate CDN. All selected files are removed from the cache. If there are no publishable assets, or if you are not a company admin, the Remove from CDN option is not available.