Latest Articles:
Committee Members:
Alert Email
Get a short email alert whenever a new entry is published.
Confidential, secure it's piece of cake to keep uptodate.
Updated preconfigured Jetty/OpenBD now available
We've made it even easier for you to get to grips with OpenBD with our preconfigured Jetty instance. Simply download, unzip and run and you are up and running. We've made some special changes to this Jetty installation to allow CFML developers get to the features they want quickly without having to figure out Jetty's setup.
The Jetty/OpenBD has proven to be one of the most popular ways for people to get their hands on OpenBD and start playing with it. Listening to feedback from the mailing list, people have enjoyed the speed at which they can get up and running, but felt confused when it came to setting up additional websites or virtual hosts. This new bundle addresses all those issues.
We've taken the latest Jetty version and stripped out all the bits that are unnecessary to the vast majority of CFML installations. We've rearranged the directory structure to make it obvious where all the pieces go, and most importantly, we've installed OpenBD into the root context, making CFML processing available to all websites and contexts.
What this means is a much reduced overhead when running multiple websites as there will only be one OpenBD instance running. You can quickly add new websites to this installation by editing a single file etc/jetty.xml and restarting. The big difference here, is how easy it is to specify document roots that fall outside of the Jetty runtime directory. This should make it very easy to point to an existing document root without having to copy it underneath Jetty.
Virtual hosts was another popular question that was asked. A virtual host is basically defining one or more HTTP/1.1 names that point to the same website or document root. You can now set these up very easily and quickly using the same etc/jetty.xml.
In this world a website is defined as a site that runs from a given document root, where as a virtual host is the symbolic name that you use to reach that website.
After downloading the distribution, simply unzip into a directory and open up a console (DOS window if on Windows) and navigate to that folder. There is a specific OpenBD readme file sitting there with detailed instructions on how to add more websites and configure OpenBD.
As per the previous installations, to startup OpenBD on Jetty simply type java -jar start.jar and up it will run. If this fails to run, make sure you have at least Java 1.5 installed on your machine and its properly plumbed into the path.
Remember, this is a complete solution. There is no requirement to put a additional web server on the front. Apache is not required and irrespective of what you have heard about static content and performance, Jetty is more than up for the task of serving up millions of images without any hassle.
Head over to the download to get the latest files.
Comments (4)
When starting the package using java -jar start.jar it seems to hang. The following lines appear before it stops though..
2008-11-19 13:07:28.239::INFO: Logging to STDERR via org.mortbay.log.StdErrLog 2008-11-19 13:07:28.517::INFO: jetty-6.1.12rc1 2008-11-19 13:07:31.463::INFO: Opened /usr/src/jetty-6.1.12-OpenBD/logs/2008_11_19.request.log 2008-11-19 13:07:31.483::INFO: Started SelectChannelConnector@0.0.0.0:8080 ..then when I try to access the dump.cfm page I get a Jetty-generated 404 error page. Any ideas what I might have done wrong? ThanksCurrently a bug is open for the issue above here: http://code.google.com/p/openbluedragon/issues/detail?id=62
It seems to work pretty good on Ubuntu 8.04, I was able to run the files under cfmlWebContext_2 just fine. But when I placed a simple "testme.cfc" in the dir and tried to load testme.cfc?wsdl, it threw a Open BlueDragon Internal Server Error: "java.io.IOException: /opt/jetty-6.1.12-OpenBD/webroot_cfmlapps/cfmlWebContext_1/WEB-INF/lib/webservices.jar does not exist and is needed to compile web service type." (That's correct, I was running cfmlWebContext_2 and the error referenced cfmlWebContext_1) That's obviously not where the jars are, they are under jetty-6.1.12-OpenBD/lib/openbd.
@Xoundboy--the Jetty startup process will stop at that point so that doesn't mean it's hung. It doesn't return to a command prompt in other words, and you hit ctrl-C to kill the process.
As for why the dump throws a 404, what URL are you using? It should come up if you hit http://localhost:8080/dump.cfm