Using a single context root for all CLM applications
Is it possible to make all CLM applications work using a single context root?
For example, for RRC 3.0 the following context roots are created by default: /jts, /rm, /admin. Is there any way to configure JTS and RRC so that the same context root is used?
For example, so that all addresses look like:
http://servername:9080/jazz/ jts
http://servername:9080/jazz/ admin
http://servername:9080/jazz/ rm
For example, for RRC 3.0 the following context roots are created by default: /jts, /rm, /admin. Is there any way to configure JTS and RRC so that the same context root is used?
For example, so that all addresses look like:
http://servername:9080
http://servername:9080
http://servername:9080
8 answers
Currently we require that each application is installed with it's own unique context root on the same server. You could use the same context root on different servers with different host names.
The infocenter also has a section on planning URLs: http://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/c_planning_URLs.html.
Ritchie Schacher
Jazz Foundation
The infocenter also has a section on planning URLs: http://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/c_planning_URLs.html.
Ritchie Schacher
Jazz Foundation
Currently we require that each application is installed with it's own unique context root on the same server. You could use the same context root on different servers with different host names.
The infocenter also has a section on planning URLs: http://jazz.net/help-dev/clm/topic/com.ibm.jazz.install.doc/topics/c_planning_URLs.html.
Ritchie Schacher
Jazz Foundation
Thank you for your reply, Ritchie.
In the "Planning URIs" section it is said that "If you are deploying up multiple instances of CCM, QM, and RM to one logical host, choose context roots that have meaning within your organization".
So, I guess that it is possible at least to change the default context roots for the applications, as long as they remain unique for each application (say, to use context root /requirements instead of /rm, and /teamserver instead of /jts). Is there any guide describing how to do this?
Actually current URL should look like this
http://servername:9080/jts for Jazz Team Server
http://servername:9080/rm for RRM
http://servername:9080/qm for RQM
http://servername:9080/ccm for RTC
And corresponding administration UI url wll be
http://servername:9080/jts/admin
http://servername:9080/rm/admin
http://servername:9080/qm/admin
http://servername:9080/ccm/admin
You can use any other context root but I am not sure if it will work when two or more application have context root conflict.
-|- Pramod Chandoria
http://servername:9080/jts for Jazz Team Server
http://servername:9080/rm for RRM
http://servername:9080/qm for RQM
http://servername:9080/ccm for RTC
And corresponding administration UI url wll be
http://servername:9080/jts/admin
http://servername:9080/rm/admin
http://servername:9080/qm/admin
http://servername:9080/ccm/admin
You can use any other context root but I am not sure if it will work when two or more application have context root conflict.
-|- Pramod Chandoria
You can use any other context root but I am not sure if it will work when two or more application have context root conflict.
And how can I change the context roots used? For example, to make them look like this:
http://servername:9080/teamserver for Jazz Team Server (and Server Administration page will be http://servername:9080/teamserver/admin)
http://servername:9080/requirements for RM
and so on.
Is it possible?
I don't think there will be any conflicts with this approach.
But our ultimate goal is not to change the contexts of each application, but to make them multi-level, so that all applications shared the single root. Like this:
http://servername:9080/clm/rm
http://servername:9080/clm/jts
http://servername:9080/clm/qm and so forth.
But as I understand from what Ritchie said, it is not possible at the moment. So we are trying to find out if it is possible at least to change the contexts.
Also, please note that we recommend you use https and port 9443 for secure communications.
Thanks, Ritchie! We are aware of that. The environment in which Jazz applications are planned to be used has some special features that force us to use http instead of https.
You can use installation manager with a silent install to use a non-default context root and it will fix all the appropriate files. I've asked someone from the install team to comment, and filed 167166: Need guidance for how to install to a different context root than the default. (https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/167166)
You can use installation manager with a silent install to use a non-default context root and it will fix all the appropriate files. I've asked someone from the install team to comment, and filed 167166: Need guidance for how to install to a different context root than the default. (https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/167166)
Thank you, Ritchie!