Setting up distrubuted applications using enterprise topology !
Hi,
I am installing JTS, RQM, RTC in different machines using enterprise topology and for the same I am following online help provided by IBM for setting up this.
http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_update_jazz_setup_after_upgrade.html.
machine1 has JTS
machine2 has RQM
machine3 has RTC
I run the setup in machine1 and give public URI as https://machine1:9443/jts and I add discovery URL of RQM in register apps step, and everything goes smoothly after this.
Now if I run the setup again the public URI will be https://machine2:9443/jts and it throws the error "URI is already set to https://machine2:9443/jts and cannot rename it to https://machine1:9443/jts". How come such strange error it gets URI rename to machine2 automatically. am i missing any steps here...inputs?
I am installing JTS, RQM, RTC in different machines using enterprise topology and for the same I am following online help provided by IBM for setting up this.
http://pic.dhe.ibm.com/infocenter/clmhelp/v3r0m1/index.jsp?topic=%2Fcom.ibm.jazz.install.doc%2Ftopics%2Ft_update_jazz_setup_after_upgrade.html.
machine1 has JTS
machine2 has RQM
machine3 has RTC
I run the setup in machine1 and give public URI as https://machine1:9443/jts and I add discovery URL of RQM in register apps step, and everything goes smoothly after this.
Now if I run the setup again the public URI will be https://machine2:9443/jts and it throws the error "URI is already set to https://machine2:9443/jts and cannot rename it to https://machine1:9443/jts". How come such strange error it gets URI rename to machine2 automatically. am i missing any steps here...inputs?
Accepted answer
Hi,
important: please be aware that you should use full qualified and machine independent host names e.g. jts.example.com, ccm.example.com etc.. Machine independent is important if you need to move to a faster machine later and your IT department might not allow to move the name of the machine to another host.
Your original question:
If you intended to install with one shared JTS Machine 2 and 3 won't have a JTS, hence the conflict.
You should have to run setup only once. You typically run setup against the shared JTS. The other machines host the applications with the context roots ccm (RTC) and qm (RQM). During the application registration you pick the context roots of the applications installed on each server. In your case, if you installed with the default context roots https://machine2:9443/qm and https://machine3:9443/ccm. As long as the applications have been successfully deployed and the servers are started the setup should connect OK. Each application on its host then has the context root you used for registering https://machine2:9443/qm and https://machine3:9443/ccm not https://machine2:9443/jts nor https://machine3:9443/jts.
important: please be aware that you should use full qualified and machine independent host names e.g. jts.example.com, ccm.example.com etc.. Machine independent is important if you need to move to a faster machine later and your IT department might not allow to move the name of the machine to another host.
Your original question:
If you intended to install with one shared JTS Machine 2 and 3 won't have a JTS, hence the conflict.
You should have to run setup only once. You typically run setup against the shared JTS. The other machines host the applications with the context roots ccm (RTC) and qm (RQM). During the application registration you pick the context roots of the applications installed on each server. In your case, if you installed with the default context roots https://machine2:9443/qm and https://machine3:9443/ccm. As long as the applications have been successfully deployed and the servers are started the setup should connect OK. Each application on its host then has the context root you used for registering https://machine2:9443/qm and https://machine3:9443/ccm not https://machine2:9443/jts nor https://machine3:9443/jts.
Comments
2 other answers
Hi,
please read the answer above very carefully.
You have deployed
JTS on machine1 (one)
QM on machine2 (no JTS)
CCM on machine3 (no JTS)
You typically start all machines. You run setup only once for the JTS. https://machine1:9443/jts/setup. During the setup you set the Public URI for JTS to https://machine1:9443/jts/. In the application registration step you register https://machine2:9443/qm/ and https://machine3:9443/ccm/. When you continue the setup the Public URI for QM is https://machine2:9443/qm/ (and not .../jts) in the part for CCM it is https://machine3:9443/ccm/ etc..
You don't install JTS on machine 2 and 3 and the setup for the individual applications would be https://machine2:9443/qm/setup and https://machine3:9443/ccm/setup.
If you run an individual setup for any of the applications their public uri is one of the ones used above https://machine2:9443/qm/, https://machine3:9443/ccm/ .
If you have done the install and set context roots wrong already I would uninstall and do a fresh install.
Please also consider to at least read this article: https://jazz.net/library/article/831
please read the answer above very carefully.
You have deployed
JTS on machine1 (one)
QM on machine2 (no JTS)
CCM on machine3 (no JTS)
You typically start all machines. You run setup only once for the JTS. https://machine1:9443/jts/setup. During the setup you set the Public URI for JTS to https://machine1:9443/jts/. In the application registration step you register https://machine2:9443/qm/ and https://machine3:9443/ccm/. When you continue the setup the Public URI for QM is https://machine2:9443/qm/ (and not .../jts) in the part for CCM it is https://machine3:9443/ccm/ etc..
You don't install JTS on machine 2 and 3 and the setup for the individual applications would be https://machine2:9443/qm/setup and https://machine3:9443/ccm/setup.
If you run an individual setup for any of the applications their public uri is one of the ones used above https://machine2:9443/qm/, https://machine3:9443/ccm/ .
If you have done the install and set context roots wrong already I would uninstall and do a fresh install.
Please also consider to at least read this article: https://jazz.net/library/article/831
You should not have to run the setup for QM and CCM (or RM). The reason is, once you register those apps, they are pulled into the setup process and you actually should run through it automatically, as far as I remember.
Comments
showing 5 of 6
show 1 more comments