Server rename for Lifecycle Query Engine and Link Index Provider with relational store

For renaming server for Lifecycle Query Engine and Link Index Provider with relational store set-up, you don’t need to unregister Lifecycle Query Engine or Link Index Provider here.

During server rename

About this task

During server rename, Lifecycle Query Engine or Link Index Provider also renames data sources and sends success status to Jazz® Team Server. The following instructions work for Lifecycle Query Engine with relational store setup. Unlike for server rename for Lifecycle Query Engine and LDX without relational store, you don’t need to unregister Lifecycle Query Engine/Link Index Provider.

Procedure

After the mapping file is generated, copy the file in to Jazz Team Server setup directory that is server/lqe/conf and server/ldx/conf. This needs to be done before you run URL import command.
On the Data Provider window, click Pause All to pause the indexing in Lifecycle Query Engine and Link Index Provider before you stop the Jazz Team Server server and run URL import command.

Note: When you restart Jazz Team Server after the URL import command, Lifecycle Query Engine/Link Index Provider also gets restarted as part of Jazz Team Server restart. During this restart it renames impacted data providers in different databases. Hence, to hold the processing of events at this time, the indexing is paused for all data sources.
If Lifecycle Query Engine and Link Index Provider are running on different server, copy mappings.txt file on the server in lqe/conf directory before you run URL import command.
If Lifecycle Query Engine and Link Index Provider are running on different server, you can trigger URL import command. After URL import, start Lifecycle Query Engine/Link Index Provider first and then start Jazz Team Server.

After server rename

After the server rename is successfully completed, delete mapping file from server/lqe/conf/ and server/ldx/conf/ directories.