To carry out this task, you must have the administrative rights that are required to create project areas and users.
To prepare the Rational Team Concert environment to receive the migration data, you must carry out the following tasks:
To upload data to the server, use the scmtools_entries.bat file that is created upon import. This file is in the .metadata folder of your local workspace or in the location that is indicated in the rpp --automaticMigration command. 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 carry out these operations by opening a command prompt and entering the command lines to upload the data to the Rational Team Concert server.
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 file performs the following actions:
lscm login -r %jazz_uri% -n Batch -u %jazz_id% -c
scm create ws -u %jazz_id% -P %jazz_pw% -r %jazz_uri% -s "%jazz_Stream%" "%jazz_wsp%"
The following actions must be carried out for each project that is created by the import:
Creation of the component that will contain the project originating from the Pacbase Library or the COBOL sources, and modification of the properties of this component.
lscm create comp -r %jazz_uri% "%Component%" "%jazz_wsp%"
lscm component propertyset visibility public "%Component%" -r %jazz_uri%
lscm component propertyset ownedby %project_area% "%Component%" -r %jazz_uri%
Sharing of the project in the component, creation of a change set, and checkin.
lscm share -r %jazz_uri% "%jazz_wsp%" "%Component%" "%LocalLWS%\%Component%"
lscm create cs --component "%Component%" -r %jazz_uri% -w "%jazz_wsp%" %Comment%
lscm checkin "%LocalLWS%\%Component%"
lscm deliver -q -r %jazz_uri% -d %LocalLWS% -s "%jazz_wsp%"
lscm create ss -r %jazz_uri% "%jazz_Stream%" -n "%Snapshot%"
lscm logout -r %jazz_uri%
scm daemon stop "%LocalLWS%"
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.
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.