...
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 "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}"/>...
<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 |
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 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
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".
...
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 4+.
- Close "Edit Application Pool" and open the "Advanced Settings".
- Under "Process Model" change the Identity to "LocalService".
Step 8: Whitelist CORS for the MediaManager Application
| Info |
|---|
This section applies only for MediaManager 5.0.5 and higher |
MediaManager application needs to be whitelisted in the DAM CORS configuration. Please follow the guide provided here: DC5.0.0 5.1 Configuring CORS