rpp --importJournal
This command imports updates into Rational Programming Patterns. These updates are extracted from the Pacbase journal or from the file that is produced by the MIBU customized migration procedure. The file to be imported must have a .ta2 extension but its name must not be MIBR. This command is automatically run by the rpp --automaticMigration command for a progressive migration. However, you can also run it independently.
Syntax
rpp.bat --importJournal [options]Parameters
Options | Comments | Required | Default values |
---|---|---|---|
--data | Full path to the workspace | Yes | |
--log | Log file name The beginning of this file reminds the parameters that were entered to run the Pacbase migration procedures. |
trace.log | |
--fromFile | Name of the input .ta2 file. This file must not be named MIBR.ta2. | Yes | |
--fromDataFile | Path and name of the .xml technical file to take into account for the import | Yes | |
--location | Target location | Yes | |
--generatedDataFile | Path and name of the .xml technical file that is generated after the import | imported_data_refer.xml in the .metadata folder, where refer corresponds to the target location | |
--report | Import report file | N/A | .pacmigration.log in the .metadata folder of the workspace |
--overwriteReport | Overwriting of the report file | N/A | false - default append to the existing file |
- User code in Rational Team Concert
- Name of the stream where the projects are uploaded to
- Address of the Rational Team Concert server
- Path of the folder that contains the lscm command
The .xml technical file that is created at the end of the import is required for a subsequent import. This file contains information that is not included in the Rational Programming Patterns metamodel, and the list of the instances that were previously imported.
- The context of the import such as the database, user, session, Library, and date.
- The replaced special characters.
- The statistics of the instances that are present in the .ta2 file. These figures include the instances that were duplicated by the migration procedures.
- The errors that were detected upon the import.
- The Data Structures and Dialogs that were duplicated by the import.
- The number of imported instances and the number of the instances in the .ta2 file. The number of imported instances can be lower than the number of the instances in the .ta2 file if you import a new Pacbase session into the same workspace. In this case, the instances that were not modified are not counted among the imported instances.
- The number of modified/created/deleted design entities.