Moving the IBM Engineering Lifecycle Management databases to a different database server

This topic provides instructions for re-configuring your Engineering Lifecycle Management deployment when the database server moves to new hardware.

Before you begin

Ensure that you have changed the context root. For more information, see Changing the context root

About this task

You might need to move your Engineering Lifecycle Management databases in the following scenarios.
  • When moving a pilot deployment to production, if the database server being used in the pilot deployment is different from the server that will be used in production.
  • When a staging environment is being set up that uses its own database server and a copy of the production data.

Procedure

  1. Back up the old database.
  2. Use database vendor-specific tools to migrate the data from the old database to the new database.
    Important: z/OS operating system icon Db2 database icon For IBM Db2® for z/OS, follow the unload and load instructions in Running UNLOAD and LOAD processes on Db2 to create a backup database.
  3. For the Jazz® Team Server, CCM, RM, QM, Global Configuration Management, Data Collection Component, and IBM Engineering Lifecycle Optimization Engineering Insights databases, update the following properties in the server/conf/applicationName/teamserver.properties file to point to the new Engineering Lifecycle Management database location.
    • com.ibm.team.repository.db.vendor
    • com.ibm.team.repository.db.jdbc.location
    • com.ibm.team.repository.db.jdbc.password
  4. For the Lifecycle Query Engine and Link Index Provider databases, update the following properties in the server/conf/lqe/dbconnection.properties file for LQE and the server/conf/ldx/dbconnection.properties file for LDX to point to the new Engineering Lifecycle Management database location.
    • db.vendor
    • db.location
    • db.password
  5. For the Jazz Team Server, CCM, RM, QM, Data Collection Component, and IBM Engineering Lifecycle Optimization Engineering Insights databases, update the following properties in the server/conf/applicationName/teamserver.properties file to point to the new data warehouse database location.
    • com.ibm.team.datawarehouse.db.jdbc.vendor
    • com.ibm.team.datawarehouse.db.jdbc.location
    • com.ibm.team.datawarehouse.db.jdbc.password
    • com.ibm.team.datawarehouse.db.base.folder
  6. For the Jazz Team Server, CCM, RM, QM, Global Configuration Management, Data Collection Component, IBM Engineering Lifecycle Optimization Engineering Insights, and Report Builder databases, run repotools-applicationName -verify to ensure that the new Engineering Lifecycle Management database connection is successful.

What to do next

Proceed with changing the database to a different database vendor. For more information, see Changing the IBM Engineering Lifecycle Management databases to a different database vendor.