Versions Compared

Old Version 20

changes.mady.by.user Mathias Mattson (MHM)

Saved on

compared with

New Version Current

changes.mady.by.user Gosia Creosteanu (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Info
titleInfo

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:

Image Added

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:

...

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 this information can be found in the Media Manager's corresponding appsettings.json file.

RunGenerateSearchForAll

Determines whether all Solr searches should be

repopuplated

repopulated after the

install

installation/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.
ApiUsername

The

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. ElseOtherwise, locate your Mobile GUID in Mobile's configManager.

Default: 1356CC29-B3A4-E6CC-152A-FEE1504E0C34

Availability

GUID of

metadatafield

metadata field that controls publishing.

Default: 74A5A102-A310-4BB7-9E84-0B14C36436B2

Timeout

Maximum 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 and saved, run db-upgrade.exe. You may choose to run it py by double clicking it, by calling it from the CMD prompt, or, if you want to retain the log, run it vis via 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. 

...

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 this information can be found in the Media Manager's 5.1 DbUpgrade.exe.config file.

runGenerateSearchForAll

Determines whether all Solr searches should be

repopuplated

repopulated after the install/update.

Default: true

apiUrlThe URL to the DAM Center's 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

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. 

More information can be found here: Where do I find this GUID?

availability

Guid of

metadatafield

metadata field that controls publishing.

Default: 74A5A102-A310-4BB7-9E84-0B14C36436B2

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 and saved, the next step is to simply run the MediaManager.DbUpgrade.exe file from the cmd prompt.

Note
titleNote

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.

Modifying the configuration file

...

(

...

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
    Image Removed
  8. Create "Options/unlocked" in Input
    Image Removed
  9. Create "asset.prevref" in Input 
    1. This to ensure replaces isn't returned in the search
      Image Removed
  10. Create "asset.prevref" in Output
    Image Removed
  11. Copy ID and Delete "Mobile/Is Public" in Output
  12. Create "Options/unlocked" in Output
    Image Removed
  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.1) Download the following file MobileAppConfiguration.json

(2) Edit the information in the file according to the following guidelines:

Parameter nameDescription

ApiUrl

The URL to the DAM Center's external API. It is formed by the base URL of the DAM Center and ending "/dmm3bwsv3/". Remember to include the character "/" at the end!

Example: https://demo3dc.digizuite.com/dmm3bwsv3/

MMUrl

The URL to the Media Manager's website.

Example: https://demo3mm5.digizuite.com/

VersionId

This is the current version ID of Digizuite Mobile's ConfigManager version to be used.

The easiest way to find it is by opening and logging in to your DAM Center, as demonstrated on the screenshot below:

Image Added

Use "!" in front of the VersionId to set that specific version as the current one, and not any version available beneath.

Remember to include the character "/" at the end! 

SSOLoginMode

This line enables or disables the ability to log in through SSO.

Default: true

(3) Add the file to the root of the DC web folder