Jazz Register Log in

Production Cloud Trial Systems, Previews, BluesDev, SoulDev, Staging Cloud Trial Systems and Previews will be unavailable due to server compliance maintenance and updates of OS, Kernel, and Middleware application patches on THU 2025 APR 17 from 07:30 PM to until approximately 11:30 PM IST (UTC +5:30)

Jazz Forum Welcome to the Jazz Community Forum

Welcome to the Jazz Community Forum

Connect and collaborate with IBM Engineering experts and users

CLM 4.0.0.1 upgrade on distributed WAS does not work

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?

0 votes



One answer

Permanent link
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.

0 votes

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 267

Question asked: Oct 15 '12, 12:38 p.m.

Question was seen: 5,406 times

Last updated: Jul 22 '13, 1:05 p.m.

Confirmation Cancel Confirm