Unregister ccm app from one JTS and register in another
Hi guys,
I have the following scenario: CCM1 registered in JTS1 and CCM2 registered in JTS2. I'd like to unregister CCM1 from JTS1 and register it in JTS2, so I will have CCM1 and CCM2 registered in JTS2.
Does anybody already did something like that? What is the premisses?
What was the experience? What was the impact, the issues?
For example, I know that I can't do that with ccm applications using the same context, right?
Thanks for any tips.
|
Accepted answer
My understanding is that this capability is called "reparenting" and it isn't supported at this time.
Ralph Schoon selected this answer as the correct answer
|
3 other answers
Ralph Schoon (63.1k●3●36●46)
| answered Oct 05 '16, 8:53 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
Flow changes cross repositories with Rational Team Concert
Rational Team Concert Workshop – Distributed SCM and Shipping RTC SCM Change Sets Across Disconnected Networks Also see https://jazz.net/wiki/bin/view/Deployment/MultipleCCMAppsUserPerspective , https://jazz.net/wiki/bin/view/Deployment/MultipleCCMAppsBestPractices , https://jazz.net/wiki/bin/view/Deployment/PlanForMultipleJazzAppInstances |
|
Thank you guys...
Well, if It's not possible, let me ask you another question, but related to this...
Is there any possibility to move/copy/transfer the source code that is in CCM1 to CCM2 without loosing the history, considering that app's are not registered in the same JTS?
Thank you one more time.
|
|
Ralph Schoon (63.1k●3●36●46)
| answered Oct 04 '16, 4:29 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I would suggest to talk to support about this. I would assume this is likely not supported.,
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.
Comments
I'm quite concerned about this practice. It will be quite difficult to maintain the UUID of all those users, if possible at all. Also, you will have to do a server rename, apparently, for the host name, and potentially the context root as well, but I don't know where to start with this.