Integrating Rational ClearQuest with other products

You can integrate Rational® ClearQuest® with other software by adding various Rational ClearQuest packages to existing schemas.

Some Rational ClearQuest integrations are independent integrations that require adding only the appropriate package. Other integrations are dependent integrations that require adding one or more packages in a specific order and may also require additional configurations to Rational ClearQuest.

It is important to note that not all ClearQuest integrations can be applied to the Web Client; therefore, fields, forms, reports, scripts and other functionality added to the Rational ClearQuest Client for Windows® or the UNIX® system and Linux® by an integration package may not be available through the Web Client. Examples of integrations that do not work with the Web client include UCM and Requisite® Pro.

Note: These instructions assume that you are adding a new integration and that the necessary packages do not already exist in your schema. If you need to upgrade an integration or package, see the topic Applying package upgrades. Before you add new integrations to your schema, you should find out which packages are already in the schema.
Warning: Be sure to plan carefully before adding packages. After you add a package to a schema, you cannot remove the package. You must delete all schema versions in which the package exists. You can delete schema versions only if you have not applied them to a user database.

Independent integrations

The following integrations are independent integrations. Note that you can use the same installation process for all independent integrations. For more information on independent integrations, see Adding independent integrations .

Dependent integrations

The following integrations are dependent integrations. For more information about dependent integrations, see Adding independent integrations .

ClearQuest integrations and code pages

Because all data in a ClearQuest database must be from the same code page, there are several things you need to keep in mind with ClearQuest integrations:

Example

The following example shows how a code page mismatch can prevent an integration between ClearQuest and Rational Administrator from functioning correctly.

Rational ClearQuest is installed on a machine with the 1252 operating system code page and the ClearQuest data code page value for the database set is also 1252.

The Rational Administrator client is installed on a machine with the 936 (Japanese) operating system code page.

A user creates a Rational Administrator project, and because she is working on a machine with a 936 code page, the project name includes Japanese characters. She then attempts to associate the new Rational Administrator project with a ClearQuest database. The attempt fails because the Japanese characters in the Rational Administrator project name are not from the 1252 code page, which is the data code page value of the ClearQuest database set.

Enabling record types for integrations

Some packages enable existing record types in a schema. At the time you install such packages, you have the option of selecting which record types you want to be enabled by the package. If you add a new record type after adding the package, you can also enable the new record type with the package functionality.

For a list of packages and the record types they modify, see ClearQuest integration packages .

To enable package functionality for a new record type:

  1. In Rational ClearQuest Designer, click File > Open Schema and select a schema to open.
  2. With the schema open, click Package > Setup Record Types for Package.
  3. In the Setup Record Types for Package window, select a record type from the Record Types list.
  4. In the Available Packages list, check the packages that you want to enable the record type.
Related concepts
Rational ClearQuest integration packages
Related information
Overview of packages and integrations
Rational ClearQuest packages

Feedback