Changing the IBM Engineering Lifecycle Management (ELM) databases to a different database vendor

This topic provides instructions for re-configuring your IBM® Engineering Lifecycle Management (ELM) deployment when the database vendor changes.

About this task

You need to change your ELM 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 ELM databases to a different database vendor for the Jazz™ Team Server, CCM, RM, QM, Data Collection Component, Global Configuration Management, IBM Engineering Lifecycle Optimization - Engineering Insights, and Report Builder databases:

  1. In the application, run repotools-<applicationName> -export toFile=export.tar to export the data from the old database, where <applicationName> is jts, ccm, am, rm, qm, gc, dcc, or relm.

  2. Copy the tar file from the old ELM server to the new ELM server if they reside on separate systems.
  3. In the application, 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. In the application, run repotools-<applicationName> -import fromFile=export.tar to import the data in the new database, where <applicationName> is jts, ccm, am, rm, qm, gc, dcc, or relm.
  5. In the application, run repotools-<applicationName> -verify to ensure that the new database connection is successful, where <applicationName> is jts, ccm, am, rm, qm, gc, dcc, or relm.
  6. For the data warehouse database, rebuild the database on the new database platform.

Changing the IBM Engineering Lifecycle Management databases to a different database vendor for LQE and LDX

Procedure

  1. Perform an LQE backup. See Backing up and restoring Lifecycle Query Engine.
  2. Shut down LQE, set up the new vendor database, and change the dbconnection.properties values to point to the new vendor. See Setting up the database.
  3. Perform an LQE restore. See Backing up and restoring Lifecycle Query Engine.
  4. Do the same for LDX.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki