Proxying to Jazz tomcat with Apache
I am trying to proxy to my jazz server using an apache rewrite proxy and this connects fine to the Tomcat.
But it seems there is a setting somewhere in Jazz that wants to connect to $HOSTNAME:$PORT/jazz/web I could conceptually do a separate vhost and then set the port in teamserver.properties to 80/443 and the hostname in teamserver.properties as well. But to be able to run this in the already defined vhost and use subdirecty on the URL to proxy to Jazz seems tricky here. Basically, I want this mapping: http://myhostname/jazzsetup1/jazz => http://myhostname:9080/jazz On the Apache side, this is just: RewriteRule ^/jazzsetup1/(.*) http://myhostname:9080/$1`
|
6 answers
Hi Ken,
Any success with your redirect from Apache to Tomcat? I am interested in the same configuration and don't want to reinvent the wheel if I can help it. I am not interested in restricting access - just hosting the HTTP portion on a separate server from the Application Server. -Bryan |
I believe that it is possible to proxy Jazz behind an Apache frontend. We proxy part of the jazz web ui through jazz.net so I know that the web piece will work. I think other teams have setup a proxy/caching server between the Jazz server and their clients before, so I believe that it will work as well.
To get Jazz to use the external name of your server, you need to set some properties on the Advanced Properties page of the admin web UI. Specifically you should set Public URI Root = https://<yuorserver>/jazzsetup1/jazz There might be other properties you can set, but start with that and let's see if you run into any problem. |
|
Matt, thanks for your help. We decided to attempt to try to use the WAS HTTP plug-in as a front end for now. If that doesn't work as expected we'll try to configure more like jazz.net.
-Bryan |
|
I have a feeling that the same setup will be required even if you use the WAS plugin, because there are some cases were the Jazz Team Server wants to know the hostname of the machine (for things like links in bug e-mails).
Please keep us posted about your configuration and if you write a little document about how you setup your machine we could host it on the wiki for others. |
You could try something like this on your Apache machine to proxy requests to Tomcat:
ProxyPass /jazz1/jazz http://myhostname:9080/jazz/ <Location> ProxyPassReverse /jazz1/jazz </Location> |
We're just getting started with RTC v1.0.1. Using Tomcat as the app server and apache mod_proxy as the proxy on a SLES 10.1 server. We have implemented the following mod_proxy config statements:
<IfModule> Seems to be working so far for browser requests - no problem navigating between admin and project spaces, login/logout/etc... I don't think we've done much with the client to see whether it holds up for all activities, and we haven't checked on things like the links that are sent out in emails - I suspect they do have the port embedded in the URL. Having the port included in the URL is OK for us at the moment as we still have access directly to the port, but we anticipate that one day we may move into a more protected firewall zone where we'll be required to come in via standard http/https ports. At that point (or sooner) we'll have to investigate setting the Public URI Root, or hosting on a server that isn't already hosting other https traffic on Apache. |
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.