Changing the Rational solution for Collaborative Lifecycle Management databases to a different database vendor

This topic provides instructions for re-configuring your CLM deployment when the database vendor changes.

About this task

You need to change your CLM databases if you are using a different vendor in production deployment than the one used in the pilot deployment. For example, a small pilot deployment using Derby is being moved into production using Db2®.

Procedure

To change the CLM databases to a different database vendor for the Jazz® Team Server, CCM, RM, QM, Data Collection Component, Global Configuration Management, Rational® Engineering Lifecycle Manager, and Report Builder databases:

  1. For the Jazz Team Server, CCM, RM, QM, Data Collection Component, Global Configuration Management, Rational Engineering Lifecycle Manager, and Report Builder databases, run repotools-applicationName -export toFile=export.tar to export the data from the old database.
  2. Copy the tar file from the old CLM server to the new CLM server if they reside on separate systems.
  3. For the Jazz Team Server, CCM, RM, QM, Data Collection Component , Global Configuration Management, Rational Engineering Lifecycle Manager, and Report Builder databases, update the following properties in the server/conf/applicationName/teamserver.properties file to point to the new location.
    • com.ibm.team.repository.db.vendor
    • com.ibm.team.repository.db.jdbc.location
    • com.ibm.team.repository.db.jdbc.password
  4. For the Jazz Team Server, CCM, RM, QM, Data Collection Component, Global Configuration Management, Rational Engineering Lifecycle Manager, and Report Builder databases, run repotools-applicationName -import fromFile=export.tar to import the data in the new database.
  5. For the Jazz Team Server, CCM, RM, QM, Data Collection Component, Global Configuration Management, Rational Engineering Lifecycle Manager, and Report Builder databases, run repotools-applicationName -verify to ensure that the new database connection is successful.
  6. For the data warehouse database, rebuild the database on the new database platform.