![]() ![]() If you see errors, the most likely culprit is that Tomcat can’t find Java. Using JRE_HOME: /usr/share/java/jdk1.6.0_11Īs long as you see something similar everything’s likely fine. Using CATALINA_TMPDIR: /home/mwoodward/apache-tomcat-6.0.18/temp Using CATALINA_HOME: /home/mwoodward/apache-tomcat-6.0.18 Using CATALINA_BASE: /home/mwoodward/apache-tomcat-6.0.18 Once you’re in the bin directory, run the startup.sh script (./startup.sh) and you’ll see some output similar to this: (Note that all of this runs perfectly well on Windows, and though I would never recommend using Windows for anything, you do not have to use Linux to get any of this to work.) For example if you unzipped Tomcat to /home/yourname/apache-tomcat-6.0.18, you would navigate to /home/yourname/apache-tomcat-6.0.18/bin. To start Tomcat, open a terminal (or DOS window if you must …) and navigate to your Tomcat directory, then the bin directory. If you have your Java environment set up correctly Tomcat should find Java fine and fire right up. Oh wait, I forgot–there is no install process! All you have to do is start Tomcat after you unzip it. After the download completes, unzip the file you downloaded. As of this blog post the latest version is 6.0.18, and you’ll want the “Core” binary distribution. Chances you won’t need to do most of these steps, and once Tomcat’s running the CFML piece of this puzzle is dead simple.įirst, download Tomcat. ![]() So, if the following looks complicated, it’s really only because I’m outlining how to get the Java settings correct if you need to worry about it. ![]() I’m assuming you already have Java installed, and I recommend Java 1.6 updater 10 or later (updater 11 is the latest) since previous versions had a bug that makes CFC instantiation horrendously slow. The only even remotely tricky part is installing Tomcat (and in most cases it isn’t tricky at all), so let’s tackle that first.Īs an aside, if you just want to try Open BlueDragon and don’t want to bother with the Tomcat installation, just download the Ready2Run Jetty + OpenBD distribution, start Jetty, and you’re done! And I think you’ll see in this blog post that “installing” CFML engines on Tomcat is actually easier than installing ColdFusion. This to me makes far more sense than letting ColdFusion and JRun dictate your Java environment. Yes, it makes it easy to install and configure ColdFusion, but in my opinion it also shields people from how Java web applications actually work, so I’ve become a big fan of treating ColdFusion like what it is: a Java web application. So why not use JRun? Well, aside from the fact that JRun is getting very long in the tooth at this point, personally (and you’ll probably hear me say this in a couple of conference presentations this year), I think the ColdFusion model stands Java on its head a bit, particularly when you do a standalone install of ColdFusion. I figure I’ll throw mine out there as well because the more information available the better. Great minds think alike because coincidentally enough, Dave Shuck also has just published two blog posts ( part 1, part 2) about setting up a similar environment. Note that this approach will work equally well on Jetty, JBoss, GlassFish, or more or less any servlet container or JEE server you choose. As a corollary to Sean’s post about running Railo, OpenBD, and ColdFusion on JRun, I thought I’d outline my preferred development environment these days, which is to run all the necessary CFML engines on Apache Tomcat. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |