How to migrate Project Area with lot of content in DNG from Local to Global Configuration Management
Hi All,
We in our project are using at the moment just one project area (locally managed) (name it "Local Configured Project Area") to create the whole specification tree, i.e. we have different folders with modules and requirements at different abstraction levels.
In order to facilitate future configuration management we would like to change/migrate that project area to global configuration. We did the following:
- Created a new project area ("Global Configured Project Area")
- Enabled global configuration in "Global Configured Project Area"
- Created Components for system, subsystems, components...
- We started to clone content from "Local Configured Project Area" to "Global Configured Project Area".
- We noticed that links are missing.
- Is there any other way of doing it that maintains the linkage, such as moving artifacts directly to the new "Global Configured Project Area"?
Thank you very much in advance for your support.
I look forward to hearing from you guys soon.
Alfonso
One answer
The easiest way to keep all of your links is to just turn on versioning in our existing project area, rather than trying to migrate your artifacts to a new project area.
Trying things out initially in a "sandbox" project area with a copy of your data before you turn versioning on in your existing project area is a good thing to do, but once you are comfortable with the behavior in that sandbox, then turning versioning on in the existing project area will keep your links intact.
Comments