Skip to main contentdfsdf

  • Railo + Tomcat + Apache

    How to configure all three in a series

    •  
       Today, let's get Railo running on Tomcat! Why Tomcat? It's a robust, high-performance Java-based web server and Servlet engine and it's also very light and lean. Tomcat is also the basis of the JBoss Web Server (I'll probably cover JBoss later in this series) so all that you learn about getting things up and running on Tomcat can be carried over to JBoss when you need a full JEE server rather than "just" a Servlet engine.
      • This describes how to get Railo running on Tomcat -- a Java Servelet Engine.
        Q: what is the difference between a full JEE server than just a servlet engine

    • If you're still in the bin folder, you can start Tomcat by typing:

      sh startup.sh
      or:
      ./startup.sh
      You should just get four lines of output saying which paths it is using. That's it, Tomcat is running!
      • Note: the startup.bat file calls the catalina.bat, which must have a reference to the jdk. usiing the JAVA_HOME environment var.

        set JAVA_HOME=C:\Program Files\Java\jdk1.6.0_13

      • for windows this startup.bat.

    4 more annotations...

  • Sep 06, 09

    After setting up Railo and Tomcat, this article shows how to make it more production friendly like making Ralio the root web application and making it run over port 80

    •  
       After getting a very basic Railo+Tomcat setup running, now we're going to make it more robust and more 'production-ready' (you'll want to do more than I'm going to show so I'd refer you to the extensive Tomcat documentation for deeper configuration). I'm just going to show how to get Tomcat integrated with Apache in a couple of ways so you can run a 'real' website on it.
      • After setting up Railo and Tomcat, this article shows how to make it more production friendly like making Ralio the root web application and makiing it run over port 80

    • , I renamed the ROOT folder, under webapps, welcome (you could - and probably should - remove it altogether on production). Then I renamed railo to ROOT.

    7 more annotations...

  • Oct 17, 09

    "In the comments on Part IV, Barney suggested using AJP to proxy and I confirmed that it preserves the CGI variables REMOTE_ADDR and REMOTE_HOST which Paul Kukiel asked me about. Paul also noted that adding the ProxyPreserveHost directive causes the host headers to be passed through the proxy. I'd actually added that locally but didn't want to complicate the blog post by mentioning it.\n\nIn this Appendix post, I want to tackle SES URLs. One downside of Tomcat is that it does not support the following common form of SES URLs: "

    • Tomcat can't find Java. You can either set a JAVA_HOME environment variable, or you can explicitly tell Tomcat where to find Java by adding the JAVA_HOME location to the catalina.sh script in the bin directory. Open catalina.sh in your favorite text editor, and after the big block of comments at the top of the file (denoted with # signs), add the following line:

      JAVA_HOME=/path/to/your/jdk

      • Copy the WAR file to /path/to/tomcat/webapps. In this case since the file name includes the version number, I did a cp railo-3.0.2.001.war /path/to/tomcat/webapps/railo.war, which will make the context path "railo"

    9 more annotations...

1 - 5 of 5
20 items/page
List Comments (0)