Rational Programming Patterns for System z

Uploading to the Rational Team Concert server

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

Procedure

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

    To prepare the Rational Team Concert environment to receive the migration data, you must perform 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 which enables configuration management (permission on source control management actions: Check-in, 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. Share the projects of the local workspace

    To upload data to the server, use the scmtools_entries.bat file created upon import. This file is located in the .metadata folder of your local workspace. This file contains all the parameters setting lines, the command lines to create a repository workspace associated with the stream, and the command lines to upload the data to the stream. To use this file, you must first set the parameters lines.

    You can also manually perform these operations by opening a command prompt and entering the command lines to upload the data to the Rational Team Concert server.

    Important: All the tasks explained here are performed with the Rational Team Concert source control command lines. However these tasks can also be performed from the graphical interface of the Work Items perspective. See the Rational Team Concert help for explanations.
    Change to the directory which contains the source control management tools (CD 'SDP directory'\scmtools\eclipse) and enter the lines which set the parameters of the command lines.
    Table 1. List of the parameters setting lines
    Batch command lines to enter Explanations
    SET jazz_wsp=WksRef Name of the repository workspace
    SET jazz_id=user Migration user (defined in Jazz)
    SET jazz_pw=password Password of the migration user
    SET jazz_uri=https://uri:9443/ccm/ Repository URI (entered when creating a Jazz repository connection from the Team Artifacts view)
    SET jazz_Stream=StreamMigr Name of the stream used for the migration
    SET LocalWS=C:\xxxx Name of the local workspace
    SET Library=lib Name of the source Pacbase Library
    1. Create a repository workspace associated with the stream:

      You must enter the following command line to associate the repository workspace with the stream:

      scm create ws -u %jazz_id% -P %jazz_pw% -r %jazz_uri% -s "%jazz_Stream%" "%jazz_wsp%"

    2. Upload the data to the stream:

      You must perform the following actions for each project created by the import:

      1. Create a component:

        Create the component which will contain the project originating from the Pacbase Library (here the Library code is the component name). Enter the following command:

        scm create comp -u %jazz_id% -P %jazz_pw% -r %jazz_uri% %Library% "%jazz_wsp%"

      2. Share the project:

        Share the project in the component with the following command line:

        scm share -u %jazz_id% -P %jazz_pw% -r %jazz_uri% "%jazz_wsp%" %Library% %LocalWS%\%REFER%.%Library%

      3. Deliver the project:

        Upload (deliver) the project to the stream to make it available to the other team members. Enter the following command line:

        scm deliver -u %jazz_id% -P %jazz_pw% -r %jazz_uri% -d %LocalWS% -C %Library%

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

  4. Process other Pacbase contexts

    Depending on the elements to be retrieved from Pacbase, you must perform the preceding steps for each session to be migrated to Rational Team Concert.

    After each iteration, create a snapshot of the migration stream. If an instance coming from a Pacbase frozen session is to be corrected, you must create a stream from the snapshot.
    Important: You must keep the same components during all the migration process.

    From the second iteration onwards, you must no longer create components or share projects because these actions have already been completed. However you must check in and deliver.


Terms of use | Feedback

This information center is powered by Eclipse technology. (http://www.eclipse.org)