Jazz Register Log in
Jazz Forum Welcome to the Jazz Community Forum

Welcome to the Jazz Community Forum

Connect and collaborate with IBM Engineering experts and users

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.

0 votes



One answer

Permanent link

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 

0 votes

Comments

Before I mark this as the answer, just to be sure:

Once you have deployed an app under a JTS, and have data, there is no way to move that app and its data to another JTS?  In my scenario above, the only deployed item that is a true duplication is the JTS on each server.  I was hoping I could stand up a "new" JTS, and then register the existing apps qm, rm, and ccm to the new JTS.  Then, kill the old JTS instances, or ignore them.

Cliff, my state of knowledge is that it is in fact the case that it is not supported/possible to move from multiple JTS and registered apps to one JTS and registered apps. I had been involved in several customer situations where that discussion came up and the answer was always no, as far as I recall. I have also been involved in creating as well as performing several talks, presentations, wiki pages that touched on these scenarios e.g. in https://jazz.net/wiki/bin/view/Deployment/PlanForMultipleJazzAppInstances . I am not sure if we mentioned the caveat in that wiki. We certainly should have. I will check.

I don't claim to know everything, so there is a chance this could be supported somehow. The best chance you would have to get a definitive answer of todays state would be to talk to support. If they say something else, it would be nice to learn about it.

Your answer

Register or log in to post 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,536

Question asked: Nov 07 '17, 5:11 p.m.

Question was seen: 2,204 times

Last updated: Nov 08 '17, 8:03 a.m.

Confirmation Cancel Confirm