There is no denying the fact that Tomcat is the most beloved application server amongst software professionals and application developers who are plying their trade in the server side universe. Not only is Tomcat the go-to test engine for coders who are looking to quickly test applications that might be deployed to a commercial server such as WebSphere or Weblogic, but it has also become the foundation for various open-source offerings such as the VMware vFabric tc Server. Whether it's being used purely as a test environment, or as a fully clustered production system, every developer working within the Java ecosystem must be familiar, to some extent, with this incredibly popular servlet engine from Apache.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
For those who are interested in honing up their skills with the latest version of the Tomcat server, TheServerSide has an excellent screencast tutorial that takes IT professionals of all stripes through the various steps required to download, deploy and test the installation of version 7:
Of course, there are a variety of different ways to configure Tomcat, and a common mistake system administrators make is using the same Tomcat settings on the server as they would with a default installation on a desktop machine. This set of tips from Lukas Stewart identifies they key elements of the settings.xml file that need to be tweaked to get the best performance out of a Tomcat installation running on a server.
Once Tomcat is up and running, an administrator will want to make sure the environment is running as efficiently as possible. One quick change an administrator can safely make on their installation is to consolidate the various log file handlers so that fewer instances are running on the production machine. This second tip from Lukas Stewart demonstrates how to do just that:
And finally, administrators will want to take a quick look at the following tutorial that demonstrates how to configure the Tomcat server to ensure that application developers don’t accidentally push applications into production that are optimized for development. Many frameworks, like JavaServer Faces and Spring, have tweaks that make development and debugging easier, but these settings can significantly degrade performance if they find their way into the production environment. The following tip demonstrates how the Tomcat server can be configured to ensure that resource depleting development settings never get deployed to a production machine:
The Tomcat server remains popular because if its simplicity and ease of use, and by using these tips and tutorials, system administrators and application developers who are using this popular Apache project will ensure that they are getting the most out of this beloved, open-source tool.