Can one move a project to another existing team server?
I see this question has been asked in different forms a few times, the most recent being https://jazz.net/forums/viewtopic.php?t=2567.
I've had several users ask me if a project, in it's entirety, can be moved to another Team Server which is already hosting other projects.
The technote about the "251 user" is very helpful in explaining how to split out a project from a Team Server that has reached it's user limit, but that requires a new Team Server and repository.
The excitement with RTC has spawned many small startup instances internally which is great. Now these startups are looking to consolidate on existing IT shops' infrastructures for IT support savings, ITCS104 compliance, and exiting Build Forge, ClearCase and ClearQuest hosting.
Is there a way, or when will ther be a way, (supported or unsupported) to move RTC projects from one Team Server Hosted environment to another existing host without requiring a clean respository?
I've had several users ask me if a project, in it's entirety, can be moved to another Team Server which is already hosting other projects.
The technote about the "251 user" is very helpful in explaining how to split out a project from a Team Server that has reached it's user limit, but that requires a new Team Server and repository.
The excitement with RTC has spawned many small startup instances internally which is great. Now these startups are looking to consolidate on existing IT shops' infrastructures for IT support savings, ITCS104 compliance, and exiting Build Forge, ClearCase and ClearQuest hosting.
Is there a way, or when will ther be a way, (supported or unsupported) to move RTC projects from one Team Server Hosted environment to another existing host without requiring a clean respository?
3 answers
Unfortunately, no. There is no way to move a project area from one DB
to another DB, unless you follow the steps in the 251 users technote. I
agree that there is a lot of desire for something like that, but the
details of the items stored in the DB do not make it easy to
implement.
-
Matt Lavin
Jazz Server Team
On Wed, 2008-11-05 at 12:48 +0000, thloeber wrote:
to another DB, unless you follow the steps in the 251 users technote. I
agree that there is a lot of desire for something like that, but the
details of the items stored in the DB do not make it easy to
implement.
-
Matt Lavin
Jazz Server Team
On Wed, 2008-11-05 at 12:48 +0000, thloeber wrote:
I see this question has been asked in different forms a few times, the
most recent being https://jazz.net/forums/viewtopic.php?t=2567.
I've had several users ask me if a project, in it's entirety, can be
moved to another Team Server which is already hosting other projects.
The technote about the "251 user" is very helpful in
explaining how to split out a project from a Team Server that has
reached it's user limit, but that requires a new Team Server and
repository.
The excitement with RTC has spawned many small startup instances
internally which is great. Now these startups are looking to
consolidate on existing IT shops' infrastructures for IT support
savings, ITCS104 compliance, and exiting Build Forge, ClearCase and
ClearQuest hosting.
Is there a way, or when will ther be a way, (supported or unsupported)
to move RTC projects from one Team Server Hosted environment to
another existing host without requiring a clean respository?
The workaround for 251st user problem is described in
https://jazz.net/learn/LearnItem.jsp?href=content/tech-notes/rational-team-concert-1_0_1-server-capacity-problem-workaround/index.html
-- Balaji
Jazz Server Team
https://jazz.net/learn/LearnItem.jsp?href=content/tech-notes/rational-team-concert-1_0_1-server-capacity-problem-workaround/index.html
-- Balaji
Jazz Server Team
Matt, I checked the formal Technotes but didn't see this one. Will you post a pointer please? Is it a previous jazz.user forum topic?
Paul Sims
IBM WebSphere Commerce