...
This section provides information on how to install Digizuite DAM Center.
Before upgrading
If you are installing a new DC skip this step.
| Info | ||
|---|---|---|
If you are upgrading from before 5.3 to this version, you must run this application! | ||
| Info | ||
| ||
SolR has been removed from the 5.6.1 Installer, Existing configuration Settings in Web.Config (SolRUrl and SolRUncPath) are maintained during upgrade. Important for DamForOptimizely or other DC customers that still needs SolR - the Windows Group "AppPools-<SITENAME>" needs R/W permissions for the SolRUncPath folder |
...
Before upgrading
If you are installing a new DC skip this step.
| Info |
|---|
If you are upgrading from before 5.3 to this version, you must run this application! |
This app should be run to cleanup a table which is likely to have data errors. This is done as an app to avoid a potential long running SQL script as part of the DAM update process.
The app:
| View file | ||||
|---|---|---|---|---|
|
Ensure all queues in RabbitMQ are empty. We do not support upgrading with data left in RabbitMQ.
Running the app
Install ElasticSearch: DC 5.6 Elastic Search
Running the app
Do a database backup first.
...
| Info |
|---|
Always remember to backup the database before upgrading! |
The Digizuie Digizuite DAM Center is installed/Upgraded using Powershell. The package, provided by the Digizuite DAM Vendor, is a zip file with the following structure:
...
To install a new Digizuite DAM Center with UNC storage, the important parameters are the following
Important note: The installation script is NOT idempotent, which means if it is run again it will not validate and correct changes to reflect the config that was used in the installation process.
Issues arising from this could be that for example services and webs folder have been created on the C: drive instead of a dedicated drive.
The only way of correcting these issues are to completely remove everything that the installation script created in this order (some services might need to be deleted by manually killing processes for that service):
- Rabbitmq (service, services folder, references in registry)
Erlang (service, services folder, references in registry)
Nats (service, services folder)
Grafana (service, services folder)
Loki (service, services folder)
Promtail (service, services folder)
Windows exporter (service, services folder)
nssm (service, services folder)
delete DAM database via SQL management studio
- delete SQL security login : "admin_<customername>_dam"
- Delete all IIS sites and App pools in IIS and restart IIS
- check that all these services have been removed (to delete each: use sc delete "<servicename>" via CMD, not Powershell, and if they still don't get removed, restart server)
Keep webs files as these are still relevant and can be moved into the new webs folder on the dedicated drive fx. H: drive
Then finally run the install script again
| Variable | Value | Description |
|---|---|---|
| NewInstallation | $True | This has to be true on new installations, as otherwise databases won't be created |
| PrestagedDatabases | $True/$False | If databases and users have not been pre-staged (created), then set this to $False, $True otherwise. This is for installing without sysadmin rights |
| Azure parameters | Leave them blank, if UNC storage is used |
...
NOTE: If another antivirus is used these paths should be excluded via the management interface of the Antivirus.
| Variable | Value | Description |
|---|---|---|
| StorageArea | localStoragePath | Storage Area eg. G:\Storage\ |
| PrometeusArea | PrometeusDataFolder | Prometeus Data Folder eg. G:\Services\prometheus-2.19.0.windows-amd64\data |
| ElasticSearchArea | OnPrem Elastic Search Data Folder | Elastic Search Data Folder eg. eg. G:\Services\ElasticSearch\data |
| LogArea | LogRoot | Log Area eg. G:\LogFiles\dc.example.com |
| RabbitStorage | RabbitMQ Data Area | RabbitData Area eg: RABBITMQ_BASE environment variable |