I am moving lots of websites from Resin 3 to Tomcat 7 (centos 4/apache 2.20) and I am battling to determine which kind of configuration matches my needs. Particularly:

  • proxy_ajp versus mod_jk versus mod_proxy for passing demands to Tomcat/Railo
  • automating deployment of recent sites
  • putting WEB-INF outdoors the website roots (to simplify cloning sites)
  • using apache itk with tomcat so each vhost runs like a different user and process
  • getting just one shared railo server administrator config
  • support for SES Web addresses without any extension (ie: /path/to/page)
  • SSL support needed

I have read lots of howtos already but many are outdated or provide conflicting advice. I must see some good examples from individuals who run many railo vhosts and deploy them instantly or programmatically. Generally I'd prefer efficiency/speed over simplicity as I wish to get the most from limited assets.

I possibly could have requested these questions individually however i want to be certain any solutions consider all of the above factors (presuming the needs are really compatible).

first of all, browse the vivotech contractors - they're a webhost, so use their contractors as the base, they're perfect. (it uses tomcat)

railo 3.3 causes it to be a great deal simpler to deploy contexts from admin, so scripting this should not be very difficult.

  • web-inf ought to be instantly put in a website when it's defined in tomcat
  • should you give each user a brand new context-root, then they're going to have their very own admin
  • every webserver (apache/iis2k8/even tomcat) supports url-rewrite
  • everything supports ssl

  • you could also want to check out how you are likely to tune your jvm's with this senario, then perform some load testing to determine the way they fare.

  • drop an e-mail to sean corfield, google railo and the title and you will get his email.