Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 24 Next »

Info

This process must be repeated every time the Digizuite Mobile App is updated

For this installation, no website is needed. Digizuite Mobile App is a self employed product that reflects the Digizuite Media Manager.

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 Mobile App, an installation script needs to be run towards the DAM Center.

For DAM Center releases later than than 5.3.0 (incl. 5.3.0)

Use this version for 5.3.2 and up:

Copy the zip installation folder from swinstall, into the server and unzip the file

In the folder, there is a appsettings.json file which needs to have some data set:

{
    "Logging": {
        "LogLevel": {
            "Default": "Debug",
            "System": "Information",
            "Microsoft": "Information"
        }
    },
    "Upgrade": {
        "ConnectionString": "#{ConnectionString}",
        "RunGenerateSearchForAll": true,
        "ApiUrl": "#{ApiUrl}",
        "ApiUsername": "#{ApiUsername}",
        "ApiPassword": "#{ApiPassword}",
        "VersionGuid": "1356CC29-B3A4-E6CC-152A-FEE1504E0C34",
        "Availability": "74A5A102-A310-4BB7-9E84-0B14C36436B2",
        "Timeout": "00:30:00"
    }
}

Here is a description of all the configuration parameters (the red parameters need to be filled out/updated):

Parameter nameDescription
ConnectionString

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 Media Manager's corresponding appsettings.json file.

RunGenerateSearchForAllDetermines whether all Solr searches should be repopuplated after the install/update. Default: true
ApiUrlThe URL to the DAM Center external API. Usually this would be the base URL of the DAM Center, with /dmm3bwsv3 added to the end.
ApiUsernameThe a high level user. Default: System
ApiPasswordMD5 hash of the password for the user set in apiUsername. You will find this in the db members table.
VersionGuid

A unique key which refers to mobile. Don't change it if it works. Else, locate your Mobile GUID in Mobile's configManager. Default: 1356CC29-B3A4-E6CC-152A-FEE1504E0C34

AvailabilityGUID of metadatafield that controls publishing. Default: 74A5A102-A310-4BB7-9E84-0B14C36436B2
TimeoutMaximum time (in seconds) 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, run db-upgrade.exe. You may choose to run it py double clicking it, by calling it from the CMD prompt, or, if you want to retain the log, run it vis PowerShell.

For DAM Center releases earlier than 5.3.0

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=customer_dam;User ID=admin_customer_dam;Password=admin_customer_dam"/>
  </connectionStrings>
  <appSettings>
    <!-- JobService GenerateSearchForAll -->
    <add key="runGenerateSearchForAll" value="true"/>
    <add key="apiUrl" value="http://customerdc.digizuite.com/dmm3bwsv3"/>
    <add key="apiUsername" value="System"/>
    <add key="apiPassword" value="#{dzApiPassword}"/>

    <!-- 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>

Here is a description of all the configuration parameters (the red parameters need to be filled out/updated):

Parameter nameDescription
connectionString

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 Media Manager's 5.1 DbUpgrade.exe.config file.

runGenerateSearchForAllDetermines whether all Solr searches should be repopuplated after the install/update. Default: true
apiUrlThe URL to the DAM Center external API. Usually this would be the base URL of the DAM Center, with /dmm3bwsv3 added to the end.
apiUsernameThe system user. Default: System
apiPasswordMD5 hash of the password for the user set in apiUsername. You will find this in the db members table.
versionGuid

The Guid can be generated in e.g. https://www.guidgenerator.com/

Otherwise, the field can use the Media Manager version GUID from the DAM Center. Where do I find this GUID?

availabilityGuid of metadatafield that controls publishing. Default: 74A5A102-A310-4BB7-9E84-0B14C36436B2
usingEmbeddedScriptsDetermines 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
timeoutInSecondsMaximum 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 from the cmd prompt.

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.

MobileAppConfiguration.json

  1. Download the following file MobileAppConfiguration.json
  2. Add information to the file
  3. Add the file to the root of the DC web folder

Configuration (OOBE 5)

A new version of Digizuite Mobile App needs to be created in the DAM center:

  1. Open the DAM center
  2. Go to ConfigManager
  3. Select Digizuite Mobile and expand the folder
  4. Click on "Default" folder
  5. Create a new version in the upper right corner. Name could e.g. be "Mobile"
  6. Go to ConfigManager → Digizuite Mobile → Default → Current version → Searches
  7. Select the Framework Search, Copy ID and Delete "Mobile/Is Public" in Input
  8. Create "Options/unlocked" in Input
  9. Create "asset.prevref" in Input 
    1. This to ensure replaces isn't returned in the search
  10. Create "asset.prevref" in Output

  11. Copy ID and Delete "Mobile/Is Public" in Output
  12. Create "Options/unlocked" in Output

  13. Copy ID and Delete "Mobile/Is Public" in Output and create "Options/unlocked" for
    1. GetAssetById
    2. GetAssetByBasketId
    3. DigiZuite_System_Framework_My_Favorites
  14. The format "Tablet H264 2048kbit ffmpeg" is used in the mobile video player
    1. Ensure the format is enabled and added to the profile

Once the configuration is done in the DAM center, information about the customer must be sent to LET Software. The information can be found:

iOS: /wiki/spaces/PP/pages/3912074824

Android: /wiki/spaces/PP/pages/850952193

Filters

In order to enable filters, your mobile Digizuite_System_Framework_Search your need to enable Solr.

If Solr is not enabled, filters will not work.

  • No labels