r13 - 2015-08-20 - 22:04:38 - Main.atiacoboYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > IntegrationsTroubleshooting > IntegrationsTroubleshootingJazzandClearQuest

community-img.gif Troubleshooting Jazz product integrations with ClearQuest

Authors: IntegrationsTroubleshootingTeam
Build basis: The Rational solution for Collaborative Lifecycle Management (CLM) 4.x

This page provides resources for troubleshooting Jazz product integrations with IBM Rational ClearQuest.

  • Rational ClearQuest Synchronizer: Through synchronization operations, the ClearQuest Synchronizer maps ClearQuest records, such as defects, to Jazz work items. When a user creates or modifies a ClearQuest record, the ClearQuest Synchronizer creates or modifies a corresponding work item. The creation and modification changes also flow from work items to ClearQuest records. A ClearQuest Synchronizer has to be installed.

  • Rational ClearQuest Importer: You can use the ClearQuest Import Wizard to import records from a ClearQuest user database into a project area. The imported records are stored as work items in the Jazz repository. The new work items are not synchronized or linked with the ClearQuest records upon which they are based. No configuration or extra installation is needed.

The troubleshooting situations on this page are divided into two groups: situations that administrators are likely to encounter, and situations that users are likely to encounter.

User situations

ClearQuest Bridge

ClearQuest Importer

Administrator situations

ClearQuest Bridge

ClearQuest Synchronizer

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r13 < r12 < r11 < r10 < r9 | More topic actions
Deployment.IntegrationsTroubleshootingJazzandClearQuest moved from Deployment.IntegrationsTroubleshootingJazzProductIntegrations on 2013-10-21 - 16:21 by Main.dmmckinn -
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.