what are recommendations for upgrading CLM from 4.0.6 to 5.0.1
![]()
Hi,
We plan to upgrade CLM from 4.0.6 to 5.0.1.
|
Accepted answer
![]()
Benjamin Silverman (4.1k●6●10)
| answered Oct 06 '14, 12:45 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Installing 5.0.1 has no impact on the existing 4.0.6 environment. You can install as many versions as you'd like to different paths. They all contain their own unique set of configuration files as to not step on existing installations. I hope that answers your question.
anoop mc selected this answer as the correct answer
|
7 other answers
![]()
While you install 5.0.1, you will get warning regarding existing package . Just ignore it.
|
![]() Hi Anoop, 1) Install the RTC 5.0.1 on the same machine based on your components if its distributed setup ( JTS,CCM,RQM,RM) 2) Stop the serivce 3) Backup the database. 4) Follow the below Interactive Upgrade for the Steps. 5) RM There is a great wiki page on this upgrade created by development that you should check out (and book mark for future reference)
* High level Steps.
Regards,
Arun.
|
![]()
thanks for the reply. I have specified the install location to be E:\Program Files\IBM\JazzTeamServer501
When it comes to context root I have chosen the Default Context Root as I have CLM 4.0.6 as lately installed version.
|
![]()
Another suggestion we have is to install 5.0.1 fresh on a new Windows Server 2012 Operating System , Get 4.0.6 data migrated over to 5.0.1.
In the above scenario we are thinking to remove the existing servers from the domain controller and have the new set of servers renamed with the original server name and join it back to the domain controller.
Here the public URI which all the application uses will be a concern. Also If we recall there are so many changes to be made from the application side.
let us know what is the best practice based on this suggestion.
|
![]()
What about the licensing option - I see that we need to get a new set of licenses for CLM 5.0.1.
As a starting point we would require 100 RRC users would require 66 licenses any suggestions ?
|
![]()
In addition, about upgrading from RM. (example for a distributed environment. AIX and Linux)
further to the copy of the JTS indexes for the index RM folder (/opt/IBM/<JazzTeamServer_4.0.6_InstallDir>/server/conf/jts/indices to /opt/IBM/<JazzTeamServer_5.0.1_InstallDir>/server/conf/rm/indices, do the following:
Note that the server/conf/rm folder, there is no teamserver.properties file. Copy the teamserver.properties file from JTS 4.0.6 version (/opt/IBM/<JazzTeamServer_406_InstallDir>/server/conf/jts) for /opt/IBM/<JazzTeamServer_4.0.6_InstallDir>/server/conf/rm folder and to /opt/IBM/<JazzTeamServer_5.0.1_InstallDir>/server/conf/rm. Edit the teamserver.properties file on /opt/IBM/<JazzTeamServer_4.0.6_InstallDir>/server/conf/rm and change the properties as follows: Entry: com.ibm.team.repository.db.jdbc.location Change: JTS by RM Entry: com.ibm.team.fulltext.indexLocation Change: jts by rm Save the file. Then from /opt/IBM/<JazzTeamServer_5.0.1_InstallDir>/server/ run the following commands: a) repotools-rm.sh -migration_rm_updateConfigurationFiles b) repotools-rm.sh -addTables c) repotools-rm.sh -finalizeApplicationMigration The finalizeApplicationMigration command will generate an output with the application ID and the public URL of RM. Note that data to use later. Clean the RM data in JTS server. Get in JTS machine: /opt/IBM/<JazzTeamServer_5.0.1_InstallDir>/server/ and run: repotools-jts.sh -finalizeApplicationMigration checkOauthDomain = true applicationId = RM-application-id = repositoryURL PUBLIC_RM_URL example: ./repotools-jts.sh -finalizeApplicationMigration checkOauthDomain = true applicationId = * = repositoryURL ** * -> Id generated by finalizeApplicationMigration ** -> URL generated by repositoryURL = PUBLIC_RM_URL run the repotools-rm.sh -reindex all |
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.