When you import data from a Subversion repository, you must decide how to express the organization of the Subversion repository as one or more Rational Team Concert source control components. An understanding of typical Subversion repository layouts can help you choose the best way to organize your import.
Project1
trunk
folder/plug-in1
folder/plug-in2 tags
branches
Project2
trunk
tags
branches
trunk
folder/plug-in1
folder/plug-in2
tags
branches
trunk
src
.classpath
tags
branches
Unless you are importing from a very simple Subversion repository, one that contains only a few revisions of one or two small projects, it is impractical to import the entire dump file in a single operation. Importing a single line of development at a time (the trunk, for example, or a branch) generates a set of component baselines that make it easier to use Rational Team Concert source control tools on the imported projects.
By default, the importer creates Rational Team Concert source control baselines that correspond to Subversion branch and tag points. Because of differences in the data model (Rational Team Concert source control uses change sets and Subversion does not), these mappings do not always have a one-to-one correspondence.
com.ibm.team.repository.db.db2.content.tablespace.numpages
to a higher value. As a rule, 250000 DB2 pages will accommodate 10000 Subversion revisions.When you are importing from a Subversion repository with a long history, the server connection might time out before the imported stream has been created. To avoid this, right-click the repository connection in the Team Artifacts view and click Properties. In the Jazz Repository Connection properties, set the Connection Timeout to a high value, such as 3600 (which causes the client to wait for one hour before displaying a connection time-out error). Even if the connection does time out, the operation will continue until it completes.
Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug