This release of the ClearQuest® Connector contains
several limitations and known problems.
This release contains the following limitations and known problems:
- To use the ClearQuest Connector,
you must be running IBM® Rational® ClearQuest 7.0.1
or higher.
- The ClearQuest Connector
Setup Wizard runs on Windows® only.
If you are deploying the ClearQuest Connector
on Linux®, you can run the ClearQuest Connector Setup
Wizard on Windows. The wizard
generates the cqconnector.properties file, which the Gateway uses.
You can copy the generated properties file to a Linux computer, edit it, and then start the
Gateway on that computer.
- In the Jazz™ Server Configuration
part of the ClearQuest Connector
Setup Wizard, the Create New Account option
fails if the Jazz user registry
is read-only, which is true if the Jazz Team Server is
running on a WebSphere® Application
Server or is configured to use Lightweight Directory Access Protocol
(LDAP).
- When synchronizing work item comments with ClearQuest defect notes, the following
limitations apply:
- The timestamp on the note is the time it was synchronized, not
the time that the comment was created.
- The user name associated with the note is that of the ClearQuest Connector user
account, not the user who created the comment.
- Because additions to notes and comments are appended to the existing
entries, and cannot be interleaved, the order of entries is the order
in which they are synchronized, not the order in which they are created.
- When mapping state values between a ClearQuest record type and a Rational Team Concert™ item,
you cannot map the transition from a ClearQuest Closed state to an Opened state.
- A Jazz repository can
contain character data for multiple national languages because it
stores the data in Unicode format, but a ClearQuest user database can hold data
for only one character set at any time. If the character set for the ClearQuest user database
does not support the character data in work items, synchronization
operations fail with errors such as, "The field "Description" contains
characters that are not supported by the data code page, "1252 (MS Windows Latin 1)"."
- In a ClearQuest user
database, the UnDuplicate action changes the state of the record to
its state prior to the Duplicate action. In some cases, the Rational Team Concert work
item cannot make the same state transition because its state transition
model does not support it.
- When you define keywords in ClearQuest record
types that are synchronized with Rational Team Concert items,
use lowercase and do not include spaces.
- Although a ClearQuest record
can have multiple attachments list fields, a Rational Team Concert item
can have only one.
- Do not add a mapping for the Description property to an attachment
synchronization rule; it is not supported and causes synchronization
to fail with the error, "Invalid Attachment property name: Description."
- Synchronization fails in some circumstances if you add an attachment
to a work item while using the Rational Team Concert Web
interface in a Microsoft® Internet
Explorer browser, and the attached file is on a remote computer. To
work around this problem, remove the attachment, copy it to the local
computer, and then reattach it to the work item. Alternatively, you
can leave the attached file on the remote computer and reattach it
while using a different browser.
- If you use the ClearQuest Connector
with a DB2® user database and
schema repository, you might encounter database deadlocks in certain
circumstances. To avoid this problem, set the DB2 MAXAPPLS parameter to 200 for the user database
and the schema repository.
- When specifying the Jazz server
Uniform Resource Identifier (URI) with the com.ibm.team.uris parameter
in the cqconnector.properties file, do not include nonstandard URL
characters, such as the @ character, in the user name or password
parts. In place of a nonstandard URL character, use the appropriate
escape characters. For example, use %40 for the @ character.
- If you use the ClearQuest Connector in
a nonASCII environment, you must use Unicode escape characters for
any nonASCII characters in the cqconnector.properties file. A Java™ utility, native2ascii, converts
characters in other formats to Unicode escape format.
- In a text editor that supports UTF-8 encoding, such as Notepad,
create and save a file that contains the nonASCII characters from
the cqconnector.properties file.
- On a computer running Windows,
open a DOS Command Prompt console and navigate to the Java-installation-directory/bin
directory.
- Enter native2ascii.exe –encoding source-file to-be-generated-unicode-escape-file where source-file is
the file that you created in Step 1.
- Open the generated file and copy the Unicode escape characters.
Open the cqconnector.properties file. Paste the Unicode escape characters
into the cqconnector.properties file where needed. Save the modified
cqconnector.properties file.
- When you apply the JazzInterop package to a schema, you select
the record type or types to which to apply the package. If you decide
later that you want to apply the package to one of the stateful record
types that you did not select when you first applied the package,
you can do so. However, if the default scripting language for the
schema is Visual Basic, you cannot apply the package to a stateless
record type that you did not select when your first applied the package
to the schema.
- The server.shutdown script in the install-directory/gateway
directory fails to shut down the ClearQuest Gateway.
On Windows, click the Close icon
(X) in the Tomcat console window. On Linux,
enter the command kill -9 process-ID.
- The ClearQuest Import Wizard in Rational Team Concert 2.0
and 2.0.0.1 is not compatible with ClearQuest 7.1.1. To use the wizard
with ClearQuest 7.1.1, upgrade to Rational Team Concert 2.0.0.2.
- In schemas based on versions of the JazzInterop package earlier
than version 1.07, problems occur if records contain attachment files
that include the ampersand sign (&) in their names. This problem
has been fixed in JazzInterop 1.07. See Upgrading the user database with a new version of the JazzInterop package for details about
upgrading a schema and user database to a new version of JazzInterop.