It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×7,448
×2,348

question asked: Oct 06 '14, 12:09 p.m.
question was seen: 4,077 times
last updated: Dec 29 '14, 7:57 p.m.

Related questions

what are recommendations for upgrading CLM from 4.0.6 to 5.0.1

0
anoop mc (748●11●200●221) | asked Oct 06 '14, 12:09 p.m.
 Hi,

We plan to upgrade CLM from 4.0.6 to 5.0.1. 

  • Currently on our staging environment we have installed all the CLM 4.0.6 applications and SQL Server 2008 R2 DB. Configured and it works fine.

  • As 5.0.1 does not support SQL Server 2008 we have upgraded the database server to 2012.

  • As the next step, as per info center guide it says to install CLM 5.0.1 fully on to the server. Here I have a doubt - Before starting the CLM 5.0.1 installation using IM should we shutdown the existing CLM 4.0.6 applications.   

  • If we install the new CLM 5.0.1 does it affect the existing 4.0.6 instance. 



Accepted answer

1
permanent link
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

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Pradeep Basnet (60●1●13●20) | answered Oct 06 '14, 4:28 p.m.
While you install 5.0.1, you will get warning regarding existing package . Just ignore it.
1
permanent link
Arun K Sriramaiah (3.2k●2●36●77) | answered Oct 07 '14, 3:40 a.m.

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.

 http://www-01.ibm.com/support/knowledgecenter/SSCP65_5.0.1/com.ibm.jazz.install.doc/topics/roadmap_clm_upgrade.html?lang=en

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)


https://jazz.net/wiki/bin/view/Deployment/RM4to5MigrationTipsTricksProblemsAndSolutions

* High level Steps.

  • copy the jts database to a new database for rm

  • Run the rmUpdateConfigurationFiles repotools command to merge the existing configuration files

  • Run the -addTables command

  • Run the -finalizeApplicationMigration command to complete all necessary offline migration (on the rm server)

  • On the JTS server run the repotools-jts.bat -finalizeApplicationMigration (with specific arguments)

  • Update project associations with the -rmUpdateProjectBackLinksOnline command

  • Run the -reindex command. (This step is optional, but recommended

Regards,

Arun.

0
permanent link
anoop mc (748●11●200●221) | answered Oct 07 '14, 12:14 a.m.
 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.

0
permanent link
anoop mc (748●11●200●221) | answered Oct 07 '14, 1:04 a.m.
The next step I did is backed up all the existing databases.
In the upgrade guide it is told that - To use your RM data, you must copy your existing Jazz Team Server database.

Have copied the existing JTS and renamed to rm. About the logins it is not specified in the upgrade guide.

Earlier when we created a new database we created corresponding login names (jtsDBuser,ccmDBuser etc) for the copied and renamed rm database should we create a new login by name rmDBuser and map it to the Database.

or the existing jtsDBuser will only do ? 


Comments
anoop mc commented Oct 07 '14, 1:50 a.m.

 Look like we need to create a new rmDBuser with dbo to the copied rm database.


Having verified the upgrade scripts and rm_params which have the below line.

SQLSERVER //localhost:1433;databaseName=RM_DB;user=rmDBuser;password={password};

0
permanent link
anoop mc (748●11●200●221) | answered Oct 07 '14, 5:07 a.m.

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.

0
permanent link
anoop mc (748●11●200●221) | answered Oct 10 '14, 9:52 a.m.
 
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 ? 
0
permanent link
Leonardo Benevides (266●6●28) | answered Dec 29 '14, 7:52 p.m.
edited Dec 29 '14, 7:57 p.m.
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

Register or 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.