This topic provides instructions for re-configuring your ELM
deployment when the database server moves to new hardware.
About this task
You might need to move your
ELM
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
- Back up the old database.
- Use database vendor-specific tools to migrate the data
from the old database to the new database.
-
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
ELM
database location.
- com.ibm.team.repository.db.vendor
- com.ibm.team.repository.db.jdbc.location
- com.ibm.team.repository.db.jdbc.password
-
For the Lifecycle Query Engine (LQE) and Link Index Provider (LDX) 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 ELM database
location.
- db.vendor
- db.location
- db.password
-
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
-
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
ELM
database connection is successful.