How to upgrade Report Builder in a distributed CLM system without mapping network drives
I want to upgrade IBM Rational Collaborative Lifecycle Management Solution (CLM) 5.0.2 to 6.0 in a distributed environment on Windows.
I don't have a possibility to map network drives between the individual machines in the system. It looks like this is a problem for the IBM Rational Report Builder (RB) application.
The Interactive Upgrade Guide states the following:
To upgrade the Report Builder application, you must run the wrapper script. The Report Builder application does not include repotools. To use the wrapper script, you must be able to mount the network drive that the Report Builder application is installed on.
How can I upgrade Report Builder in a distributed CLM if I cannot map network drives?
I don't have a possibility to map network drives between the individual machines in the system. It looks like this is a problem for the IBM Rational Report Builder (RB) application.
The Interactive Upgrade Guide states the following:
To upgrade the Report Builder application, you must run the wrapper script. The Report Builder application does not include repotools. To use the wrapper script, you must be able to mount the network drive that the Report Builder application is installed on.
How can I upgrade Report Builder in a distributed CLM if I cannot map network drives?
2 answers
You can still upgrade the RB application in a distributed environment using the rs_upgrade.bat script directly with -ignoreJTSVersionCheck argument.
This argument will skip attempts to access the IBM Rational Jazz Team Server's (JTS) installation directory to perform version compatibility checks.
To upgrade RB application in a distributed environment without mapping network drives:
This argument will skip attempts to access the IBM Rational Jazz Team Server's (JTS) installation directory to perform version compatibility checks.
To upgrade RB application in a distributed environment without mapping network drives:
- Open command prompt.
-
Change directory to
RB installation directory\server. -
Run the following command:
upgrade\rs\rs_upgrade.bat -oldApplicationHome old version installation directory\server \conf -updateTomcatFiles no -ignoreJTSVersionCheck -noPrompt -noVerify -noStepPrompt -noEditor.
Hi Adam,
The upgrade scripts try to check the version of your JTS to make sure that it has been upgraded first before the other apps. If it is in a distributed environment, the officially recommended way is to map a network drive. But as long as you make sure to upgrade JTS first, you can then include the "-ignoreJTSVersionCheck" option in your rs_upgrade.bat command to get around this without having to map a drive.
The upgrade scripts try to check the version of your JTS to make sure that it has been upgraded first before the other apps. If it is in a distributed environment, the officially recommended way is to map a network drive. But as long as you make sure to upgrade JTS first, you can then include the "-ignoreJTSVersionCheck" option in your rs_upgrade.bat command to get around this without having to map a drive.