You are not logged in. Click here to log in.

codebeamer Application Lifecycle Management (ALM)

Search In Project

Search inClear

Tags:  not added yet

Upgrading from older versions - simple

This document describes how to upgrade to codebeamer 9.x from older codebeamer 8.x releases running with MySQL or Oracle.

For tested upgrade paths, see: Upgrading codebeamer

This method cannot be used for any older codebeamer versions.

To control the whole upgrade process, use this upgrade guide: Upgrading from older versions - advanced - before 21.09 (Emma)

Only MySQL 5.7 and Oracle 19 are supported. Upgrade your MySql/Oracle instance before upgrading your codebeamer instance.To upgrade to newer version than 21.09 (Emma), first upgrading to Emma is required.

The old codebeamer installation will be referred as OLD-CB, the new one as NEW-CB throughout this document.

  1. It is imperative that you make a backup of your codebeamer and codebeamer database before you upgrade.
  2. During the installation codebeamer must be stopped. Ensure all java/javaw processes are stopped, otherwise you might end up losing data.

The upgrade procedure transfers your installation instance data from the old version to the new version. Migration from the new version back to the old version is NOT supported.

When you upgrade mysql to a newer version, do not forget to do the followings:
  • run the following command: "mysql_upgrade -u root -p --force"
  • restart mysqld

You can find more information on this webpage:

Step 1. Install NEW-CB

Install NEW-CB into a new directory (the installation must not be executed into an existing directory) and do not start the CB server at the end of the installation.

Step 2. Start upgrade script





Go through upgrade steps.

In case of error, fix the problem and start the whole process again. (Reinstall new codebeamer)

Step 3. Get a new license

Check the appropriate Release-Notes whether a new license is required.

Read the Getting Licenses section in codeBeamer Licensing.

You need to have that license at hand before you continue with the next steps.

Also consider that you can only request licenses from Intland Software from Monday through Friday, 8:00 - 17:00 GMT+2, and that processing a license request may take hours up to several days!

So do not shut down your live production system or schedule to upgrade overnight or during the weekend until you already have a license for the new system.

To install the new license:

  1. Log in to codebeamer with System Admin and open System Admin ► License page.
  2. Click on the [Edit License] button and insert the new License.
  3. Once done, click on [Save].

Step 4. Runtime Parameters

If you had customized OLD-CB runtime variables, e.g. special JVM, HEAPSIZE, etc., then you should copy these settings from the OLD_CB start script to the NEW-CB start script.

Operating System Path Script
Unix/Linux/Mac OS X ~/NEW-CB/bin cb
Windows (No Service) ~/NEW-CB/bin cb.bat
Windows (Service) ~/NEW-CB/tomcat/bin cbservice.bat

For changes in ~/NEW-CB/tomcat/bin/cbservice.bat to take effect, you must run the following command manually afterwards

cbservice codebeamer codebeamer

Step 5. Start

Start the NEW-CB server. The first time the codebeamer server is started, the database schema will be upgraded to version NEW-CB.
Depending on which version you're upgrading from, and the amount of data in your database, the first startup of the NEW-CB server might take up to 10-120 min, because the database scheme will be updated in the background (the database process might use a lot of CPU).

Do not shutdown or kill the NEW-CB server as long as the database upgrade is in progress, otherwise the database might be corrupted.

Step 6. Clearing Browser Caches

Since browsers cache javascript files, the cached javascript files must be re-loaded. We strongly recommend clearing the browsers' cache and then re-starting the browser.

Step 7. Starting Re-indexing

  1. After upgrading, the index database is empty, thus searching will not return any match.
  2. Perform a re-indexing of artifacts by going to System Admin ► Indexing ► click on [YES, drop file cache and re-index!]
Note: during the re-indexing process, the search result may not contain all matches, so it is recommended to perform out of business hours.

Step 8. Validate logs

Check that ~/NEW-CB/tomcat/logs/errors.txt does not contains any error. In case of errors, create a bug ticket on with the attached log files (cb.txt / errors.txt)

Step 9. Git http-backend verification ( Optional, for Windows- based installation )

Go to System Admin ► Application Configuration and verify and update the "http-backend" key in "git" section:

"git" : {
      "http-backend" : "C:\\NEW_CB_\\libexec\\git\\mingw64\\libexec\\git-core\\git-http-backend.exe",