...
For Unix-based systems:
| Code Block | ||
|---|---|---|
| ||
sh ./bin/migrate.sh --source <path_to_v1.1_files> --target <path_to_v1.3_files> |
...
If the target exists, then the above command will fail. The migration tool has the ability to overwrite the target folder, as shown below.
| Code Block | language | bash
|---|
sh ./bin/migrate.sh --source <path_to_v1.1_files> --target <path_to_v1.3_files> --overwrite |
The above options will consolidate the Concept Determination Methods (the concept mappings) into a single file called cdm.xml. However, the Concept Determination Method mappings can be split up into multiple files, one per ConceptDeterminationMethod, using the following example:
| Code Block | language | bash
|---|
sh ./bin/migrate.sh --source <path_to_v1.1_files> --target <path_to_v1.3_files> --split-cdm |
...
Before running the REST Service-based migration, OpenCDS must be running and configured to use BDB as the backend (see Configuration Backend Tooling for details). Once this is complete, migration can be performed using the following command:
| Code Block | language | bash
|---|
sh ./bin/migrate.sh --username <user> --password <pass> --source <path_to_v1.1_files> --target <url_to_opencds_config_rest_service> |
This method will migrate data using the PUT method for collections (see Configuration API (REST) Version 1.0 for details).
PLEASE NOTE: Any existing configuration data in the OpenCDS Configuration Rest Service will be discarded and replaced.
...