Info
This process must be repeated every time the Media Manager is updated.
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 proceeding with running the installation script.
Before you can use the Media Manager, an installation script need to be applied to the DAM Center to accompany the installation:
- Copy the zip installation folder from swinstall, into the server and unzip the file
- The folder includes a "MediaManager.DbUpgrade" executable that is an all-in-one. You must specify a variety of configuration parameters in the accompanying MediaManager.DbUpgrade.exe.config file before running the executable script.
The following is an example of a valid configuration:
<?xml version="1.0" encoding="utf-8"?>
<configuration>
<connectionStrings>
<add name="db" connectionString="Server=localhost;Persist Security Info=False;MultipleActiveResultSets=False;Initial Catalog=cvk_dam;User ID=admin_cvk_dam;Password=admin_cvk_dam"/>
</connectionStrings>
<appSettings>
<!-- JobService GenerateSearchForAll -->
<add key="runGenerateSearchForAll" value="true"/>
<add key="apiUrl" value="http://cvkdc.dev.digizuite.com/dmm3bwsv3"/>
<add key="apiUsername" value="System"/>
<add key="apiPassword" value="21cdee6d24ac4a16ba7fe03b2f25d1bc"/>
<!-- Standard/Required -->
<add key="versionGuid" value="5021806d-157c-466d-b346-ba7bed246968"/>
<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>
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:
| Parameter name | Description |
|---|---|
| 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) |
| runGenerateSearchForAll | Determines whether all Solr searches should be repopuplated after the install/update. Default: true |
| apiUrl | The URL to the DAM Center external API. Usually this would be the base URL of the DAM Center, with /dmm3bwsv3/ added to the end. |
| apiUsername | The system user. Default: System |
| apiPassword | MD5 hash of the password for the user set in apiUsername. You will find this in the members table. |
| 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 |
| usingEmbeddedScripts | Determines 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 |
| timeoutInSeconds | Maximum time to wait before timing out any request. If using runGenerateSearchForAll, the advised value is 1800. Default: 1800 |
| Availability | Guid 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
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.