IBM Support

How to export data from ClearDDTS to ClearQuest

Question & Answer


Question

This technote explains how to export data from IBM® Rational® ClearDDTS® to IBM Rational ClearQuest®.

Answer

In order to migrate data from ClearDDTS to ClearQuest the User should use the command "cqexport" in the following syntax:


    ~ddts/bin/wt_perl bin/cqexport classname destination_dir

The above tool prepares raw data files of ClearDDTS defect data so that they can be easily imported into ClearQuest. The ClearQuest Administrator will need to prepare a suitable CQ schema in order to import the data.

REQUIREMENTS:
The User must have access to the "DDTS" user account on the ClearDDTS site. Also, sufficient disk space to contain the exported data is necessary. The tool may only be used on ClearDDTS version 4.1 and higher.

NOTE:
The tool does not modify any DDTS data. The User may safely execute this command as often as required. There will be no detrimental effect on the data in DDTS.

OPTIONS:
classname - the class to be exported

destination_dir - the path to where the exported data belongs

FILES
The exporter contains the following files:
cqexport - a Perl script; this is the only program that requires to be run.

cqconv - a binary executable that actually exports the data given complicated directions


APPLICATION OF CQEXPORT TOOL:
1. Log onto the DDTS server. "SU" to the DDTS user. Navigate to the directory into which the exporter was extracted.

2. Choose the class to be exported. (Only one class is handled at a time because each class contains its own field definitions.)
Select the destination storage directory for all the data.

Run the following syntax:

$DDTSHOME/[your_platform_bin]/wt_perl cqexport [classname] \
[destination_dir]

3. The User will first be asked for a confirmation of the startup arguments. Then the program iterates over each field in the given class's master.tmpl file and prompts the User about each unknown field. The User has a choice whether to export the given field. The type of each field must be entered, i.e. "DATE", "USER", and "STRING".

DATA TYPE DEFINITIONS
For the purpose of the cqexport tool four datatypes must be distinguished:

String - anything typed at the keyboard.

Date - fields that DDTS thinks of as a datetime; ClearQuest requires these fields to be printed out in a special format.

User - string fields that have a semantic meaning of being the User name; ClearQuest needs to have knowledge of the User before importing the record.

Status - the status field has to be exported as its expanded name. (User is not prompted for this.)

The User has a choice to interrupt the process of prompting for the fields at any time with "Ctrl-C". The tool will save the current answers. Upon restarting the exporter, the tool will continue where it was interrupted. This option can be useful if the User made a mistake on a field and wishes to restate answers.
Simply edit the [destination_dir]/fieldinfo file and remove the offending field. While rerunning the exporter, the tool will prompt again for that field.

4. Subsequently, the User is asked for the findbug query string which selects the records to be exported. It is recommended that the default query string or a different string be used. See the findbug manual page for more details.

5. The exporter also prompts for the path to where the data will be placed on the ClearQuest machine. This is necessary on account of the import format of attachments (DDTS uses the term "enclosures"). The format requires the full path to each enclosure including drive letter. If the User chooses it incorrectly, the enclosures.txt and history.txt files can easily be edited incorrectly after having been moved to the proper location.

Following the last prompt, the tool carries out the exporting and data preparation.

6. After running cqexport, the User should get the exported data:

a. Copy the two files - export.tar and export.bat - to the ClearQuest NT machine.
b. Place the files in the location entered above.
c. Next, run the export.bat script by double-clicking on it or running it from a command prompt.

7. Run CQ Designer and import the users.txt into the CQ database.

8. Run the CQ Import Tool. Use it to import the data in the following order:
NOTE: You have to import projects.txt first as Project record type in CQ. You can't import defects.txt unless you have imported projects first, enclosures.txt are imported as attachments, and history.txt is history itself.

projects.txt
defects.txt
enclosures.txt
history.txt


ADDITIONAL TIPS
Users should ensure that there is a field, which will contain the old DDTS identifier. Any attachments will need to be imported by referring to this identifier.



[{"Product":{"code":"SSSH4K","label":"Rational ClearDDTS"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"General Information","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF027","label":"Solaris"}],"Version":"4.7;4.8","Edition":"","Line of Business":{"code":"","label":""}}]

Historical Number

17406

Document Information

Modified date:
16 June 2018

UID

swg21124539