2 Installation Process - MM v4.11.0

2.1 Prepare the website folder

Unzip the provided archive of Digizuite™ Media Manager and copy the content of the folder to the desired location where the front-end website should reside. In this document, we will refer to this folder as <WebsiteFolder>.

We recommend that you name the folder to match the prepared DNS record name, e.g. "mediamanager.mycompany.com".

2.2 Installation scripts

Before you can use the Media Manager, some installation scripts need to be applied to the DAM Center to accompany the installation. These can be found in the DigiZuite Media Manager DAM Center updates.zip archive. It includes a "MediaManager.DbUpgrade" executable that is an all-in-one installer for the DAM Center update. You must specify a variety of configuration parameters in the accompanying MediaManager.DbUpgrade.exe.config file before running the executable.

The configuration parameters are defined as XML keys. For all parameters aside from connectionString, the value property is the one containing the configurable value.

The following is an example of a valid configuration:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <connectionStrings>
    <add name="db" connectionString="Server=8.8.8.8;Database=company_dam;User Id=administrator;Password=evK3GFn9LQVpm;"/>
  </connectionStrings>
  <appSettings>
    <!-- JobService GenerateSearchForAll -->
    <add key="runGenerateSearchForAll" value="true"/>
    <add key="apiUrl" value="https://dam.company-site.net/dmm3bwsv3/"/>
    <add key="apiUsername" value="System"/>
    <add key="apiPassword" value="e6662662a3f90aa497566c9b4a32f2f7"/>

    <!-- Standard/Required -->
    <add key="versionGuid" value="7E78E552-B052-43BE-8D0E-DA7357C1BACC"/>
    <add key="availability" value="74A5A102-A310-4BB7-9E84-0B14C36436B2"/>
    <add key="usingEmbeddedScripts" value="true"/>
    <add key="timeoutInSeconds" value="1800"/>
  </appSettings>
</configuration>

To configure this file for whatever installation you have, you will need to get some information about the DAM Center, as well as make some decisions based on what kind of installation you want. Here is a description of all the configuration parameters:

Once the config file is set up correctly, the next step is to simply run the MediaManager.DbUpgrade.exe file.

2.3 Media Manager website configuration

Before the Media Manager can be used, it needs to have some base configuration set, such as what DAM Center it should use. This configuration can be found in the web.config file. This file can be found named web.config.new upon extraction, and must be renamed to web.config before it can be used. Once renamed, please use the following table to configure your Media Manager.

<!-- ... -->
	<digiConfig>
    <log name="Mediaportal" path="LOGPATH" filter="Warning"/>
	<!-- To disable unc access requirements, comment out the unc element and enable appsetting 'UseUploadProxy' -->
    <unc useNetUseApi="true" userName="ASSETSTREAM" password="ASSETSTREAM_PASS" domain="ASSETSTREAM_DOMAIN" shareDriveName=""/>
    <services userName="System" userType="BackEnd" password="SYSPASSWORD"/>
  </digiConfig>
  <appSettings>
    <add key="APIURL" value="DAMCENTER_URL/dmm3bwsv3" />
    <add key="ProxyApiUrl" value="dmm3bwsv3" />
    <add key="RestApiUrl" value="DAMCENTER_URL/api/v2/" />
	<!-- Set UseUploadProxy to 'true' to enable upload without UNC access -->
	<add key="UseUploadProxy" value="false" />
    <add key="Access-Control-Allow-Origin" value="*" />
    <add key="vs:EnableBrowserLink" value="false" />
    <add key="ConnectRestReturnAccesskey" value="false" />
    <add key="UseSessionAccess" value="true" />
    <add key="ConfigVersionId" value="CONFIG_VERSION" />
    <add key="SearchesUseVersionedAccesskey" value="DigiZuite_System_Configs" />
    <add key="ConfigSearchName" value="DigiZuite_System_Configs" />
    <add key="ConnectRestReturnAccesskey" value="True" />
    <add key="ResponseContentTypeAsJson" value="True" />
    <add key="labelFolderId" value="/50025/" />
    <add key="guestUsername" value="Guest" />
    <add key="guestPassword" value="0ea2f02d5f73c86c220ff08b23d1c3f1" />
<!-- ... -->

The table below contains a list of placeholders from the above web.config file section. The placeholders are simply a representation of where the data should be changed, and the description explains what it is and what is should be.

2.4 Enabling icons

In your Media Manager's website folder, there are two files, that like web.config, has the extension ".new".

If you wish to use these files as icons for your software, then you remove the ".new" from them.

Alternatively, you may create your own icons, and put them in the website folder. NB. they both need to be .PNG. .ICO will not work.

After having removed .new, you need to reload your Media Manager for the favicon to appear.

2.4 Google Analytics setup

To use Google Analytics, you need to download a cryptographic private key file from Google Analytics and save it in the App_Data folder of the Digizuite™ Media Manager website. By default, this file should be named privatekey.p12.

Also you need to copy Google Analytics ViewId and account email to the configuration.

2.5 Create a new IIS website

To add a new website on Windows Server 2012, open the Server Manager console and under the Tools drop-down menu select Internet Information Services (IIS) Manager.

Right click the webserver and select Add website.

Once you select Add website, a new window will show up.

• Site name - We recommend that you name the folder to match the prepared DNS record name.
• Physical path - Specify the website path <WebsiteFolder>.
• Host name - Specify the prepared DNS record name.

Note: Only edit the above sections.

2.6 Setup Application Pool

• Expand the server content from the IIS Manager window and Select the Application Pools menu.
• Locate the pool with the same name as your website and double click it.
• The Edit Application Pool window will pop-up. Confirm that the selected .Net CLR version is 4+.
• Close Edit Application Pool and open the Advanced Settings.
• Under Process Model change the Identity to LocalService.

2.7 Create bindings

• Bindings for both http and https should be configured.