Rational ProjectConsole Designer Help
After you select a mapping for a collection task, Rational ProjectConsole creates collection parameters that correspond to that mapping. The collection parameters are assigned the values used in the source template that created the mapping.
You can modify the collection parameters to reflect other values that you want to use. For example, you might want to collect Rational Rose data for a Rational Rose model that was not used to create the Rational Rose source template.
If the mapping for a collection task points to a text source template, Rational ProjectConsole creates a SourceInstance parameter for the task. The value of this parameter is the name of the template file used to create the text source template. You must modify this value, specifying the fully qualified path of the file. You can also collect data from a file other than the one used to create the source template.
You can define additional information (data not present in the source) for insertion during the data loading process.
For example, Unified Change Management (UCM) uses the concept of Projects to associate Rational ClearCase data with a specific project. Other Rational tools such as Rational RequisitePro also use the concept of projects and can be related to specific data within Rational ClearCase.
If you are extracting data from Rational Rose and you are not using UCM, you should define a field called Project and associate it with a project name or value. This makes it possible to distinguish the Rational Rose data from data collection from other sources so that a correlation between Rational products can be established. To do this, create a parameter called Project and assign it a value.