Configure Dynamic Media Publish Setup for Image Server

Configuring Dynamic Media Publish Setup is available only if:

Dynamic Media Publish Setup is intended for use by experienced web site developers and programmers. Adobe Dynamic Media recommends that users who change these publish settings be familiar with Adobe Dynamic Media, HTTP protocol standards and conventions, and basic imaging technology.

The Dynamic Media Publish Setup page establishes default settings that determine how assets are delivered from Adobe Dynamic Media servers to web sites or applications. If no setting is specified, the Adobe Dynamic Media server delivers an asset according to a default setting that was configured on the Dynamic Media Publish Setup page.

See also Optional - Setup and configuration of Dynamic Media - Scene7 mode settings for more optional configuration tasks.

NOTE

Upgrading from Dynamic Media Classic to Dynamic Media on Adobe Experience Manager? The General Settings page and Publish Setup page in Dynamic Media are pre-populated with the values taken from your Dynamic Media Classic account. The exceptions are all the values that are listed under the Default upload options area of the General Settings page. Those values are already in Experience Manager. As such, any changes that you make under Default upload options, across any of the five tabs, by way of the Experience Manager user interface, are reflected in Dynamic Media, not in Dynamic Media Classic. All other settings and values in the General Settings page and the Publish Setup page are maintained between Dynamic Media Classic and Dynamic Media on Experience Manager.

To configure Dynamic Media Publish Setup Image Server:

  1. In Experience Manager Author mode, select the Experience Manager logo to access the global navigation console.

  2. In the left rail, select the Tools icon, then go to Assets > Dynamic Media Publish Setup.

  3. In the Image Server page, set your Image Server - publish context, and then use the five tabs to configure default publish settings.

    Dynamic Media Publish Setup page
    Dynamic Media Publish Setup page, with the Request Attributes tab selected.

  4. When you are finished, near the upper-right corner of the page, select Save.

Image Server

The Image Server page establishes default settings for delivering images from image servers. Settings are available in five categories

Publish Context Description
Image Serving Specifies the context for publish settings.
Test Image Serving Specifies the context for testing publish settings.
For new Dynamic Media accounts only, the default Client address field is set to 127.0.0.1 automatically.
See Test assets before making them public.

Security tab

Client address - Lets you specify one or more IP addresses or IP address ranges. When specified, requests to this image catalog that originates from a client at an unlisted IP address is rejected. This rule applies both to delivery of images and rendered images.

Security tab
Security tab showing IP “allow” field.

Catalog Management tab

Rule set definition file path - Specifies the file that contains the rule set definitions for the image catalog.

See also RuleSetFile parameter in the Dynamic Media Viewers Reference Guide.

NOTE

If your Dynamic Media Classic account already has a Rule set definition file path selected (as set under Setup > Application > Publish setup, under Catalog Management group), your Dynamic Media account on Experience Manager fetches the file from Dynamic Media Classic. The file is then stored and made available in this field, when you open the Dynamic Media Publish Setup page for the first time.

Request Attributes tab

These settings pertain to the default appearance of images.

