We have a TFS environment with one App Tier server and one SQL server. So as make it easy for the users to remember the URL we implemented "IIS URL Rewrite Module" and "Microsoft Application Request Routing Version 2". Using these IIS modules we wrote some rules so that a user just need to type in "tfs.xxx.com" instead of entire URL "http://tfs.xxx.com:8080/tfs".
Few days later we added one more App Tier and implemented Big IP F5 load balancing. We replicated same IIS modules and redirection rules on the new App tier server.
Currently Load Balancer is redirecting requests for "tfs.xxx.com" to either of App Tier servers which means when a user tries to access TFS using browser by typing in "tfs.xxx.com" will redirected to either of the App Tier server.
Since these rules have been applied at server level therefore while connecting to TFS via Load balancer using Visual Studio is failing. Because the load balancer expects "tfs.xxxx.com" whereas in case of Visual studio though user types in "tfs.xxxx.com" but Visual Studio appends port number and directory and converts "tfs.xxxx.com" into "http://tfs.xxxx.com:8080/tfs" for which Load balancer is not prepared for.
Is there a way to make Load Balancer handle both (handling "tfs.xxxx.com" and "http://tfs.xxxx.com:8080/tfs") these kind of requests? Because we can leverage the second App Tier Server for High Availabilty only if Load Balancer can cater requests through both web and Visual Studio.
What options do I have?
Thanks in advance...
↧