Re: HOST - DNS setup
Im doing something (vaguely)similar using Apache2, mod_jk and mod_rewrite. Im taking the 1st part of the address (http://1.2.3 - the '1') and using it to determine what db to access. mod_rewrite lets you get v detailed with parsing the incoming URL. Perhaps you could boil down your efforts into some perl and let apache do the work for you rather than having to maintain multiple independant server.xml files. Just a notion. Hi Hmm as far as i know there is no other way... The only thing i know you could do is the following: Create a CatchAll-DNS entry which responses to *.mycompany.com = All requests to subdomains which are not in use will go to the default context. From there you could redirect/forward the request to the apropriate context. To get the requested hostname you can do: String reqHost = request.getHeader(Host); ^^^ (which will contain: blah.mycompany.com if user typed: http://blah.mycompany.com) (as far as i know - i do not have tested this). greets, mike Kal Govindu wrote: Hi all, Our company has just started into Java based web applications. Our current methodology for deploying to production is to setup a DNS like say firstapp.mycompany.com and define a Host entry in the server.xml with aliases to respond to the new DNS. We do this purely for the capability of typing http://firstapp.mycompany.com in a web browser and getting to the application. But this is kind of cumbersome and time consuming setup when ever we deploy to production. As we have more applications this way we will end up with several Host's which does not seem like a good thing. Is there a better way to do this? Please help. Thanks Kal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HOST - DNS setup
I'm not sure what you are after. But... You could put Apache in front of Tomcat. Have Apache mount the appropriate Tomcat apps so that you would be able to type in. http://mycompany.com/firstapp Or you could setup a Virtual Host for each time you wanted to do: http://firstapp.mycompany.com/ It may not be that much different but it does mean you don't have to touch Tomcat configuration when deploying, just Apache. Oscar On Thu, 29 Jan 2004, Kal Govindu wrote: Hi all, Our company has just started into Java based web applications. Our current methodology for deploying to production is to setup a DNS like say firstapp.mycompany.com and define a Host entry in the server.xml with aliases to respond to the new DNS. We do this purely for the capability of typing http://firstapp.mycompany.com in a web browser and getting to the application. But this is kind of cumbersome and time consuming setup when ever we deploy to production. As we have more applications this way we will end up with several Host's which does not seem like a good thing. Is there a better way to do this? Please help. Thanks Kal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HOST - DNS setup [T2004013100BN]
Dear [EMAIL PROTECTED], We received your message on 1/30/2004 at 8:15:17 PM Central Standard Time. Thank you for contacting Member Savings. We have received and are reviewing your inquiry. Due to heavy volume, it may take longer than usual for us to get back to you. Messages are being answered within 5 to 7 business days. In the event you need to contact us regarding this inquiry, please refer to the tracking number at the top of this message. Member Savings Representatives are available to respond to messages Monday through Friday 8:00AM to 5:00PM Central Standard Time, excluding holidays. Thanks once again for writing. You will hear from one of our staff shortly. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: HOST - DNS setup
Hi Hmm as far as i know there is no other way... The only thing i know you could do is the following: Create a CatchAll-DNS entry which responses to *.mycompany.com = All requests to subdomains which are not in use will go to the default context. From there you could redirect/forward the request to the apropriate context. To get the requested hostname you can do: String reqHost = request.getHeader(Host); ^^^ (which will contain: blah.mycompany.com if user typed: http://blah.mycompany.com) (as far as i know - i do not have tested this). greets, mike Kal Govindu wrote: Hi all, Our company has just started into Java based web applications. Our current methodology for deploying to production is to setup a DNS like say firstapp.mycompany.com and define a Host entry in the server.xml with aliases to respond to the new DNS. We do this purely for the capability of typing http://firstapp.mycompany.com in a web browser and getting to the application. But this is kind of cumbersome and time consuming setup when ever we deploy to production. As we have more applications this way we will end up with several Host's which does not seem like a good thing. Is there a better way to do this? Please help. Thanks Kal - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
