Introduction
DMS module do not exist anymore in M5. His re
Tasks
Migrate Binary data to DAM repository
GOAL: Migrate DMS (or other repository) into the DAM repository.
STEPS:
Class: ContentModuleMigrationTask
Constructor attributes:
| Property | Description | Default value | Valid values |
|---|---|---|---|
taskName | Task name used by the reporting tool, and to log/display informations related to this task. | String | |
taskDescription | Task Description used to display informations in the admin. central update view. | String | |
moduleName | Name of the module currently handled. This is used by the ConfiguredPostMigrationTask in order to retrieve the appropriate properties files. | Module name: demo-project | |
repository | Repository name of the content to migrate. | Usually website | |
sitePaths | List of the root path of site to migrate. For example for the demo-project: Arrays.asList("/demo-project", "/demo-features") | List<String> | |
disposeObservation | Inherited from the old migration process. | false | boolean |
stkSites | Define if your content is based on STK extends. In case of STK extends, additional migration tasks are performed. | boolean |
Change DMS to DAM content references
Move uploaded binary from content(website) to DAM repository
FAQ:
Overview
Content Tools