Are c/alm links preserved after upgrade to RTC 2.0.0.2?
Hi,
I currently have RTC 2.0.0.1, RQM 2.0.01 and RRC 2.0 linked through the C/ALM integrations. The RTC is Standard editiion installed from the .zip file. I plan to install RTC 2.0.0.2 and would like to preserve the current C/ALM links between project areas.
Will repotools -export / -import support this, and if so which config files/folders do I need to copy over?
If the above won't work, do I need to unlink the project areas, and then re-link once RTC 2.0.0.2 is installed?
Thanks,
Simon
I currently have RTC 2.0.0.1, RQM 2.0.01 and RRC 2.0 linked through the C/ALM integrations. The RTC is Standard editiion installed from the .zip file. I plan to install RTC 2.0.0.2 and would like to preserve the current C/ALM links between project areas.
Will repotools -export / -import support this, and if so which config files/folders do I need to copy over?
If the above won't work, do I need to unlink the project areas, and then re-link once RTC 2.0.0.2 is installed?
Thanks,
Simon
One answer
I currently have RTC 2.0.0.1, RQM 2.0.01 and RRC 2.0 linked through
the C/ALM integrations. The RTC is Standard editiion installed from
the .zip file. I plan to install RTC 2.0.0.2 and would like to
preserve the current C/ALM links between project areas.
Will repotools -export / -import support this, and if so which config
files/folders do I need to copy over?
If the above won't work, do I need to unlink the project areas, and
then re-link once RTC 2.0.0.2 is installed?
Going from 2.0.0.1 to 2.0.0.2 does not require a migration, so it is not
necessary to run repotools -export/-import. You can just update the
server with the DB unchanged.
You need to make sure, however, that friendsconfig.rdf and services.xml
are preserved when updating.
--
Regards,
Patrick
Jazz Work Item Team