How to merge 2 CLM installations with separate apps into one deployment
I have 2 separate CLM 6.0.4 iFix004 deployments that were built autonomously before there was a need to put them together.
Server A has JTS, CCM, RM, and accessories DW, DCC, LQE, and RS
Server B has JTS, QM, and accessories DW, DCC, LQE and RS
There are lots of links between QM RM and CCM that we are fearful of losing (years of work)
The desired simplification would be to stand up a single JTS on its own server, QM on it's own server, CCM on its own server, RM on its own server, and then a collection and reporting server for the accessories
I have read many articles about server renaming, and reverse proxy server fronting the deployment, I have not found any article in the wiki or forum that mentions what the implications are (if any) to merging 2 JTS instances into 1, or, if you just start over with a new JTS that registers all the apps where they reside. I'm not opposed to keeping the QM app on its current server, and keeping CCM and RM on its current server to avoid a rename. Our user list is small, so manually re-entering that kind of info should be doable. For the data collectors and reporting, we can just blow that away, and install fresh and collect again from scratch.
One answer
As far as I know, there is no way to "merge" such a deployment. What you can do is to make the apps registered to different JTS and the JTS' friends, so the user does have a better experience and you can basically have any data of any application on your dashboards, regardless which app this data comes from.
PS: where the app run (which server) is not really the question, if you have set up the topology with a forward proxy in front as suggested in https://jazz.net/wiki/bin/view/Deployment/StandardTopologiesOverview
Comments
