Do I need to migrate link validity on RM if I don't have configuration management enabled?
I'm upgrading from V6.0.6 to V7.0.2 and use command line scripts to automate my upgrade. The RM upgrade script now needs me to stop at certain steps and stop/start the repository in order to migrate the link validity, however from what I can see I need configuration management enabled on the RM in order to enable link validity and I haven't enabled it. Am I safe to set -migrateLinkValidity to 'no' for the rm upgrade?
Is there any way to validate whether linkvalidity is enabled on my RMs?
Accepted answer
Short answer: Correct ... if you haven't enabled configuration management in your RM project areas, you are safe to set -migrateLinkValidity to 'no'.
You only need to perform the migrate link validity step if you have made link validity assertions that you want preserved.
You cannot make link validity assertions in 6.0.6 if you have not enabled configuration management, so you would not have any link validity assertions to preserve. So it is sufficient to confirm that configuration management has not been enabled on your RM project areas.