The Importer is located with the DAM installation files in a separate zip file.
- Create a folder where you want the app to be. It's recommended to use an "non-program-files" location to avoid windows rights management issues or at least to set path configurations to a unc path outside. It's required to have write access to all configured directory paths.
- Unzip the contents to the folder.
- Optional: Run DamImporterMatchSearchByAssetid.sql if or when you need a match search that matches assetId. This can also be done at a later time. The default DamImporterMatchSearch matches against a string metafield containing filenames.
- Set application level configuration in Importer.exe.config (app mode) and/or ImportService.exe.config (service mode). See "DC5.0.0 Application configuration".Open install.ps1, which can be found among the unzipped content, with a text editor
- Fill out the unset fields: ConnectionstringDAM, ServiceFolder, ApiUrl, ApiUsername, and ApiPassword. Keep in mind that ApiPassword, must be an MD5 hash of the actual password
- Update ServiceName and ServiceDisplayName to something that is relevant for you.
- Save, and execute Install.ps1
- Set import level configuration in xml files in the subfolder ImportConfigs. See "DC5.0.0 Import configuration".
- Set metadata level configuration if needed.Install as a service if you need. See section below. Set the service to start automatically.
Install as a Windows service
To install the Importer service, please do the following steps:
First of all, enter a command prompt or PowerShell prompt, and navigate to your import service folder.
Run these two lines. The first to change to the correct hard drive - and secondly to navigate to the root of the importer
Firstly:
Code Block | ||
---|---|---|
| ||
[driveLetter]: |
e.g.
Code Block | ||||
---|---|---|---|---|
| ||||
D: . |
Secondly:
Code Block | ||
---|---|---|
| ||
"[driveLetter]:\[pathToImporter]" |
e.g.
Code Block | ||
---|---|---|
| ||
"D:\Importer" |
Now that you're in the correct folder within your chosen command prompt, you can now run the service installation one-liner:
Code Block | ||
---|---|---|
| ||
sc create [ImportServiceCustomName] binPath= "[driveLetter]:\[pathToImporter]\ImportService.exe" DisplayName= "[importServiceNameWithSpaces]" |
e.g.
...
title | Windows command prompt |
---|
...
App mode vs. service mode
Running the Importer as service works essentially the same as in app mode. The differences are highlighted in the following table:
Feature | App mode | Service mode |
---|---|---|
Continous monitoring | No | Yes |
Halt on fatal exception 1) | Yes | No 2) |
...