This forum is now a read-only archive. All commenting, posting, registration services have been turned off. Those needing community support and/or wanting to ask questions should refer to the Tag/Forum map, and to http://spring.io/questions for a curated list of stackoverflow tags that Pivotal engineers, and the community, monitor.
tc Server is built on Apache Tomcat so the same architectures that work with Tomcat will work with tc Server. The right architecture will depend on what you are trying to achieve but as a rough guide:
- load balancing is usually achieved using httpd or a hardware LB
- if using httpd and you are familiar with mod_jk use that
- if using httpd and you are not familiar with mod_jk use mod_proxy_http
- enable sticky sessions
- consider if the benefit of clustering is worth the additional configuration complexity and processing overhead - often it isn't
- it is often worth disabling connection pooling between http and tc Server
For deployment with tc Server I'd always use AMS. It provides simple deployment to multiple tc Server instances. If you need something more flexible then take a look at the AMS command-line client.