Unable to run CCM up-grade script in distributed environment.
Problem description and business impact Hi Team, I am performing an up-grading of CLM 602 to CLM 605 on my production environment. Topology: Distributed environment- 1. Server 1: JTS, DCC,LQE and RS. 2. Server 2: CCM,QM and RELM. 3. Server 3: RM and DM. 4. Server 4: DB2 5. Server 5: IHS. I have run upgrade script on server 1 and it all went fine, It JTS, DCC, LQE and RS has updated. But, When I switch to Server 2, and insert command for CCM upgrade it has given me below error, also find the screen shot attachted "E:\IBM\JazzTeamServer_605\server>upgrade\ccm\ccm_upgrade.bat - oldApplicationHome "E:\IBM\JazzTeamServer\server\conf" -newJTSHome "E: \IBM\JazzTeamServer_605\serv er\conf" -updateTomcatFiles no -updateAppServerFiles no Cannot find the JTS repotools command '"E: \IBM\JazzTeamServer_605\server"\repoto ols-jts.bat'. Verify that the -newJTSHome parameter '"E: \IBM\JazzTeamServer_605\server\conf"' is pointing to the new JTS server configuration directory, for example, 'JazzIns tallRoot\server\conf' and that the -jtsContextRoot parameter 'jts' is correct. E:\IBM\JazzTeamServer_605\server>upgrade\ccm\ccm_upgrade.bat - oldApplicationHome "E:\IBM\JazzTeamServer\server\conf" -newJTSHome "Y:\server\conf" - updateTomcatF iles no -updateAppServerFiles no"
One answer
I only have experience with performing upgrades on 'All-in-one' configurations (non-distributed) but the command you listed for the CCM upgrade is showing '-newJTSHome' is on the same drive location as CCM (both are on an "E:\" drive). This seems contrary to your statement that you are running in a distributed environment.
For comparison: The following upgrade instructions were generated for me by the IBM when I entered the "C:\" drive for my JTS application and the "D:" drive for my CCM application (note that paths are all faked for this example):
upgrade\ccm\ccm_upgrade.bat -oldApplicationHome "D:\ProgFiles\IBM\JazzServer6.0.2\server\conf" -newJTSHome "C:\ProgFiles\IBM\JazzServer6.0.5\server\conf" -noPrompt -noVerify -noStepPrompt -noEditor.
Look at the instructions you used for upgrading the applications located on Server1 and compare them to the instructions you used for upgrading CCM. When upgrading the CCM application - the path to the files at the new JTS location (on Server1) needs to be visible from Server2.