If the other application is not fully Unicode compliant, its data is considered to be in Local mode. In this case, Rational ClearQuest 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.
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 |
ProjectTracker (integration with Microsoft Project) | RETURN_STRING_UNICODE |
Eclipse | RETURN_STRING_UNICODE |
SAP Crystal Reports | RETURN_STRING_LOCAL |
Schema developers can create integrations between Rational ClearQuest and other applications.