Lifecycle Query Engine doesn't start after data migration

After you upgrade and migrate the data, you might encounter an error when you try to start the Lifecycle Query Engine . The issue occurs because the lqe.key file was deleted or moved. This file stores the key for decrypting sensitive data that was migrated.

Problem

When the new version of Lifecycle Query Engine 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 Lifecycle Query Engine and Link Index Provider passwords and credentials. Lifecycle Query Engine automatically migrates internal data to the new version. Sensitive information is encrypted with the new key from the lqe.key file. When you start Lifecycle Query Engine, the lqe.key file is used to decrypt the data.

If you delete the lqe.key file, or if you move the JTS_install_dir/server/conf/lqe directory without moving the lqe.key file, Lifecycle Query Engine doesn't find the file at startup, and generates a new lqe.key file. LQE tries to decrypt the data with this new key. You get an error because the data was encrypted with a different key (from the original lqe.key file).

Solution

To resolve this problem:
  1. Shut down Lifecycle Query Engine.
  2. Find the JTS_install_dir/server/conf/lqe directory that was used when you started your previous Lifecycle Query Engine version for the first time.
  3. Copy the lqe.key and dbconnection.properties files from that directory to the current JTS_install_dir/server/conf/lqe directory.
  4. Start Lifecycle Query Engine.