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:
- You will work with the folder named "MediaManager.DbUpgrade.(version)" in Step 3.
- 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:- unfold the menu with the server name
- unfold "Sites"
- right click on the name of one of the existing Digizuite products, for example your DAM center
- 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
3.1 Preparation of the configuration file
In the folder named "MediaManager.DbUpgrade" locate the configuration file named "MediaManager.DbUpgrade". Right-click it and select "Edit with Notepad++". This is what you will see:
<configuration> <connectionStrings> <add name="db" connectionString="/> </connectionStrings> <appSettings> <!-- JobService GenerateSearchForAll --> <add key="runGenerateSearchForAll" value="true"/> <add key="apiUrl" value="#{APIURL}"/> <add key="apiUsername" value="#{dzApiUsername}"/> <add key="apiPassword" value="#{dzApiPassword}"/> <!-- Standard/Required --> <add key="versionGuid" value="0b59c5cf-e3a9-4043-aedb-fceaa4040d4c"/> <add key="availability" value="74A5A102-A310-4BB7-9E84-0B14C36436B2"/> <add key="usingEmbeddedScripts" value="true"/> <add key="timeoutInSeconds" value="1800"/> </appSettings> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.6.2"/> </startup></configuration> |
|---|
The names of the parameters that need to be changed are marked in green above. The fields marked in red above need to be either completely replaced with the values relevant for your environment or double-checked, if they are default values. It is important that all of the fields are filled out correctly, without missing or adding characters.
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 chages to this file.
Here is the description of all the configuration parameters:
| Parameter name | Description |
|---|---|
| db | 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.
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 |
Example of a valid configuration:
3.2 Running the installation script
Once the config file is set up correctly, the next step is to simply run the executable file with the same name as the configuration file that you have filled in in the previous step, as demonstrated on the screenshot:
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: 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 "web.config" 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++:
<digiConfig> <log name="Mediaportal" path="#{dzDigiConfigLogPath}" filter="Warning"/> <unc useNetUseApi="true" userName="#{dzDigiConfigUncUsername}" password="#{dzDigiConfigUncPassword}" domain="#{dzDigiConfigUncDomain}" shareDriveName=""/> <services userName="System" userType="BackEnd" password="#{dzDigiConfigServicesPassword}"/> </digiConfig> <appSettings> <add key="guestUsername" value="Guest" /> <add key="guestPassword" value="0ea2f02d5f73c86c220ff08b23d1c3f1" /> <add key="WowzaAppName" value="mmapp" /> <add key="abrMediaUrl" value="666" /> <add key="enabledFeatures" value="" /> <add key="UseFederatedAuthentication" value="false" /> <add key="ConfigVersionId" value="!/2/0" /> <add key="P3PCompactPolicy" value="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI" /> <add key="InstrumentationKey" value="#{instrumentationKey}" /> <add key="ProductVersion" value="#{productVersion}" /> </appSettings> |
|---|
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 |
|---|---|
#{dzDigiConfigLogPath} | This is the absolute file path to the folder where all the Media Manager 5 log files will be stored. This folder was created in point 4 of the preparation step. In order to find out the correct path, go to the abovementioned folder, click on the breadcrumb trail that leads to it, and then copy it. Example of a correct file path: C:\LogFiles\MediaManager5 |
#{dzDigiConfigUncUsername} | This is the username for the assetstream user. This information can be found in the DAM Center's configuration file. You need to copy information from the section "digiConfig".
|
#{dzDigiConfigUncPassword} | This is the password for the assetstream user. This information can be found in the DAM Center's configuration file. You need to copy information from the section "digiConfig".
|
#{dzDigiConfigUncDomain} | This is the domain of the assetstream user. This information can be found in the DAM Center's configuration file. You need to copy information from the section "digiConfig".
|
#{dzDigiConfigServicesPassword} | 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".
|
DAMCENTER_URL | You need to replace DAMCENTER_URL with the base URL 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 easiet 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! |
#{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 |
Example of a valid configuration:
Step 5: 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 6: 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 4+.
- Close "Edit Application Pool" and open the "Advanced Settings".
- Under "Process Model" change the Identity to "LocalService".
