Upgrading from CLM 4.0.2/DB2 9.7 to CLM 5.0.2/DB2 10.5

Have you had the opportunity to do an upgrade certainly of a Jazz platform? I did several of them these last years and generally I had to either upgrade the database or migrate the application server and it worked pretty smoothly…

For this one, we have to go thru 2 migrations and 1 upgrade. Actually, CLM 4.x supports DB2 9.7, CLM 5.0 does not and CLM 5.0 supports DB2 10.5. CLM 4.x does not. So we have to upgrade first against an intermediate version of DB2 (10.1) supported by both CLMs to be able to do the full migration.

So this upgrade will run in 3 main steps:

  1. Migrate your CLM 4.0.6 from DB 9.7 to DB2 10.1
  2. Upgrade your CLM 4.0.6/DB2 10.1 to CLM 5.0.2/DB2 10.1
  3. Migrate your CLM 5.0.2/DB2 10.1 to CLM 5.0.2/DB2 10.5

Migrate your CLM 4.0.6 from DB 9.7 to DB2 10.1

  1. Export your different databases: JTS, CCM, QM as TAR files using the corresponding repotools that you should retrieve in the associated installation directory:
    JTS_dir/server repotools-jts -export toFile=JTSData.tar
    CCM_dir/server repotools-ccm -export toFile=CCMData.tar
    QM_dir/server repotools-qm -export toFile=QMData.tar
  2. Uninstall your current instance of DB2 9.7
  3. Uninstall your current CLM 4.0.6 instance
  4. Install a new instance of DB2 10.1
  5. Install a new instance of the CLM 4.0.6
  6. Run the Setup wizard to connect this CLM 4.0.6 against DB2 10.1
SnapShot At this point, if your are running a VM, you should create a Snapshot titled, e.g., “SS1: Clean CLM406 on DB2 10.1
  1. Import TAR files, you before exported, to refill your databases, this time, against DB2 10.1
    JTS_dir/server repotools-jts -import fromFile=JTSData.tar
    CCM_dir/server repotools-ccm -import fromFile=CCMData.tar
    QM_dir/server repotools-qm -import fromFile=QMData.tar
  2. Start the Jazz Team Server
    • If you get an error with your consumer key configuration,
      • Replace the files JTS_dir/server/conf/admin/friends.rdf and JTS_dir/server/conf/rm/friendsconfig.rdf from the new instance of CLM 4.0.6 by the ones in the first CLM 4.0.6 instance. It should fix your problem.
    • Restart the server.
SnapShot At this point, if you are running a VM, you should create a Snapshot titled, e.g., “SS2: CLM406 on DB2 10.1 with DATA
  1. If you have an LDAP setup, log into https://hostname.example.com:9443/jts/setup
  2. Set the User Registry to Tomcat User Database
    • It will create a user with the same login and password as the one you used to connect thru your LDAP as an ADMIN.
  3. Shutdown the CLM 4.0.6 server

Upgrade your CLM 4.0.6/DB2_10.1 to CLM 5.0.2/DB2_10.1

  1. Install the CLM 5.0.2 applications, including the trial license keys
  2. Start the CLM 5.0.2 server to deploy the applications but do not run the setup wizard after the installation.
  3. Shutdown the CLM 5.0.2 server
SnapShot At this point, if your are running a VM, you should create a Snapshot titled, e.g., “SS3: CLM406 on DB2 10.1 with DATA and clean CLM502
  1. Copy your current JTS database into a new RM database (The backup directory that you use in the command must exist):
    • db2 backup database JTS to C:\DB2_backup
    • db2 restore database JTS from C:\DB2_backup into RM
  2. Upgrade the Jazz Team Server
    • Go to the JTS_5.0.2_install_dir\server directory and run:
      • upgrade\jts\jts_upgrade.bat -oldJTSHome C:\Progra~1\IBM\JazzTeamServer406\server\conf
  3. Upgrade the Change and Configuration Management application
    • Go to the CCM_5.0.2_install_dir\server directory and run
      • upgrade\ccm\ccm_upgrade.bat -oldApplicationHome C:\Progra~1\IBM\JazzTeamServer406\server\conf
  4. Upgrade the Quality Management application
    • The Help suggests to run to run statistics to update the database tables before you start the Quality Management application upgrade. I didn’t have to do it because I don’t really use QM for now…
    • Go to the QM_5.0.2_install_dir\server directory and run
      • upgrade\qm\qm_upgrade.bat -oldApplicationHome C:\Progra~1\IBM\JazzTeamServer406\server\conf
  5. Upgrade the Requirements Management application
    • Go to the RM_5.0.2_install_dir\server directory and run
      • upgrade\rm\rm_upgrade.bat -oldApplicationHome C:\Progra~1\IBM\JazzTeamServer406\server\conf -newJTSHome C:\Progra~1\IBM\JazzTeamServer502\server\conf
  6. Restart the server
  7. Add the licenses for 5.0
