5.2.3  One Instance of Tomcat on a Single Server 
Advantages: Easy to configure (only single server.xml file). 
Disadvantages: Interference among developers when using Tomcat (starting, stopping, 
debugging). Source of error messages is identifiable, but more effort is needed. The system 
resources must be shared among all developers. 
Installing just one instance of Tomcat on a single server is the quickest way of setting up the 
environment. This is often sufficient for smaller development teams (for the case study 
presented in Section 4, this worked well for a group of three people; the team shared the server 
for testing and compilation of the application, while editing of the code was mostly done on other 
machines. In addition to the group of three, the server was occasionally used by two other 
development teams at the same time   however, up to 5 concurrent developers did not pose 
any problem). 
To have multiple teams or people working under the same Tomcat process, all you need to do 
is add new contexts to the server.xml file (see example below). As long as Tomcat does not 
need to be restarted often (which is required to apply changes to the web.xml file), this can work 
well during development. By default, Tomcat allows for up to 50 concurrent threads, which is 
more than sufficient during development even with many team members. 
docBase="/devteam/andreas/deployHome"
debug="0"
reloadable="true"
trusted="false" >
docBase="/devteam/grace/deployHome"
debug="0"
reloadable="true"
trusted="false" >
Reference 
  
Gal Sachor; Tomcat   A Minimalistic User's Guide; 1999 
http://jakarta.apache.org/tomcat/jakarta tomcat/src/doc/uguide/tomcat_ug.html
76 




Java Web Hosting Application Development Using Java Technologies Hosting




 
TotalRoute.net Business web hosting division of Vision Web Hosting Inc. All rights reserved.