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 | ||
|---|---|---|
| ||
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 | ||
|---|---|---|
| ||
| 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 | ||
|---|---|---|
| ||
All the fields in the configuration file are required. |
The following is an example of a valid configuration:
| Code Block | ||
|---|---|---|
| ||
<?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="CD7179C0-260D-4E8C-9558-3540040749CE"/>
<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:
| 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. |
| 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. |
| 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? |
| 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 |
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. |
2.3 Media Manager website configuration
Open the folder <WebsiteFolder> and copy the file Web.Config.new to Web.config. Open it in a text editor and change the following:
- In section appSettings: Change the value for APIURL so that it points to the dmm3bwsv3 URL of your Digizuite™ DAM Center installation, e.g. http://damcenter.mycompany.com/dmm3bwsv3/.
- Specify the backend system user password in section digiConfig/services/@password. For more information, see the Digizuite™ DAM Center documentation.
- Specify the desired location for log files in digiConfig/log/@path.
- If your upload storage is not a local destination, you need to specify userName, password and domain in the UNC section. Then make sure the UNC section is uncommented.
2.
34 Google Analytics setup
| Info | ||
|---|---|---|
| ||
This step is optional. |
If you want to use Google Analytics for statistics, 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 you should name this file privatekey.p12.
Also you need to copy Google Analytics ViewId and account email to the configuration.
2.
45 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.
56 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.
67 Create bindings
- Bindings for both http and https should be configured.
Table of Contents
Table of Contents