...

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").

Image Modified

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".

...

This is the relevant part of the configuration file that you will see once you open it with Notepad++:

PlaceholderDescription#{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".

Image Removed

#{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".

Image Removed

#{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".

Image Removed

#{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".

Image Removed

< digiConfig appSettings>    < log add  name key=" Mediaportal guestUsername"  path value=" #{dzDigiConfigLogPath} Guest"  filter="Warning" />    < unc add  useNetUseApi key=" true guestPassword"  userName value=" #{dzDigiConfigUncUsername}" password="#{dzDigiConfigUncPassword}" domain="#{dzDigiConfigUncDomain}" shareDriveName="" 0ea2f02d5f73c86c220ff08b23d1c3f1" />    <add key="RestApiUrl" value="https://DAMCENTER_URL/api/v2/" />    < services add  userName key=" System BaseFakeApiUrl"  userType password="#{dzDigiConfigServicesPassword}"/>  </digiConfig>  <appSettings>    <add key="guestUsername" value="Guest value=" BackEnd" https://DAMCENTER_URL/Comment/commenting/api/v1"/>    <add key="BaseApiUrl" value="https://DAMCENTER_URL/dmm3bwsv3" />    <add key=" guestPassword DamMediaUrl" value=" 0ea2f02d5f73c86c220ff08b23d1c3f1 https://DAMCENTER_URL/" />    <add key=" RestApiUrl WowzaServer" value="https:// DAMCENTER WOWSA_URL /api / v2/ " />    <add key=" BaseFakeApiUrl LoginServiceUrl" value="https:// DAMCENTER LOGIN_SERVICE_URL /Comment/commenting/api/v1"/> "/>      <add key=" BaseApiUrl WowzaAppName" value=" https://DAMCENTER_URL/dmm3bwsv3 mmapp" />    <add key=" DamMediaUrl abrMediaUrl" value=" https://DAMCENTER_URL/ 666" />    <add key=" WowzaServer enabledFeatures" value=" https://WOWSA_URL/ " />      <add key=" LoginServiceUrl/> UseFederatedAuthentication" value="false" https://LOGIN_SERVICE_URL"  />      <add key=" WowzaAppName ConfigVersionId" value=" mmapp !/2/0" />    <add key=" abrMediaUrl P3PCompactPolicy" value=" 666 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=" enabledFeatures InstrumentationKey" value="#{instrumentationKey}" />      <add key=" UseFederatedAuthentication ProductVersion" value=" false #{productVersion}" />       < 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):

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):

Example of a valid configuration:

Image RemovedImage Added

Step 6: Creation of a New IIS Website

...

1. Expand the server content from the IIS Manager window and select the "Application Pools" menu.
2. Locate the pool with the same name as your website and double-click it.
3. The "Edit Application Pool" window will appear. Confirm that the selected .Net CLR version is 4+.
4. Close "Edit Application Pool" and open the "Advanced Settings".
5. Under "Process Model" change the Identity to "LocalService".

Image Removed

Image Removed

...

1. Application Pool" and open the "Advanced Settings".
2. Under "Process Model" change the Identity to "LocalService".

Image Added

Image Added

Image Added

Step 8: Whitelist CORS for the MediaManager Application

MediaManager application needs to be whitelisted in the DAM CORS configuration. Please follow the guide provided here: DC5.0.0 5.1 Configuring CORS