1 Step 1: Database Backup
2 Step 2: Preparation
3 Step 3: Installation Scripts
- 3.1 Preparation of the configuration file
- 3.2 Running the installation script
4 Step 4: Creating a new Media Manager 5 version
5 Step 5: Website Configuration for Media Manager 5
6 Step 6: Creation of a New IIS Website
7 Step 7: Application Pool Setup
8 Step 8: Whitelist CORS for the MediaManager Application

Step 1: Database Backup

During the installation process there are changes applied to the DAM database. For this reason it is strongly recommended to back up the database for the DAM Center before proceding with running the instalaltion scripts in Step 3.

In order to back up the database you need to perform the following steps:

Open Microsoft SQL Server Management Studio.
Expand "Databases" menu.
Right-click the name of you the DAM Center that Media Manager 5 will be connected to.
Click "Tasks".
In the new menu click "Back Up...".
In the new window that pops up, choose "Add..."
Click "..." to access more options
Type the name of the back up file, adding ".bak" at the end.
Click "OK".
Confirm your selections by clicking "OK" in the two remaining windows.

Step 2: Preparation

To initialize the installation it is important to to do the following steps:

Copy the two provided archives into your server and unzip both of them into new folders:
1. You will work with the folder named "MediaManager.DbUpgrade.(version)" in Step 3.
2. You will work with the folder named "MediaManager.(version)" in Step 4.
Create a new folder with the name matching the DNS record for Media Manager 5 in the location that your IIS server has the access to. This location is usually the folder named "Webs" (usually C:/Webs is used, but it can also be located on a different drive).
Alternative method of finding the relevant "Webs" folder is by using Internet Information Services (IIS) Manager. In order to do that, you need to:
1. unfold the menu with the server name
2. unfold "Sites"
3. right click on the name of one of the existing Digizuite products, for example your DAM center
4. click "Explore"
The folder named "MediaManager.(version)" is your Digizuite™ Media Manager 5. After unpacking it, you need to place its contents into the folder created in the previous step.
Create a new folder with the same name as your DNS record in the folder "LogFiles". You will need to specify the path to the newly created folder in one of the following steps.

Step 3: Installation Scripts

Preparation of the configuration file

In the folder named "MediaManager.DbUpgrade" locate the configuration file named appsettings.json. Right-click it and select "Edit with Notepad++". This is what you will see:

{
    "Logging": {
        "LogLevel": {
            "Default": "Debug",
            "System": "Information",
            "Microsoft": "Information"
        }
    },
    "Upgrade": {
        "ConnectionString": "Server=172.18.3.32;Persist Security Info=False;MultipleActiveResultSets=False;Initial Catalog=mmdev_dam;User ID=admin_mmdev_dam;Password=admin_mmdev_dam",
        "RunGenerateSearchForAll": true,
        "ApiUrl": "https://dam.digizuite.com/dmm3bwsv3",
        "ApiUsername": "System",
        "ApiPassword": "a2ddc680310e876a61c5d4bd7e52663f",
        "VersionGuid": "0B59C5CF-E3A9-4043-AEDB-FCEAA4040D4C",
        "Availability": "74A5A102-A310-4BB7-9E84-0B14C36436B2",
        "Timeout": "00:30:00"
    }
}

It is good practice to completely remove the text between quotation marks before copy-pasting new information. This minimizes the chances of typing mistakes.

To configure this file for the installation you have, you will need to retrieve some information about the DAM Center, as well as make some decisions based on what kind of installation you want.

Here is the description of how you retrieve most of the information about the DAM Center:

Locate the folder containing your DAM Center in "Webs" and open it.
Find the file called web.config.
Open the file by right-clicking it and selecting "Edit with Notepad++"
Remember to not make any changes to this file.

Here is the description of all the configuration parameters:

Parameter name	Description

Parameter name	Description
ConnectionString	This is database connection string. It 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. This information can be found in the DAM Center's configuration file. You need to copy information from the field called "connectionString"
runGenerateSearchForAll	This determines, whether all Solr searches should be repopulated after the installation/update. Default: true
apiUrl	The URL to the DAM Center's external API. It is formed by the base URL of the DAM Center and ending "/dmm3bwsv3/". Remember to include the character "/" at the end! Example: https://demo3dc.digizuite.com/dmm3bwsv3/
apiUsername	This is the name of the system user. This information can be found in the DAM Center's configuration file. You need to copy information from the section "digiConfig". Default: System
apiPassword	This is the MD5 hash of the password for the user set in apiUsername. This information can be found in the DAM Center's configuration file. You need to copy information from the section "digiConfig".
versionGuid	This is the desired GUID for the Media Manager 5 configuration. If there is no Media Manager 5 installed on the DAM Center, this field can be any valid GUID. If Media Manager 5 is already installed and the update is performed, the field must use the Media Manager 5 version GUID from the DAM Center. The GUID you use, has to point at the root of the Media Manager configuration version. If Media Manager 4 is installed on the DAM Center, the version GUID for Media Manager 5 must be unique from it!
usingEmbeddedScripts	This determines, whether the executable uses the default embedded SQL scripts for the installation, or if it looks for SQL scripts in the installer folder. Default: true
timeoutInSeconds	This is the maximum time to wait before timing out any request. If runGenerateSearchForAll is used, it is recommended to set the value to 1800. Default: 1800
Availability	This is the Guid of metadata field that controls publishing. Default: 74A5A102-A310-4BB7-9E84-0B14C36436B2