Setting Description
Reply image size limit Required.
For new Dynamic Media accounts only, the default size limit is automatically set to Width: 3000 and Height: 3000 for both Image Serving and Test Image Serving.
Specifies the maximum reply image width and height that is returned to the client. The server returns an error if a request causes a reply image whose width, or height, or both, is larger than this setting.
See also MaxPix parameter in the Dynamic Media Viewers Reference Guide.
Request obfuscation mode Enable if you want base64 encoding applied to valid requests.
See also RequestObfuscation parameter in the Dynamic Media Viewers Reference Guide.
Request locking mode Enable if you want a simple hash lock included in requests.
See also RequestLock parameter in the Dynamic Media Viewers Reference Guide.
Default Request Attributes
Default image file suffix Required.
Default data file extension that is appended to the catalog Path and MaskPath field values if the path does not include a file suffix.
See also DefaultExt parameter in the Dynamic Media Viewers Reference Guide.
Default font face name Specifies which font is used if no font is provided by a text layer request. If specified, it must be a valid font name value in the font map of this image catalog or in the font map of the default catalog.
See also DefaultFont parameter in the Dynamic Media Viewers Reference Guide.
Default image Provides a default image to return in response to a request where the requested image is not found.
See also DefaultImage parameter in the Dynamic Media Viewers Reference Guide.
NOTE: If your Dynamic Media Classic account already has a Default image selected (as set under Setup > Application > Publish setup, under Default Request Attributes group), your Dynamic Media account on Experience Manager fetches the file from Dynamic Media Classic. The file is then stored and made available in this field when you open the Dynamic Media Publish Setup page for the first time.
Default image mode When the slider box is enabled (slider on the right), the Default image replaces each missing layer in the source image with the default image and returns the composite as usual. When the slider box is disabled (slider on the left), the default image replaces the entire composite image, even if the missing image is just one of several layers.
See also DefaultImageMode parameter in the Dynamic Media Viewers Reference Guide.
Default view size Required.
For new Dynamic Media accounts only, the default view size is automatically set to Width: 1280 and Height: 1280 for both Image Serving and Test Image Serving.
The server constrains reply images to be no larger than this width and height, if the request does not specify the view size explicitly using wid=, hei=, or scl=.
See also DefaultPix parameter in the Dynamic Media Viewers Reference Guide.
Default thumbnail size Required.
Used instead of attribute Default view size for thumbnail requests (req=tmb). The server constrains reply images to be no larger that this width and height, if a thumbnail request (req=tmb) does not specify the size explicitly using wid=, hei=, or scl=.
See also DefaultThumbPix parameter in the Dynamic Media Viewers Reference Guide.
Default background color Specifies the RGB value used to fill in any area of a reply image that does not contain actual image data.
See also BkgColor parameter in the Dynamic Media Viewers Reference Guide.
JPEG Encoding Attributes
Quality
Specifies the default attributes for JPEG reply images.
For new Dynamic Media accounts only, the Quality default value is automatically set to 80 for both Image Serving and Test Image Serving.
This field is defined in the range of 1 - 100.
See also JpegQuality parameter in the Dynamic Media Viewers Reference Guide.
Chromatically downsampling Enable or disable chromatically downsampling which is employed by JPEG encoders.
Default resampling mode Specifies the default resampling and interpolation attributes to use for scaling image data. Use when resMode is not specified in a request.
For new Dynamic Media accounts only, the default resampling mode is automatically set to Sharp2 for both Image Serving and Test Image Serving.
See also ResMode parameter in the Dynamic Media Viewers Reference Guide.

Common Thumbnail Attributes tab

These settings pertain to the default appearance and alignment of thumbnail images.

Setting Description
Default background color for thumbnail Specifies the RGB value used to fill the area of an output thumbnail image that does not contain actual image data. Used only for thumbnail requests (req=tmb) and when Default Thumbnail Type setting is set to Fit or Texture.
See also ThumbBkgColor parameter in the Dynamic Media Viewers Reference Guide.
Horizontal alignment Specifies the horizontal alignment of the thumbnail image in the reply image rectangle specified by wid= and hei= values.
Used only for thumbnail requests (req=tmb) and when Default Thumbnail Type setting is set to Fit.
There are three horizontal alignments to choose from: Center alignment, Left alignment, and Right alignment.
See also ThumbHorizAlign parameter in the Dynamic Media Viewers Reference Guide.
Vertical alignment Specifies the vertical alignment of the thumbnail image in the reply image rectangle specified by wid= and hei= values. Used only for thumbnail requests (req=tmb) and when Default Thumbnail Type setting is set to Fit.
There are three vertical alignments to choose from: Top alignment, Center alignment, and Bottom alignment.
See also ThumbVertAlign parameter in the Dynamic Media Viewers Reference Guide.
Default cache time to live Provides a default expiration interval in hours in case a particular catalog record does not contain a valid catalog Expiration value. Set to -1 to mark as never expire.
See also Expiration parameter in the Dynamic Media Viewers Reference Guide.
Default thumbnail type Provides a default for the thumbnail type in case a particular catalog record does not contain a valid catalog ThumbType value. Used only for thumbnail requests (req=tmb).
There are three thumbnail types to choose from: Crop, Fit, and Texture.
See also ThumbType parameter in the Dynamic Media Viewers Reference Guide.
Default thumbnail resolution Provides a default for the thumbnail object resolution in case a particular catalog record does not contain a valid catalog ThumbRes value. Used only for thumbnail requests (req=tmb) and when the Default thumbnail type setting is set to Texture.
See also ThumbRes parameter in the Dynamic Media Viewers Reference Guide.

