To complete this task, you must have the administrative rights that are required to create project areas and users.
Then, edit the preferences.properties file that is in the jazz-scm directory. In this file, add the property trace.disable: true to optimize the upload.
To prepare the Rational Team Concert environment to receive the migration data, you must complete the following tasks:
You must unlock the locked instances before you can deliver them to the server, then lock them again if necessary.
You unlock the instances by running the scmUnLock.bat script file before delivering to the Rational Team Concert server. This file is automatically created in the .metadata directory of the migration workspace when the journal is imported.
It unlocks the instances that were modified or deleted by the journal. The instances that were created by the journal are not present in the script file.
In the script file, you must specify the address of the Rational Team Concert server, the stream, and the path to the scm commands.
The user ID and password of the Rational Team Concert administrator must be indicated in the script file. They can be entered manually or automatically retrieved from a file that must be explicitly created. This file must be named pac_rtc_users and must be in the same directory as the ta2 import file. It must contain at least one line, with the following syntax:
Pacbase user#RTC user#RTC password#A
The Pacbase user ID is optional for an unlock operation. #A indicates that it is an administrator. An administrator line is required.
When it is run, the scmUnLock.bat file generates an scmUnLocklog file in the .metadata directory so that you can verify the result of the unlock operation.
A script file that contains the Rational Team Concert scm commands to share the projets is automatically created at the end of the migration process, when the command file is run (rpp --commands).
Batch command lines to enter | Explanations |
---|---|
SET path="C:\Program Files\IBM\SDP\scmtools\eclipse";%PATH% | Path of the Eclipse directory that contains the scmtools |
SET jazz_wsp=RepWks | Name of the repository workspace You must indicate the same repository workspace to successively upload the data that comes from several Pacbase sessions. |
SET jazz_id=user | Migration user (defined in Jazz) |
SET jazz_uri=https://uri:9443/ccm/ | Repository URI (entered when a Jazz repository connection is created from the Team Artifacts view) |
SET project_area="project area" | Name of the project area with which the components are to be associated |
SET jazz_Stream=StreamMigr | Name of the stream that is used for the migration |
SET Snapshot=snapshot | Snapshot name |
SET Comment="xx" | Comment on the change set |
SET LocalWS=C:\xxxx | Name of the local workspace |
Then, run the scmtools_entries.bat file. For information on the commands that are run by this file, refer to the Rational Team Concert help on the source control command lines.
In the Work Items perspective, you must select the created streams in order for them to be scanned. In the Team Artifacts view, under your project area, select Enterprise Extensions > Source Code Data > Select Streams for Scanning.
Each time these streams are updated, the server indexes are created, if necessary.
To build the indexes for the first time, select Reset Source Code Data, available in the same menu as Select Streams for Scanning.
In the script file, you must specify the address of the Rational Team Concert server, the stream, and the path to the scm commands.
When it is run, the scmLock.bat file generates an scmLocklog file in the .metadata directory so that you can verify the result of the lock operation.
The script file must transfer the locks from the Pacbase users to the Rational Team Concert users, who are generally different. The Pacbase users are automatically retrieved from the records of the ta2 import file. They must be matched with the Rational Team Concert users. You can do it manually or create a pac_rtc_users file and store it in the same directory as the ta2 import file. The users will then be matched. Each line of the matching file represents a user, according to the following syntax:
Pacbase user#RTC user#RTC password
If the user is a Rational Team Concert administrator, you must add #A at the end of the line. An administrator line is not required to lock and, if it is present, it does not need to be matched with a Pacbase user. If passwords are not indicated in the matching file, the Rational Team Concert users and the word _password will be concatenated in the generated script file to create passwords.
To upload several contexts, you must verify that the value of the advanced property Encourage component names to be unique was changed to true, as it is indicated in the Rational® Programming Patterns installation guide.