It's all about the answers!

Ask a question

Upgrading from CLM 4.0.3 to v5.0.2?

Ken Murphy (1033235) | asked Nov 06 '14, 4:41 p.m.
edited Nov 06 '14, 5:11 p.m. by Patrick Remington (2013)
Is it possible to upgrade directly from CLM v4.0.3 (CCM, QM, and RM) to v5.0.2?  Or, is it strongly recommended that one upgrade from v4.0.3 to v4.0.7 first?

2 answers

permanent link
Patrick Remington (2013) | answered Nov 06 '14, 5:11 p.m.
Upgrading from CLM 4.0.3 directly to CLM 5.0.2 should not be a problem.  The only problem comes if you are upgrading from CLM version 3.0.  See

Ken Murphy commented Nov 06 '14, 5:28 p.m.

Thanks for the tip, Patrick.  It'll certainly be more efficient to upgrade in one step.  Wasn't sure if any of the fixes in v4.0.7 were to address issues or workarounds with upgrading from v4.x to v5.x.  Again, thanks.

permanent link
Robin Bater (3.4k47) | answered Nov 07 '14, 11:01 a.m.
My teams have recently upgraded from V406 to V501, we did not see any problems but did take the opportunity to make some enterprise changes that you might want to consider at the same time.
  1. Added some new servers for the new reporting capabilities - Jazz Reporting Services and the Data Collection Component; including adopting some of the dashboard widgets
  2. Made some changes to the RTC server to improve performance
    1. increase the CPU power, from 2 to 4 CPU's.
    2. increase memory allocation to WAS instance, from 4 to 8 GB
    3. modify thread pools to allow processes to run smoothly.
  3. Increased the DB2 storage - so that we could maintain backups of the V406 environment for several weeks as well as improve overall performance
  4. Updated manually the web help UI on the server to the new knowledge center location
  5. Applied the CLM 5.0.1 iFix002 which has resolution for 24 field defects  (APARs):
    1. Jazz Foundation : 3 APARs
    2. Rational DOORS Next Generation (RDNG) : 10 APARs
    3. Rational Quality Manager (RQM) : 3  APARs
    4. Rational Team Concert  (RTC) : 8 APARs
  6. And finally some other things to maybe consider during an upgrade might be to archive old users, projects etc.

Kevin Ramer commented Nov 07 '14, 2:07 p.m.

2.3 -- WebSphere changes ?  could you be more precise.
6 -- Unless v5 has changed archiving doesn't free any resources in the databases

Robin Bater commented Nov 07 '14, 2:50 p.m. | edited Nov 07 '14, 3:32 p.m.

For WAS we upgraded the version, from v8.0.0.5 to v8.5.5 and then applied FP3.

This upgrade was performed for each separate server CCM, QM, RM, JTS, DM and RRDI

As well, increased the memory allocation for the CCM application from 4 Gbytes to 8 Gbytes. Also for the CCM application we increased the cpu's from 2 to 4 for that instance.

In regards to #6, this is mainly just to clean up the environment rather than any specific performance gain.

We also took the opportunity to upgrade DB2 from V9.7 to V10.5.

Your answer

Register or to post your answer.