Color Management Attributes tab

These settings determine which ICC color profiles are used for images.

Color Conversion Rendering Intent
A color conversion rendering intent permits overriding of the default rendering intent of the working profiles to determine how the source colors are adjusted. Used when:

  1. One of the default ICC profiles is the target color space of a color conversion.
  2. An output device (printer or monitor) is characterized by this profile.
  3. And, the specified rendering intent is valid for this profile.

Different rendering intents use different rules to determine how the source colors are adjusted.

See also IccRenderIntent parameter in the Dynamic Media Viewers Reference Guide.

NOTE

In general, it is best to use the default rendering intent for the selected color setting, which has been tested by Adobe to meet industry standards. For example, if you choose a color setting for North America or Europe, the default color conversion rendering intent is Relative Colorimetric. If you choose a color setting for Japan, the default color conversion rendering intent is Perceptual.

Setting Characteristics
CMYK default color space Specifies the name of the ICC color profile to use as a working profile for CMYK data. If None Specified is chosen, color management is disabled for this image catalog when CMYK source images are involved. All CMYK working spaces are device-dependent, meaning that they are based on actual ink and paper combinations. The CMYK working spaces Adobe supplies are based on standard commercial print conditions.
See also IccProfileCMYK parameter in the Dynamic Media Viewers Reference Guide.
Gray-Scale default color space Specifies the name of the ICC color profile to use as a working profile for gray-scale data. If None Specified is chosen, color management is disabled for this image catalog when gray-scale source images are involved.
See also IccProfileGray parameter in the Dynamic Media Viewers Reference Guide.
RGB default color space Specifies the name of the ICC color profile to use as a working profile for RGB data. If None Specified is chosen, color management is disabled for this image catalog when RGB sources images are involved. In general, it is best to choose Adobe RGB or sRGB, rather than the profile for a specific device (such as a monitor profile). sRGB is recommended when you prepare images for the web or mobile devices, because it defines the color space of the standard monitor used to view images on the web. sRGB is also a good choice when you work with images from consumer-level digital cameras, because most of these cameras use sRGB as their default color space.
See also IccProfileRBG parameter in the Dynamic Media Viewers Reference Guide.
Color conversion rendering intent Perceptual – Aims to preserve the visual relationship between colors so it’s perceived as natural to the human eye, even though the color values themselves may change. This intent is suitable for photographic images with lots of out-of-gamut colors. This setting is the standard rendering intent for the Japanese printing industry.
Relative Colorimetric - Compares the extreme highlight of the source color space to that of the destination color space and shifts all colors accordingly. Out-of-gamut colors are shifted to the closest reproducible color in the destination color space. Relative Colorimetric preserves more of the original colors in an image than Perceptual. This setting is the standard rendering intent for printing in North America and Europe.
Saturation – Tries to produce vivid colors in an image at the expense of color accuracy. This rendering intent is suitable for business graphics like graphs or charts, where bright saturated colors are more important than the exact relationship between colors.
Absolute Colorimetric – Leaves colors that fall inside the destination gamut unchanged. Out-of-gamut colors are clipped. No scaling of colors to destination white point is performed. This intent aims to maintain color accuracy at the expense of preserving relationships between colors and is suitable for proofing to simulate the output of a particular device. This intent is useful for previewing how paper color affects printed colors.

Test assets before making them public

Secure Testing helps you define a secure test environment and build a robust business-to-business solution, based on a configurable set of IP address and ranges. This functionality lets you match your Adobe Dynamic Media deployments with the architecture of your content management and business system.

With Secure Testing, you can preview the staging version of the website with unpublished content.

If desired, create a staging environment rather than making assets publicly available for the following reasons:

  • Preview websites before public launch (staging website).
  • Serve assets that require restricted access, such as eCatalogs that show prices in a B2B web application.
  • Use assets behind a firewall as part of product information management system, customer service application, training site, and so on.
NOTE

Secure Testing does not affect access to Adobe Dynamic Media Classic. Adobe Dynamic Media Classic security remains consistent and requires the usual credentials for access to Adobe Dynamic Media Classic and related web services.

