Multisite implementation with RTC 4.0.1
My organisation is having multiple site development units, and we want to have secure configuration and change management among our Mumbai and Delhi base units. We want, that the ownership should lies with Delhi office and Mumbai office will have controlled access to central repository.
Can you please help me in setting up RTC (Configuration management) between our Delhi and Mumbai office with central repository for change and configuration management.
Thanks and Regards
Shruti
2 answers
Comments
unfortunately, that article barely mentioned Distributed SCM in RTC.
This provides a LOCAL RTC for source code operations with the ability to commit from one stream (local server) to another (master)..
the setup is a FULL RTC locally which may be a support issue (we removed most of our IT staff from remote offices). Also, during the promote operations, the user requires TWO licenses checked out concurrently.. one on each server.
you also have to decide if the RTC instances share a license server , or have separate copies. If the phone line goes down and u share JTS, then operations stop on the remote CCM, if u don't share, then you have ANOTHER server manage remotely, AND you need two license pools. (cost & mgmt).
our IT org application support model says we cannot have web server and DB server on the same machine (logical), so you have two OS's, two App servers, two apps, and maybe require JTS and an IHS in front as well..
you also have to consider backup and recovery strategies from the remote office, as it will now be holding some of your precious intellectual property.
I am not entirely sure what you ask for here. In general you have two options with RTC if you work at multiple sites.
-
You can configure a central server at one site. The other site can access this site e.g. via VPN and use the SCM and CM component like any local user can. The permissions and visibility to SCM data like streams is managed in the repository as required. To reduce network bandwidth you can use a caching proxy on the remote site that the eclipse clients talk to, instead of directly talking to the server.
-
You can set up RTC for distributed SCM - it needs to be enabled in the CCM advanced properties of the servers first. Using distributed SCM allows certain users with the permission to read/write a stream on both sites and the permission to replicate change sets to flow replicate SCM data across sites. These users could have a repository workspace on one server, that flows with a stream on the other server. This way they can replicate changes back and fort and also synchronize streams on both sites. There is no mastership concept in RTC however. Anyone who has the permission can read and write SCM data. Conflicting changes on different streams need to be solved by merging as in the usual use cases.
