> -----Original Message----- > From: Christopher Schultz [mailto:ch...@christopherschultz.net] > Sent: Monday, March 10, 2014 10:15 AM > To: Tomcat Users List > Subject: Re: The Service Component > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Jeffrey, > > On 3/10/14, 10:26 AM, Jeffrey Janner wrote: > >> -----Original Message----- From: Leo Donahue > >> [mailto:donahu...@gmail.com] Sent: Friday, March 07, 2014 9:44 AM > To: > >> users@tomcat.apache.org Subject: The Service Component > >> > >> Who uses more than one Service in their server.xml and why? I get > >> that you can have multiple Connectors if you have multiple Service > >> components but why use multiple connectors? > >> > >> Are there any docs on the use cases for these features? > >> > > > > Hi Leo, I may be the only person on this list who does this > > consistently. I use it as an alternative method of virtual hosting, > > i.e. each host gets its own <Service> and related sub-structure. > > The real reason? The default host has to be set to something, and I > > don't want to maintain some generic host to catch those that come in. > > Since I'm running an SaaS environment, really more ASP, a business > > requirement is that each host appear to the outside world as a unique > > physical host, so two customers don't get the same IP address. I > could > > add <Alias> tags for the IP address and all know variations of the > > hostname, but there's nothing to keep some yahoo admin at a customer > > site from configuring a DNS entry on an internal DNS server with some > > name I'm not expecting. Therefore, each <Engine> in each <Service> > > gets a defaultHost entry pointing to its one and only <Host> entry. > > I'm interested in this use case. > > Since you have to maintain a <Connector> for every IP address already, > how is that different from having a single <Connector> with a bunch of > <Alias> elements? How are those different? Or is it that you need > application isolation in the first place, so this is the best way to do > it in a single JVM? >
It's primarily for App Isolation. The other is that I'm trying to keep the modifiable elements to a minimum, so that someone not completely versed in Tomcat can do a setup if I'm not available. Essentially, I have a predefined with <Service> tree that can be copied to a server.xml and only need to modify 7 values, 2 IP address fields, and 2 hostname fields, and engine name, a service name, and an appbase. The way I have it setup right now, you enter the same value for the last 3 entries in that list to make it easy to manage at the file system level. And by keeping it compact, it makes that move I mentioned easy, since all the elements are together in the server.xml (as opposed to <Connectors> being in one location and <Hosts> in another. Jeff --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