How Secure Testing works

Most corporations run their Internet behind a firewall. Access to the Internet is possible through certain routes and typically through a limited range of public IP addresses.

From your corporate network, you can figure out your public IP address using websites like https://www.whatismyip.com or request this information from your corporate IT organization.

With Secure Testing, Adobe Dynamic Media establishes a dedicated Image Server for staging environments or internal applications. Any request to this server checks the origin IP address. If the incoming request is not within the approved list of IP addresses, a failure response is returned. The Adobe Dynamic Media Company Administrator configures the approved list of IP addresses for their company’s Secure Testing environment.

Because the location of the original request must be confirmed, the traffic of the Secure Testing service is not routed through a content distribution network like public Dynamic Media Image Server traffic. Requests to the Secure Testing service have a slightly higher latency compared to the public Dynamic Media Image Servers.

Unpublished assets are immediately available from the Secure Testing services, without the need to publish. In this way, you can run a preview before assets are published to their public facing image server.

NOTE

Secure Testing services use the Catalog Server that is configured with an internal publish context. Therefore, if your company is configured to publish to Secure Testing, any uploaded assets in Adobe Dynamic Media immediately become available on Secure Testing services. This functionality is true regardless of whether the assets are marked for publish on upload.

Secure Testing services currently support the following asset types and functionalities:

  • Images.
  • Vignettes (Render Server requests).
  • Render Server requests (supported, but must be requested explicitly by customer).
  • Sets, including image sets, eCatalog, render sets, and media sets.
  • Standard Adobe Dynamic Media rich media viewers.
  • Adobe Dynamic Media OnDemand JSP pages.
  • Static content, such as PDF files and progressively served videos.
  • HTTP video streaming.
  • Progressive video streaming.

The following asset types and functionalities are currently not supported:

  • Adobe Dynamic Media Classic Info or eCatalog search
  • RTMP video streaming
  • Web-to-print
  • UGC (User-Generated Content) services
IMPORTANT

Support for new or existing UGC vector image assets in Adobe Dynamic Media ended on September 30, 2021.

Test the Secure Testing service

To ensure that Secure Testing service works as expected, do the following:

Prepare your account

  1. Contact Adobe Customer Care and request that they enable Secure Testing on your account.

  2. In Adobe Experience Manager, select Tools > Assets > Dynamic Media Publish Setup.

  3. On the Image Server page, in the Publish Context drop-down list, select Test Image Serving.

  4. Select the Security tab.

  5. For the Client address filter, select Add.

  6. In the IP Address field, type an IP address.

  7. In the Mask field, type a net mask.

    NOTE

    If you add more than one IP address and net mask, it effectively permits all IP addresses to make asset calls, and they all show up.

  8. Do one of the following:

    • To add more IP addresses, repeat the previous three steps.
    • Continue to the next step.
  9. In the upper right corner of the Image Server page, select Save.

  10. Upload the desired images to your Adobe Dynamic Media account.

  1. Make sure some of the images are marked for publish and others are unmarked, and then submit the publish job.
  1. Determine the name of your Secure Testing service by going to Tools > Assets > Dynamic Media General Setting.
  2. On the Server page, find the server name to the right of Published Server Name.

Contact Adobe Care if the server name is missing or the URL to the server does not work.

Prepare website variations

You need two variations of a website that links the published and unpublished assets:

  • Public version - Link assets using your traditional Adobe Dynamic Media URL syntax.
  • Staging version - Link assets using the same syntax but with the Secure Testing site name.

Run the tests

Perform the following tests:

  1. Check whether assets are visible from within your corporate network.

    From within the corporate network identified by the previously defined IP address range, the staging version of the website displays all images, whether marked for publish or not. As such, you can test without accidentally making images available before preview approval or product launch.

    Confirm that the public version of your site shows published assets as previously experienced with Adobe Dynamic Media.

  2. From outside your corporate network, verify that nonpublished assets (that is, unmarked for publish) are protected from third-party access.

    Access your network from outside (such as from your home computer, or over a 4G/5G connection), then verify that the public version of the site shows all published assets but none of the unpublished content.

    Confirm that the staging version does not show any asset because you are accessing the Secure Testing service from an unapproved IP address.

On this page