THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- generate a new 2.0 project
- export
content.xml
from 1.2 deployment - run the migration tool to convert most of
content.xml
into someMasterContent.xml
- there are some items which cannot be directly migrated, as virtual schemas and related mappings - put the generated
MasterContent.xml
undercore/src/test/resources/domains
in the new 2.0 project - run the new 2.0 project in embedded mode while watching all logs - if errors are found, make appropriate corrections into
core/src/test/resources/domains/MasterContent.xml
- this might involve migrate 1.2 customized classes into their respective 2.0 counterparts - once errors are gone, access the admin console in embedded mode and look if every configuration item is at its place (schema, connectors, resources, mappings, notifications, ...)
- manually add the items that cannot be automatically migrated
- if using delegated administration, reconstruct roles and entitlements under the new security model[DISCUSS] Realms
- verify that all operations (CRUD / propagate / synchronize / push) about users and roles in 1.2 are now working (CRUD / propagate / pull / push) with users and groups in 2.0
- export the working configuration and save it as
core/src/test/resources/domains/MasterContent.xml
...