SnapShot At this point, if your are running a VM, you should create a Snapshot titled, e.g., “SS4: CLM502 on DB2 10.1 with DATA+Licenses
  1. Update project associations
    • The upgrade process suggests to apply this step. I tried a couple of times and it breaks my config. I can’t tell you if it comes from the fact that I don’t have any RM project instantiated in my repository. So I skipped this step.
    • Go to the RM_5.0.2_install_dir\server directory and run
      • repotools-rm.bat -rmUpdateProjectBacklinksOnline adminUserId=admin_user_id adminPassword=admin_password repositoryURL=RM_repository_URL

Migrate your CLM 5.0.2/DB2_10.1 to CLM 5.0.2/DB2_10.5

  1. Export JTS, CCM, QM, RM to TAR
    • JTS_install_dir/server repotools-jts -export toFile=JTSData.tar
    • CCM_install_dir/server repotools-ccm -export toFile=CCMData.tar
    • QM_install_dir/server repotools-qm -export toFile=QMData.tar
    • RM_install_dir/server repotools-rm -export toFile=RMData.tar
  2. Install DB2 10.5
  3. Install a new instance of the CLM 5.0.2
  4. Run the Setup wizard to setup this CLM against DB2 10.5
SnapShot At this point, if your are running a VM, you should create a Snapshot titled, e.g., “SS5: Clean CLM502 on DB2 10.5″
  1. Stop the Server
  2. Import TAR files
    • JTS_install_dir/server repotools-jts -import fromFile=JTSData.tar
    • CCM_install_dir/server repotools-ccm -import fromFile=CCMData.tar
    • QM_install_dir/server repotools-qm -import fromFile=QMData.tar
    • RM_install_dir/server repotools-rm -import fromFile=RMData.tar
  3. Restart the Server

You should be all set.

This article was sitting as a draft for few some months in my blog so it is targeting a migration to CLM502. The current version of the CLM is the 6.0 so you might find some minor changes between both versions. Sorry about that.

Nevertheless, you should have the general idea correctly explained.

Feel free to comment if you find any major difference between both versions, I will appreciate as well as any other ready.

I hope it will help.

Advertisements

4 thoughts on “Upgrading from CLM 4.0.2/DB2 9.7 to CLM 5.0.2/DB2 10.5

  1. Thanks for the post!
    For the last step, can’t you perform an in situ DB2 migration of 10.1->10.5? Just get DB2 to migrate the databases?

    • Hi Chris,
      Thanks for your interest.
      I’m not sure that I understand what you mean by “in situ DB2 migration of 10.1->10.5”. Can you clarify?
      As you saw, in my case I used the usual export / import Database process which worked great.
      I understand that in some cases, when the DB is too big, it could be tough to do it but it weoks pretty well.
      Now you can also checkout what the jazz help in suggesting: Upgrade to DB2 Version 10.5.
      I hope it will help.

  2. Hi Philippe,
    What I meant was, to perform a DB2 10.1 -> 10.5 update, have have DB2 migrate the existing database (as a DB2 upgrade exercise), rather than import/export and install a new RTC instance. Just update and migrate DB2 under RTC’s nose, as it were. 🙂
    -Chris

  3. Hi Chris,

    I used DB2 to upgrade the database even when I upgrade from V9.7 to V10.1 on a CLM 4.0.3 instance. It worked out great!

    I did not use any of the Jazz repotools to export and import data.

    Spencer

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s