Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


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

Info
titleInfo

This process must be repeated every time the Media Manager is updated.


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.


Note
titleNote
As this tool makes changes to the DAM database, remember to back up the database for the DAM Center before proceeding.


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


Info
titleInfo

All the fields in the configuration file are required.


The following is an example of a valid configuration:


Code Block
languagexml
<?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="CD7179C07E78E552-260DB052-4E8C43BE-95588D0E-3540040749CEDA7357C1BACC"/>
    <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:


DA7357C1BACCD
Parameter nameDescription
db

The database connection string. Must include the SQL server IP/Hostname, database name for the DAM Center, and the credentials of a SQL Server user with the rights to edit the given database.

Most of it can be found in the table named Install_config_actualsiteid under dbConnectionString. By going this way, you have to change the "master" in the string to be the name of your database (e.g. psi_dam)

runGenerateSearchForAllDetermines whether all Solr searches should be repopuplated after the install/update. Default: true
apiUrlThe URL to the DAM Center external API. Usually this would be the base URL of the DAM Center, with /dmm3bwsv3/ added to the end.
apiUsernameThe system user. Default: System
apiPasswordMD5 hash of the password for the user set in apiUsername.
versionGuid

The desired GUID for the Media Manager configuration. If there is no Media Manager installed on the DAM Center, this field can be any valid GUID. Otherwise, the field must use the Media Manager version GUID from the DAM Center. Where do I find this GUID?

Unless being told explicitly that you should use another GUID, then use the Default: 7E78E552-B052-43BE-8D0E-

DA7357C1BACC

usingEmbeddedScriptsDetermines whether the executable uses the default embedded SQL scripts for the install, or if it looks for SQL scripts in the installer folder.Default: true
timeoutInSecondsMaximum time to wait before timing out any request. If using runGenerateSearchForAll, the advised value is 1800. Default: 1800
AvailabilityGuid of metadatafield that controls publishing. Default: 74A5A102-A310-4BB7-9E84-0B14C36436B2


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


Note
titleNote

There is a small possibility of the installer crashing due to a rare deadlock issue. If this happens, simply run the application one more time.


2.3 Media Manager website configuration

Note
titleNote

This section is for the general configuration of the Media Manager web.config file. For specific configurations (e.g. ADFS), see the relevant configuration guide.

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.

Code Block
languagexml
<!-- ... -->
	<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.

PlaceholderDescription
LOGPATHThe absolute file path to the folder where all the Media Manager log files will be stored. Default: C:\LogFiles\MediaManager
ASSETSTREAMThe username for the assetstream user. Default: assetstream
ASSETSTREAM_PASSThe password for the assetstream user.
ASSETSTREAM_DOMAINThe domain of the assetstream user.
SYSPASSWORDMD5 hash of the System user in the DAM Center. This hash can only be retrieved via the DAM Center database. This can be found in the member table of the database.
DAMCENTER_URLThe URL to the DAM Center. This includes the https:// prefix. Example: https://dam.company.net
ConnectRestReturnAccesskeySecure that the value is set to "true", else you migth risk customers getting an asset download error from MM.
CONFIG_VERSIONThe version ID of the Media Manager ConfigManager version to use. Default: /5/

2.4 Google Analytics setup

Info
titleOptional

This step is optional.

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.

Table of Contents

Table of Contents