This topic provides instructions for re-configuring your
deployment when the database server moves to new hardware.
About this task
You may need to move your 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, RELM, and LQE databases, update the following properties in
the server/conf/applicationName/teamserver.properties file
to point to the new Rational® Engineering
Lifecycle Manager database location.
- com.ibm.team.repository.db.vendor
- com.ibm.team.repository.db.jdbc.location
- com.ibm.team.repository.db.jdbc.password
- For the Jazz Team
Server, RELM, and LQE 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, RELM, and LQE databases, run repotools-applicationName
-verify to ensure that the new Rational Engineering Lifecycle
Manager database
connection is successful.