Migrating Lifecycle Query Engine

The process for migrating from previous versions of Lifecycle Query Engine (LQE) to the current release happens automatically. When you update the WAR file and start the server, LQE determines whether or not migration is required; if it is, migration begins.

When you migrate from a previous version of LQE, you are actually converting the index, the relational database, and the properties files so that they work with the new version.

  • Use the TRS 2.0 data source instead of TRS 1.0 for improved efficiency and performance.
  • If you migrate your data to the current version, you must reindex Rational® Team Concert® process and work item data sources.
Important: When LQE starts for the first time after upgrading, the lqe.key file is created in the JTS_install_dir/server/conf/lqe directory. This file stores the key for encrypting LQE and Link Index Provider (LDX) passwords and credentials. LQE automatically migrates internal data to the current version. Sensitive information is encrypted with the new key from the lqe.key file. When you start LQE, the lqe.key file is used to decrypt the data. If you delete this file, or if you move the JTS_install_dir/server/conf/lqe directory without moving lqe.key, you get an error when you start LQE. To learn how to resolve the issue, read this troubleshooting article.

Migrating to the current Lifecycle Query Engine release in single node environments

About this task

In single node environments where you are using LQE with Apache Derby, it is easy to migrate to the current release.


  1. Back up the existing version of LQE. See Backing up and restoring Lifecycle Query Engine and Link Index Provider (LDX).
  2. Shut down all the servers.
  3. Install LQE.
  4. Start LQE.