One of Pivotal’s field engineers, Dan Carwin, recently began a series of posts breaking down differences between Pivotal tc Server and Apache Tomcat. In this post, we outline the five key configuration differences that Dan reported on with more detail. The upcoming, second post will cover the second category of differences—extensions to functionality.
The five key differences in configuration with Apache Tomcat and tc Server:
Multi-instance Support with Shared tc Server Binaries
Variable Substitution for Consistent Configuration and Port Management
TC-Native (compiled C) Connectors
Priority One—Interchangeable Runtimes
Most importantly, tc Server has been designed to be completely interchangeable with Tomcat—you can run the same codebase on either one, and we provide a 100% compatibility guarantee. The tc Server engineering team includes Apache contributors, committers, and team members—we are part of the community and know that integrity here means that our version must be completely interchangeable. Since we have been supporting Tomcat since 2001 (version 3.x), we can stand by our word.
About the Differences in Configuration
Anyone who wants to make configuration changes to the ASF's Tomcat can do so, and you might see that this list includes some of the same configuration changes that you have already done. Of course, we run into many people who aren’t aware of the options. Each of these five items helps take Tomcat to another level of enterprise readiness—together, they make it easier for admins, improve scale, and enhance security.