Clarity Upgrade path: Best practices for old versions
search cancel

Clarity Upgrade path: Best practices for old versions


Article ID: 216747


Updated On:


Clarity PPM On Premise Clarity PPM SaaS


Trying to upgrade from an old version and need to determine the best supported upgrade path, what would be the recommendations?


Release : Any


  • Broadcom Support recommends to always keep up with the current versions, so you do not have to stay on unsupported versions and then do upgrade through 6-7 versions at once
  • If you have to upgrade from an old version, make sure you are on the same Java version. Being on the same Java versions avoids known upgrade issues with install with multiple Java versions. 
    • 13.x, 14.x
      • If you have Release 13.3, 14.1, or 14.2, you can upgrade to Release 15.4 or 15.4.1 first, and then install 15.5.
      • To upgrade from 13.2 and earlier releases, upgrade to 14.3 first, then 15.4.1 and 15.5.
    • 15.x
      • If upgrading from 15.5 or older (JDK 8), upgrade to 15.5 first.
      • Then upgrade 15.5 > 15.6.1 (JDK 11)
      • Then do 15.6.1> 15.7.1 (OpenJDK 11) and you can use the direct upgrades to current releases starting 15.7.1.
      • 15.7.1>15.9.2 (OpenJDK 11, latest versions with securability fixes)

      • If you are on 15.4.1 going to 15.9.2, do a step upgrade: 15.4.1> 15.5> 15.6.1> 15.7.1> 15.9.2
      • If you are on a release in between, i.e. 15.5.1, then just follow the next steps: 15.5.1> 15.6.1> 15.7.1> 15.9.2
    • 16.x  
      • If you want to go from 15.9.2 to 16.x do 15.9.2 > 16.0.1 > 16.0.3  >16.1.3
      • From 16.0.0: 16.0.0 > 16.0.3 > 16.1.3> 16.2.1
      • Going from 16.0.1 to 16.1.3? Do 16.0.1 > 16.0.3 > 16.1.3


  • You have to download the install files for each version from the Support site.
  • The timing of the upgrade is not affected as each version would have to be applied anyway.
  • You do not have to bring up the application between the upgrade steps. You should just remove services and start the next step. Testing in between "hops" is not recommended
  • You can use the time between the steps to take a fresh database backup. This will help in case you hit an error, then you will not have to rollback all the way down to the initial version
  • We recommend doing backup of the database every time you complete a "hop". This way if you face an error you will not have to rollback all the way

Additional Information