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, and IBM Engineering Lifecycle Optimization - Engineering Insights databases:
Changing the IBM Engineering Lifecycle Management databases to a different database vendor for LQE and LDX
Procedure
- Perform an LQE backup. See Backing up and restoring Lifecycle Query Engine.
- 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.
- Perform an LQE restore. See Backing up and restoring Lifecycle Query Engine.
- Do the same for LDX.