Java Tomcat 与 Pivotal tc 服务器

Tomcat vs Pivotal tc Server

提问by Steve Chambers

Could anyone advise as to the pros and cons of using Pivotal tc Server as opposed to just vanilla Tomcat for a Spring-MVC Java web application? Could find very little about Pivotal other than on their websiteand the fact it's packaged as part of the Spring Tool Suite. This lack of info is making me a bit wary about being dependent on it...

任何人都可以就使用 Pivotal tc Server 而不是使用普通 Tomcat 的 Spring-MVC Java Web 应用程序的优缺点提出建议吗？除了在他们的网站上以及它被打包为 Spring Tool Suite 的一部分之外，几乎找不到关于 Pivotal 的信息。缺乏信息让我有点担心依赖它......

Background:Am preparing the development environment for a Spring-MVC project and currently evaluating whether to use the packaged Spring Tool Suite (STS)or just start with the latest Eclipse (possibly combined with the Eclipse STS plugin). Came across Pivotal tc Server as one of the optional components in this plugin.

背景：我正在为一个 Spring-MVC 项目准备开发环境，目前正在评估是使用打包的Spring Tool Suite (STS)还是从最新的 Eclipse（可能结合Eclipse STS 插件）开始。作为此插件中的可选组件之一，遇到了 Pivotal tc Server。

采纳答案by Carwin

Pivotal tc Server contains all of vanilla Tomcat, and has a few optional extensions designed to make it easier to deploy and maintain. Broken out into three groups, the diff looks like this:

Pivotal tc Server 包含所有 vanilla Tomcat，并有一些可选的扩展，旨在使其更易于部署和维护。分为三组，差异如下所示：

Configuration extensions (No altered code, just config changes we implement)

配置扩展（没有改变的代码，只是我们实现的配置更改）

• Multi-Instance using shared binaries
  • Trivial to change Tomcat versions while preserving app and configuration
• Variable Substitution in config files
• Async Logging
• Mild Security Tuning (ports, mgmt apps, JMX)

• 使用共享二进制文件的多实例
  • 在保留应用程序和配置的同时更改 Tomcat 版本很简单
• 配置文件中的变量替换
• 异步日志记录
• 轻度安全调优（端口、管理应用程序、JMX）

Code Extensions

代码扩展

• Patch version releases – fix flaws in current release [e.g. tomcat-7.0.32.B.RELEASE]
• Extended JMX interface
  • Additional Metrics
  • Application Deployment
• Diagnostics Valve - good troubleshooting info when there's a slowdown
• Config Templates – including custom-created
• Change log level on the fly
• Advanced Session replication (Gemfire)
• Oracle DB Connection Proxy

• 补丁版本发布 – 修复当前版本中的缺陷 [例如 tomcat-7.0.32.B.RELEASE]
• 扩展的 JMX 接口
  • 附加指标
  • 应用部署
• 诊断阀 - 出现减速时的良好故障排除信息
• 配置模板——包括自定义创建
• 即时更改日志级别
• 高级会话复制 (Gemfire)
• Oracle 数据库连接代理

Add-Ons

附加组件

• Windows Service Wrapper
• RPM / Apt-Get / Debian installers (linux)
• Startup scripts (linux)
• Chef Recipes
• Puppet Scripts
• Password Encryption
• Spring Insight for performance tuning

• Windows 服务包装器
• RPM / Apt-Get / Debian 安装程序 (linux)
• 启动脚本 (linux)
• 厨师食谱
• 傀儡脚本
• 密码加密
• 用于性能调优的 Spring Insight

FYI on the tag thing, there's still the old "springsource-tc-server" tag. SpringSource is now Pivotal. (Can/should we update the tag or add a new one?)

仅供参考，标签方面仍然存在旧的“springsource-tc-server”标签。SpringSource 现在是 Pivotal。（我们可以/应该更新标签还是添加一个新标签？）

Hope this helps.

希望这可以帮助。

回答by Makarand.Thorat

SpringSource tc Server is an enterprise version of Apache Tomcat, the widely used Web application server. SpringSource tc Server is hardened for enterprise use and is coupled with key operational capabilities, advanced diagnostics, and is backed by mission-critical support.

SpringSource tc Server 是广泛使用的 Web 应用服务器 Apache Tomcat 的企业版。SpringSource tc Server 已针对企业使用进行了强化，并结合了关键操作功能、高级诊断功能，并由关键任务支持提供支持。

SpringSource tc Server is designed to be a drop in replacement for Apache Tomcat, ensuring a seamless upgrade path for existing custom-built and commercial software applications already certified for Tomcat. Maintaining this level of compatibility enables our customers to add the business-critical functionality they need to more effectively run and manage their applications with the least amount of effort.

SpringSource tc Server 旨在替代 Apache Tomcat，确保现有定制和商业软件应用程序的无缝升级路径已经通过 Tomcat 认证。保持这种级别的兼容性使我们的客户能够添加他们所需的关键业务功能，从而以最少的努力更有效地运行和管理他们的应用程序。

find more information at http://static.springsource.com/projects/tc-server/6.0/getstart/cgsdiffs.html

在http://static.springsource.com/projects/tc-server/6.0/getstart/cgsdiffs.html找到更多信息

回答by Kyle Walker

This doesn't answer your question about the pros and cons, but I found this site really helpful in getting tc server up and running in STS. http://sosiouxme.wordpress.com/2012/04/06/the-missing-guide-to-creating-and-modifying-tc-server-instances-for-sts/

这并没有回答您关于优缺点的问题，但我发现这个站点对于在 STS 中启动和运行 tc 服务器非常有帮助。http://sosiouxme.wordpress.com/2012/04/06/the-missing-guide-to-creating-and-modifying-tc-server-instances-for-sts/

回答by Beezer

To me it seems a high price for just getting a servlet container. Specifically, it (the tc server) seems to try to mimmic a production quality application server (servlet engine) with the added features. For development it seems overkill. You could just as well use Tomcatstand-alone or Glassfishor Jetty.

对我来说，仅仅获得一个 servlet 容器似乎是一个高价。具体来说，它（tc 服务器）似乎试图模仿具有附加功能的生产质量应用程序服务器（servlet 引擎）。对于开发来说，这似乎有点矫枉过正。您也可以单独使用Tomcat或Glassfish或Jetty。

I would choose the tc serverif my target was some cloud implementation of Cloud Foundary that was ultimately my target production deployment environment.

如果我的目标是 Cloud Foundary 的某个云实现，最终是我的目标生产部署环境，我会选择tc 服务器。

Finally, I just noticed that the tc serveris a commercial offering. So, the licensing implications should the features become integral to your delivery, might have a cost that your project would not bear: https://www.cdw.com/shop/products/SpringSource-tc-Server-Spring-Edition-license/2156278.aspx

最后，我刚刚注意到tc 服务器是一个商业产品。因此，如果这些功能成为您交付不可或缺的一部分，许可影响可能会产生您的项目无法承受的成本：https: //www.cdw.com/shop/products/SpringSource-tc-Server-Spring-Edition-license /2156278.aspx