Info | ||
---|---|---|
| ||
This process must be repeated every time the Media Manager is updated. |
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, an installation script need to be applied to the DAM Center to accompany the installation:
...
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 (the red parameters need to be filled out/updated):
Parameter name | Description |
---|---|
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. |
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. 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? |
availability | Guid of metadatafield 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, 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. |
Configuration
A new version of Digizuite Mobile App needs to be created in the DAM center:
- Open the DAM center
- Go to ConfigManager
- Select Digizuite Mobile and expand the folder
- Click on "Default" folder
- Create a new version in the upper right corner. Name could e.g. be "Mobile".
Once the configuration is done in the DAM center, information about the customer must be send to LET Software. The information can be found:
iOS: 1355 - Build Digizuite™ Mobile app for iOS - new
Android: /wiki/spaces/PP/pages/850952193