CLM 4.0.0.1 upgrade on distributed WAS does not work
![]()
Benjamin Chodroff (898●52●31)
| asked Oct 15 '12, 12:38 p.m.
retagged Nov 05 '12, 12:25 p.m. by Bo Chulindra (1.3k●2●7●18)
Even with the options to not look for the JTS, it still looks for it and fails. Don't have time to explain it more, but the work around is to copy the JTS repotools and conf directories to the RTC server for the upgrade, and then delete them once you're done. Anyone else hit this?
|
One answer
![]()
when running the upgrade script, add in ignoreJTSVersionCheck to the repotools command. This will stop any application from contacting the JTS on a seperate server.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.