Rational ClearQuest integrations and data code pages

Integrations of Rational® ClearQuest® with a number of other applications are available. If the other application can pass and receive Unicode data, all data passed from Rational ClearQuest is transferred correctly regardless of the local character set or language setting on the client that runs the integration. Rational ClearQuest always verifies that data passed to one of its applications can be stored correctly in the database set.

If the other application is not fully Unicode compliant, its data is considered to be in Local mode. In this case, Rational ClearQuest just attempts to convert data to the code page that corresponds to the client's local character set; if it cannot perform the conversion, it returns an error to indicate that it is unable to write the data back to the integration correctly.

Existing integrations use the Unicode compatibility modes in the table below.

Table 1. Integration compatibility modes
Integration Mode
Mainframe (SCLM) RETURN_STRING_LOCAL
IBM Rational ClearCase (Base) RETURN_STRING_LOCAL
IBM Rational ClearCase (UCM) RETURN_STRING_LOCAL
IBM PurifyPlus RETURN_STRING_LOCAL
IBM Rational Requisite Pro RETURN_STRING_LOCAL
TestManager/Rational Administrator (2003.06.xx and earlier versions) RETURN_STRING_LOCAL
Rational ClearQuest Test Manager (Version 7.0) RETURN_STRING_UNICODE
Microsoft Visual SourceSafe RETURN_STRING_LOCAL
ProjectTracker (integration with Microsoft Project) RETURN_STRING_UNICODE
ProjectConsole/SoDA RETURN_STRING_LOCAL
Microsoft Visual Studio .NET RETURN_STRING_UNICODE
Eclipse RETURN_STRING_UNICODE
Business Objects Crystal Reports RETURN_STRING_LOCAL

Schema developers can create integrations between Rational ClearQuest and other applications.


Feedback