On 5/15/07, Nathan Hook <[EMAIL PROTECTED]> wrote:
We are an Application Service Provider (ASP) that has numerous clients with the number of clients increasing rapidly. All our clients use the same application but each client needs/wants a distinguishing element in the url to identify them to their users.
Then in our server.xml config file for Tomcat we only declare one Host element with a Context that has many Alias':
So, what is the problem? Well, when we add a new customer we have to edit the httpd.conf, the server.xml, restart both applications, and add the new <customer>.<server name>.com to DNS
OK, maybe I'm missing something, but if you want *one* context to handle *all* requests -- why not just make that the default? Don't even bother to specify any hostnames or aliases. Voila. :-) You still have to have the DNS entries, but you knew that... And it's not clear whether you're serving unique static content from the httpd DocumentRoot you specify; if not, you could just get rid of that -- using httpd -- as well. FWIW, -- Hassan Schroeder ------------------------ [EMAIL PROTECTED] --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
