Media Settings

From Znode Knowledge Base
Jump to: navigation, search
Submit a Support Ticket
DAM > Media Settings 

Main media manager panel Media Settings.png

When the user selects the other services option by clicking on the radio button

Media Setting 1.png

When the option selected by the user is the network drive. Here in the Hosted URL, the site domain hosted on IIS that will be used to fetch and display the images on webstore. The network drive path is the actual network drive path that is to be entered by the user.

Media Settings 2.png

Note: By default, Multifront's is initially configured for local file storage but supports Amazon S3 and Azure Storage Servers. Administrators may need to reconfigure Media Settings before migrating your media assets.

The Media Settings section of Multifront allows Administrators to manage the specific storage server configuration for their media assets. After a storage server has been configured, new media asset data will be saved to the location specified. In this section, Administrators can choose to use a Local, Amazon S3, or Azure servers.

Media Setting Details

Detail Description
Select Server Select between "Local Server" or "Other Server" radial buttons. For, Azure or Amazon S3, use "Other Server".
Media Server Path "Local Server" only. Specify the local server URL with domain and media folder path.

For example, "http://api.localhost.com/Data/Media/"

Storage Server "Other Server" only. Select "Amazon S3" or "Azure" from a drop-down.
Access Key Generated from your Amazon S3 or Azure account
Secret Key Generated from your Amazon S3 or Azure account
Amazon Bucket Name Generated from your Amazon S3 account
Azure Bucket Name Generated from your Azure account


Configure Local Storage Server

Note: After changing the Storage Server, Administrators will need to republish any Catalog or Stores affected.

  1. Select "Local Server" radial button
  2. Enter detail for the Local Media Server Path - example "http://api.znodellc.com/Data/Media/" Media will be stored under the data folder of the API site.
  3. Save progress via the "Save" button. The page will reload will action confirmation.
  4. Storage Server is now configured


Configure Azure Storage Server

Media can also be stored using Azure servers after an Azure account has been created. Azure servers require special Access Keys, Secret Keys, and Bucket Name via your Azure account.

Note: After changing the Storage Server, Administrators will need to republish any Catalog or Stores affected.

  1. Select "Other Server" radial button
  2. Select Storage Server Type via a drop-down list
  3. Enter Azure Access Key, which corresponds to the Azure "Storage Account Name" detail on "Storage" tab, via "Manage Access Key"
  4. Enter Azure Secret Key, which corresponds to the Azure "Primary Access Key" detail on "Storage" tab, via "Manage Access Key"
  5. Enter Azure Bucket Name, which corresponds to the detail for "Container Name" in Azure, found by "Create New Container" via "Manage Access Key" link on the "Container" tab
  6. Save progress via the "Save" button. The page will reload will action confirmation.
  7. Storage Server is now configured

Configure Amazon S3 Storage Server

Media can also be stored using Amazon S3 servers after an Amazon S3 account has been created. Amazon servers require special Access Keys, Secret Keys, and Bucket Name via your Amazon/Azure account. Help Walk-Through]]

Note: After changing the Storage Server, Administrators will need to republish any Catalog or Stores affected.

  1. Select "Other Server" radial button
  2. Select Storage Server Type via a drop-down list
  3. Enter the Amazon Access Key, which corresponds to Amazon's Access Key ID detail.
  4. Enter the Amazon Secret Key, which corresponds to Amazon's Secret Access Key detail.
  5. Enter the Amazon Bucket Name, which corresponds to Amazon's Bucket Name detail.
  6. Save progress via the "Save" button. The page will reload will action confirmation.
  7. Storage Server is now configured

Related Links