Uploading to the Rational Team Concert server

To complete this task, you must have the administrative rights that are required to create project areas and users.

Before you begin

Before you start uploading, you must get the file that defines the encoding rules and the line delimiters that are used upon the first deliver action. You must then get the magic.properties file in the ...\rpp\properties directory and put it in the jazz-scm directory. For more information about this file, see jazz.net.

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.

Procedure

  1. Prepare the Rational Team Concert™ environment
    Important: All the Rational Team Concert notions that mentioned here are explained in the Rational Team Concert help.

    To prepare the Rational Team Concert environment to receive the migration data, you must complete the following tasks:

    1. Open the Work Items perspective in Rational Team Concert.
    2. Create a Jazz™ repository connection.
    3. Create a project area from the Jazz repository connection. This project area defines the project deliverables, team structure, process, and schedule.
    4. Create a team area to which you must add the migration user. Assign this user the role that enables configuration management (permission on source control management actions such as Check-in and Deliver)
    5. Create a stream to store the artifacts. The team members will then be able to deliver their own changes to the stream and accept changes from other team members into their repository workspaces from the stream.
  2. Modify the unlock file
    You must run this step to retrieve the Pacbase locks on the instances that were migrated with the MIBJ journal extraction procedure.
    Note: The lock extraction option must have been indicated in the procedure.

    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.

  3. Share the projects of the local workspace

    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).

    This file, named scmtools_entries.bat, is in the .metadata folder of your local workspace. It contains all the parameter lines of the scm commands, the command lines to create a repository workspace that is associated with the stream, and the command lines to upload to the stream. It is generic for the successive uploads that are related to a multi-session or progressive migration, or for any development and maintenance operations. It is generated upon the first upload and remains valid for the next uploads. Only a few lines (the Rational® Programming Patterns location for example) must be modified according to the uploads. The scmtools_entries.bat file calls the scm command line extensions: rpp-uploadsandbox and rpp-zcompmap.
    Important: The workspace that is used to upload to the server cannot be reused, after the upload, for applications maintenance or development operations. However, it can still be reused for the continuation of the migration process, such as in a multi-session migration.
    You must first edit the scmtools_entries.bat file to set the parameters of the command lines.
    Table 1. List of the parameters setting lines
    Batch command lines to enter Explanations
    SET path="C:\Program Files\IBM\SDP\scmtools\eclipse";%PATH% Path to the Eclipse directory that contains the scmtools.
    SET jazz_uri=https://hostname:9443/ccm/ Repository URI (entered when a Jazz repository connection is created in the Team Artifacts view).
    SET jazz_id=JAZZ Migration user (defined in Jazz).
    SET project_area="TEST" Name of the project area with which the components are to be associated.

    It must exist before you run the scmtools_entries.bat file.

    SET jazz_Stream="TEST" Name of the stream that is used for the migration.

    It must exist before you run the scmtools_entries.bat file.

    SET jazz_wsp="TEST_WKS" Name of the repository workspace

    You must indicate the same repository workspace to successively upload the data that comes from several Pacbase sessions.

    If it does not exist, this workspace is created by the scmtools_entries.bat file.

    SET Location="TEST" Name of the Rational Programming Patterns location.
    SET Snapshot="xx" Snapshot name.
    SET Comment="xx" Comment on the change set.
    SET LocalWS="C:\Migration\Test" Name of the local workspace.

    It must exist before you run the scmtools_entries.bat file.

    SET DRIVE=C The drive must be the drive of the local workspace.
    SET create_cobcomp_opt="" If you chose to generate the COBOL code in separate projects (--separateCobolProject option in the --automaticMigration command), then you can use this option to upload these projects to separate components in Rational Team Concert.

    By default, this option is set to blank. All the COBOL projects will be in the same Rational Team Concert component as their design files projects.

    If you indicate -x, the COBOL projects will be in a Rational Team Concert component that is named as the design files project but that ends with .COB.

    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.

  4. Modify the lock file
    You must run this step to retrieve the Pacbase locks on the instances that were migrated from the MIBR or MIBJ extraction procedures.
    Note: The lock extraction option must have been indicated in the procedure.
    You must run the scmLock.bat script file after delivering to the Rational Team Concert server. This file is automatically created in the .metadata directory of the migration workspace upon the import. It contains the list of the instances that will be locked (or locked again in a progressive migration) on the Rational Team Concert server after the modifications are delivered. Only the user who owns the lock will then be able to deliver the locked instance.
    Note: The repository workspace that is used for the migration must be public to enable the users to lock instances.

    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.

  5. Build the server indexes

    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.

    With Rational Team Concert V6.0.1 and later, you configure the source code data scanning for the stream with the choice Open Scan Configurations. To know how to do it, see the explanations in the Rational Team Concert documentation: Creating a scan configuration for a stream.

    With Rational Team Concert V5.0.2 ou V6.0, click Select streams for scanning. So, 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.

    Important: This step can be very long. You must then modify the connection parameter of the Rational Team Concert server to avoid any timeout. To do so, right-click your repository connection in the Team Artifacts view. On the Jazz repository connection page, enter 0 in the Connection timeout (in seconds) field. Click OK.
  6. Process other Pacbase contexts

    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.


Feedback