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.

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. Share the projects of the local workspace
    You can use two files that are created by the import:
    • The scmtools_entries.bat file for the initial sharing.
    • The scmtools_entries_update.bat file when the projects of the local workspace are already shared. This file calls the scmtools_entries.bat file with different variables according to the updates.
    These two files are in the .metadata folder of your local workspace or in the location that is indicated in the rpp --automaticMigration command. They contain all the parameter lines, the command lines to create a repository workspace that is associated with the stream, and the command lines to upload the data to the stream.
    Important: The workspace that is used to upload the data to the server cannot be reused after the upload.
    You can also upload the data to the Rational Team Concert server manually by opening a command prompt and entering the command lines.
    Important: All the tasks that are explained here are completed with the Rational Team Concert source control command lines. However, these tasks can also be completed from the graphical interface of the Work Items perspective. See the Rational Team Concert help for explanations.
    To upload data to the server with the two files that are created by the import, you must first edit the scmtoolsEntries.bat file and modify the settings of the command lines parameters.
    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 of the Eclipse directory that contains the scmtools
    SET jazz_wsp=WksRef Name of the repository workspace
    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

    The command files complete the following actions:

    1. Connecting to Rational Team Concert

      lscm login -r %jazz_uri% -n Batch -u %jazz_id% -c

    2. Creating a repository workspace that is associated with the stream

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

    3. Uploading the data to the stream

      The following actions must be completed for each project that is created by the import:

      1. Creating a component:

        The component that will contain the project that originates from the Pacbase Library or the COBOL sources is created, and its properties are modified.

        The scmtools_entries.bat file initializes the components. The scmtools_entries_update.bat file updates the components that are already present in the Rational Team Concert stream and/or shares the new projects of the local workspace.

        lscm create comp -r %jazz_uri% "%Component%" "%jazz_wsp%"
        lscm component propertyset ownedby %project_area% "%Component%"  -r %jazz_uri%
      2. Sharing the project:
        Projects are shared in components upon the initial uploading (scmtools_entries.bat file).
        lscm share  -r %jazz_uri% "%jazz_wsp%" "%Component%" "%LocalLWS%\%Component%"
        When updates are uploaded (scmtools_entries_update.bat file), the new projects of the local workspace are shared, and change sets are created and checked in. For the projects that are already shared, change sets are created and checked in.
        lscm share  -r %jazz_uri% "%jazz_wsp%" "%Component%" "%LocalLWS%\%Component%"
        lscm create cs --component "%Component%" -r %jazz_uri% -w "%jazz_wsp%" %Comment%
        lscm checkin lscm checkin -N %LocalLWS%\%Project%
    4. Delivering all the modifications

      A deliver command is run after each share.

      lscm deliver -q -r %jazz_uri% -d %LocalLWS% -s "%jazz_wsp%"

    5. Creating a snapshot

      lscm create ss -r %jazz_uri% "%jazz_Stream%" -n "%Snapshot%"

    6. Logging out

      lscm logout -r %jazz_uri%

    7. Stopping the daemon

      scm daemon stop "%LocalLWS%"

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

    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.
  4. Processing other Pacbase contexts

    The scmtoolsEntries script can be used 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