This is a documentation task, with the help of which it should be easy to configure project.net in production mode using Apache+Tomcat

Production installations of project.net needs to completly use facilities provided by Apache and Tomcat. Optimal deployment architecture and parameter configuration has huge impact on performance of project.net in production deployments.

If the test server deployment of project.net is similar to production deployments, it will probably help test the performance of project.net

following are some of the deployment architecture points may need to consider for preparing the production setup

1. Apache should tunnel traffic to tomcat ajp3.0 port (not to http port)
2. Apache should use ProxyPreservHost? On
3. All static content shall be served by Apache (js/css/images etc)
4. Apache shall be configured to use tomcat in cluster mode

• Must for production servers, cluster can be between two or more instances of tomcat running on same server on different ports.
  
• this avoid any downtime because of any single tomcat crash etc.
  

5. SSL shall be configured within Apache, so that ssl cpu load is shared by Apache and tomcat is free from any ssl processing (production has ssl config in its own config files)
6. configure/tune Apache for high loads, increase maxClients, thread values etc
7. Run tomcat and httpd on separate servers in separate DMZ, for higher level of data security.