...
In the folder named "MediaManager.DbUpgrade" locate the configuration file named "MediaManagerappsettings.DbUpgradejson". Right-click it and select "Edit with Notepad++". This is what you will see:
| Code Block |
|---|
<configuration> <connectionStrings> <add name="db" connectionString="#{dzDAMConnectionString}"/> </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"/>...
| ||
{ "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://mm-dam.dev.digizuite.com/dmm3bwsv3", "ApiUsername": "System", "ApiPassword": "a2ddc680310e876a61c5d4bd7e52663f", "VersionGuid": "0B59C5CF-E3A9-4043-AEDB-FCEAA4040D4C", "Availability": "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>...
,
"Timeout": "00:30:00"
}
} |
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.
...
| 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.
| ||
| 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:
, 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.
...
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 "webappsettings.configjson" 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++:
...
<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>| Code Block | ||
|---|---|---|
| ||
{
"Logging": {
"LogLevel": {
"Default": "Warning"
}
},
"AllowedHosts": "*",
"EnablePrerendering": false,
"ForceHttps": true,
"HttpsPort": 443,
"MediaManagerConfiguration": {
"GuestUsername": "Guest",
"GuestPassword": "0ea2f02d5f73c86c220ff08b23d1c3f1",
"ApiDomain": "mm-dam.dev.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 |
|---|---|
DAMCENTER_URLApiDomain | You need to replace DAMCENTER_URL ApiDomain with the base URL 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 |
Example of a valid configuration:
...
Step 6: Creation of a New IIS Website
...
- 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+"No Managed code".
- Close "Edit Application Pool" and open the "Advanced Settings".
- Under "Process Model" change the Identity to "LocalService".
...