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.
- 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.
The Importer is now installed as a service, and will automatically import any files in the folder which the import configuration was set to import from during step 7.
You can also choose to run ImportService.exe manually (App mode).
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) |
1) A fatal exception in this context means an error the Importer does not know how to safely proceed with. Specifically with data errors or data parse errors the Importer will take a safe approach and not do anything rather than set wrong metadata.
2) As a service if FailureDirectory is set the involved files will be moved and not retried. If not moved they will be retried.