Now you have downloaded the Open BlueDragon Jetty Ready2Start package and read the Read-Me and you get errors trying to start it that looks like this:
sh-3.2# java -Mx512M -jar start.jar
Unrecognized option: -Mx512M
Could not create the Java virtual machine.
It looks like that MacOS X handles this a little bit different. Thus you will want to start it with the following commands:
java -jar -Xmx512M start.jar
If you enjoyed this post, make sure you subscribe to the RSS feed!
Thanks for the suggestion, but for OSX users it may be easier to run JBOSS and just drop the war file into the deploy directory.
Or Tomcat for that matter
Exactly. Given that Tomcat is at the core of JBoss that’s to be expected.
Right now I’m running an exploded war of the developers version of blue dragon for j2ee on my macBook at home. Its much easier than the Jetty option. Also given that Apache is integrated into OSX, its very easy to set up mod_jk and run Tomcat/JBoss via Apache.
regards,
larry
Yes, I also deployed Tomcat on MacOS X and configured Apache to route to Tomcat for some applications. Works perfectly.
Just one thing hits me a little strange: Does each of my application has to have a bluedragon and a Web-Inf folder with all the configuration, drivers, etc in it? Isn’t there a “global CFIDE” so to say?
Remember what you have there, each application in your configuration is a separate BlueDragon instance. To do what you want you need to use an exploded war. I’m not sure how it works with Tomcat, since most of my experience has been with JBoss, but I imagine it should be similar. I just had a quick look through the Tomcat manual and it does handle exploded war directories.
What follows are what I use with JBoss:
Name your folder something appropriate, (I use BD.war) but make sure you have .war as part of the folder name.
Put the bluedragon and Web-INF directories into that folder.
In the WEB-INF folder, create a new xml file called jboss-web.xml - this file tells jboss what to serve. The contents should look something like this:
/
Note you’ll need to find the equivalent for Tomcat, but in the sections I read of the website, it looks like you can use something similar.
The jboss-web file tells JBoss to serve the app off the context root. However, if you want this war directory to be a subdirectory off of your root, you would specify that subdirectory name in the jboss-web.xml file, as in
/foo
Essentially that’s all you have to do. Then to serve multiple apps, all you have to do is drop the directory containing your app files (cfm’s, htm’s and media files) into your exploded war folder in the deploy directory.
sorry about that, it looks like your blog app rejected the xml snippets I included.
Inside the jboss-web The contents should look something like this:
<jboss-web>
<context-root>/</context-root>
</jboss-web>
and if you want to serve it off a subdirectory off your context root:l
<jboss-web>
<context-root>/foo</context-root>
</jboss-web>
Ok, I have not found the equivalent of the XML file (yet) but just one question before:
Couldn’t I just take the openbluedragon.war file, rename it to “myapplications.war”. Starup Tomcat, it will create a “myapplications” folder for me and deploy all my applications in that folder then?
Sorry, but the J2EE server stuff it rather new currently.
I believe so yes. That’s basically how I deploy on my dev box. Given that Tomcat can handle exploded wars, you should be able to do that without too much trouble.
Sorry I misread your post. From what I understand, you have to explode the war file, rename that to myapplication.war and then deploy the exploded directory with your apps in each of its own subdirectories.
Ok. understood. But then when there is a new version of bd we will have to update each instance. I highly doubt that this is “good practice”, or?
Not really, in your wepapp directory you’d have something like this:
/webapp
/openbd.war
/app1
/app2
/bluedragon
etc.
In the web applications named app1 and app2, the only files in there would be the .cfm and the other web files. When upgrade time comes you’d stop the server, then replace the /bluedragon directory and the web.xml file in the /openbd.war directory.
That said there are a number of advantages to having separate bluedragon instances for each app. For instance if one app takes down its instance, the other ones keep serving .cfm files without going down themselves. It also allows for differing security contexts etc.
One thing, the /app1, /app2 and /bluedragon directories would reside under the /openbd.war directory.