Ideally (as it is working currently for us using RHQ 4.1) it should NOT be redirected to the real host:port URL (only) but be reverse proxied so we stay on the host:port alias "rhq".

Our main advantages are:
- links are short and easy to remember/generate
- links are independent from the "physical" RHQ server host:port
- load balancing/failover can be hidden behind those links
- RHQ server unavailability can be dealt with on the Apache side (we could easily set up a maintenance page or whatever to be delivered to the client if the Apache is still running)

user browser:
- typing "http://rhq" redirects (RHQ Apache) to "http://rhq/coregui/#Dashboards" (not to http://myrhqhost:7080/coregui/#Dashboards)

underneeth:
- setup DNS alias rhq to myrhqhost
- setup Apache HTTP reverse proxy on myrhqhost: "http://rhq(.*)$" <=> "http://myrhqhost:7080$1"

the load balancing/failover stuff Apache config that David mentioned is also in the pipe


On 07/24/2012 06:48 AM, Larry O'Leary wrote:
So you are saying that you rewrite the URL utilizing a proxy service
between the client browser and the RHQ server?

Such as http://rhq/coregui/#Dashboards becomes
http://server1.myrack.mydatacenter.corp:7080/coregui/#Dashboard

Based on that example, in your use-case, is it okay that the client
browser have its URL rewritten or should the browser always think its
retrieving content from http://rhq/coregui/#Dashboards




_______________________________________________
rhq-devel mailing list
rhq-devel@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/rhq-devel