Running the installation script

Once the config file is set up correctly, simple execute the db-upgrade.exe file, to have the upgrade happen.

Dependent on the size of you database, it might take anywhere from under 60 seconds to several minutes to for the installation process to finish.

Step 4: Creating a new Media Manager 5 version

The DAM Center enables the opportunity of creating multiple Media Manager versions with the help of the Config Manager. Usually, however, you will only have one version corresponding to your one Media Manager.

It is strongly recommended to create at least one version of Media Manager 5 (Default) at this stage of the installation process.

To create a new version, you'll have to access your DAM Center.

In your DAM Center, navigate to System tools → ConfigManager → Digizuite™ Media Manager 5 → 5.0.0 (Aka. "The root version").

While standing in the root of the Media Manager 5's Config Manager (i.e. "5.0.0"), look to the upper right corner where a button says "Create new version".

To the left of the button, there is a text field. In this, type the title of the version. If you only plan to have one version only, best practice is to name it "Default" (See image below).

Press the "Create new version" button.

You will now see the new Config Manager version beneath the root of the Media Manager 5's Config Manager (5.0.0).

You will need to access the versionID of this newly created Media Manager 5's version in the next step.

Step 5: Website Configuration for Media Manager 5

Before the Media Manager 5 can be used, it needs to have some base configuration set, such as which DAM Center it should use. This configuration can be found in the appsettings.json file. This file was part of the content that you have copied into the folder containing Digizuite™ Media Manager during the preparations.

This is the relevant part of the configuration file that you will see once you open it with Notepad++:

{
  "Logging": {
    "LogLevel": {
      "Default": "Warning"
    }
  },
  "AllowedHosts": "*",
  "EnablePrerendering": false,
  "ForceHttps": true,
  "HttpsPort": 443,
  "MediaManagerConfiguration": {
    "GuestUsername": "Guest",
    "GuestPassword": "0ea2f02d5f73c86c220ff08b23d1c3f1",
    "ApiDomain": "dam.digizuite.com",
    "UseHttps": true,
    "WowzaServer": "https://mm.dev.digizuite.com/",
    "WowzaAppName": "mmapp",
    "AbrMediaId": "666",
    "EnabledFeatures": [],
    "InstrumentationKey": "#{instrumentationKey}",
    "ProductVersion": "#{productVersion}",
    "VersionId": "!/5/",
    "UseFederatedAuthentication": false,
    "EnableNormalLogin": false,
    "BusinessWorkflowServiceUrl": "http://localhost:60000/"
  }
}

While you fill out the required fields, the same rules as with the configuration file for the installation scripts apply. Here is the description of how to replace the placeholders (marked in red):

Placeholder	Description

Placeholder	Description
ApiDomain	You need to replace ApiDomain with the base Domain of the DAM Center that Media Manager 5 should be connected to.
`!/2/0`	This is the version ID of the Media Manager 5 ConfigManager version to be used. The easiest way to find it is by opening and logging in to your DAM Center, as demonstrated on the screenshot below: Remember to include the character "/" at the end! Without this, setting the splash screen from within Media Manager 5 will not work.
`#{instrumentationKey}`	If MM5 is installed on a non-production environment, e.g. DEV, POC or TEST, use: 74afe12a-8df3-4efa-998d-936a1021ff6c If MM5 is installed on a production environment, use: e08240fb-c3b6-4b1f-9013-361c81dc506d
`#{productVersion}`	The version of the product that has been installed. Example: 5.0.0-1404

Step 6: Creation of a New IIS Website

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

Unfold the menu under the server name. Next, right-click the webserver and select "Add website...".

Once you select "Add website...", a new window will show up. Here you have to do the following:

Type in your "Site name". The name should be the same as the folder that you created in "Webs" folder for your Digizuite™ Media Manager 5 in the preparation process (second step).
Specify your "Physical path". You do this by clicking "..." next to the text box and searching for the Media Manager 5 folder mentioned above.
Specify the prepared DNS record name in "Host name", which matches "Site name".
Change type to "https".
Check the box "Require Server Name Identification"
Select the correct SSL certificate from the drop-down menu.
Click "OK".

Once the site has been created, go into the bindings for the site in the IIS and create http site on the same domain.

Step 7: Application Pool Setup

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 appear. Confirm that the selected .Net CLR version is "No Managed code".
Close "Edit Application Pool" and open the "Advanced Settings".

Step 8: Whitelist CORS for the MediaManager Application

MediaManager application needs to be whitelisted in the DAM CORS configuration. Please follow the guide provided here: DC5.0.0 5.1 Configuring CORS

Documentation

MM5.7 Installation Process