Preparing the ClearQuest Synchronizer for renaming the Jazz Team Server

If you plan to rename the Jazz™ Team Server that the Rational® ClearQuest® Gateway connects to, you need to perform certain steps before and after the rename operation to ensure that the ClearQuest Synchronizer behaves as expected.

Risks and precautions

Renaming a server is a complex and potentially disruptive operation because it might be difficult or impossible to correct the stored links into the server from other applications and systems. It is supported only for a limited set of scenarios, requires careful advance planning, and should generally be used only as a last resort when other approaches are unworkable.

How renaming the server affects the ClearQuest Synchronizer environment

If you rename the server that the ClearQuest Synchronizer connects to:

  • The server rename operation updates URLs in work items for the new server URL; however the new URLs are not automatically synchronized with Rational ClearQuest records. You must force outgoing synchronization of work items to propagate the changes to ClearQuest. Depending on the number of work items that have been synchronized, the outgoing synchronization process can take a long time and might generate synchronization errors.
  • The URL links in ClearQuest record comments are not updated to reflect the updated work item URL links because ClearQuest does not support modifying existing comments. In those ClearQuest records, a comment is added stating that a server rename operation has occurred and that the previous comments might contain stale URL links.

Server rename scenarios

The server rename operation supports the following scenarios:
  • Preparing a test staging environment by using production data. If the ClearQuest Synchronizer is included in the production environment, then you must block access to the ClearQuest Gateway. Otherwise, a test Jazz Team Server might be connected to a production ClearQuest Gateway, which could cause test data to be synchronized out to the production environment. To block access to the ClearQuest Gateway, you edit the mapping file.
  • Moving a pilot deployment to full production. In this scenario, you probably want to continue to use the ClearQuest Gateway. Therefore, you do not need to edit the mapping file.
  • Production to production. In this scenario, you probably want to continue to use the ClearQuest Gateway. Therefore, you do not need to edit the mapping file.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki