DetailsDotAt wrote:
I find it frustrating and dissapointing that a clear cut installation guide for running OpenBD on an IIS server hasn't been generated yet. People at NewAtlanta who support this should have done this along time ago.
Well, two things. First, as you've seen from some other posts there is information out there. Point well taken, however, that we need to consolidate and get things on the wiki.
Second, this is an open source project with a small handful of people working on it. Believe me, we do everything we can with the time we have available and frankly in my experience there's far more responsiveness here on most issues than from the commercial software companies I've worked with.
The whole point for Bluedragon originally was as an alternative to Coldfusion Server, as least that's what I thought.
And it is. I understand you're frustrated and we'll help as best we can.
I shouldn't have to be feeling I need to spearhead some big movement to get OpenBD running on IIS.
I feel that I need to clarify again that you're looking to get *Tomcat or Jetty connecting to IIS*, not get OpenBD *running on* IIS. That may come off like it's just semantics, but since it seems to be a point of confusion I think it's an important distinction to make.
OpenBD is just a Java application. So to get IIS in the mix you'd follow the exact same steps as you would getting any Java servlet container/JEE server connected to IIS.
All this Install Tomcat on Jetty on Java on Tomcat in Jetty running with Java using Bluedragon on Windows running Jetty using Java stuff is confusing me (considering I'm at work trying to fit working on this in with the rest of my non related activities).
Doesn't need to be confusing. 1. Install Java 2. Install Tomcat/Jetty 3. Deploy OpenBD on Tomcat/JettyAt this point you have things running on port 8080. After that you can do one of the following: 1. Use the web server that is built into the servlet container/JEE server as your web server by changing the port it runs on to 80 and configuring your virtual hosts accordingly. OR ..
2. Use Apache as your web server. OR ... 3. Use IIS as your web server. (Yes, we need documentation.)I have a lengthy blog post about all of this with Apache on Windows server here:
http://bit.ly/3NHyhzAnd I did a presentation on the CF Meetup last week that may help with the first piece of this puzzle:
http://experts.na3.acrobat.com/p13033917/Note that in the presentation I did not have time to cover web server connectivity, but I think it will definitely help better understand how all the pieces fit together.
Part of the reason I did that presentation is because I think ColdFusion has shielded people from how Java web applications work for a very long time, but now with OpenBD available people are having a bit of a learning curve with the Java configuration side of it that CF does for you. The good news is it really isn't complicated at all, and once you get the hang of it you'll have a tremendous amount of flexibility with your setup.
So, all this being said, believe me--we hear you and see the need for more/better help with Windows/IIS. Going back to my earlier point, this is an open source project and we do rely on members of the community assisting with their knowledge when possible. That's the only way open source thrives.
I hope that helps a bit and I'll do everything I can this week to dig into this and get some solid documentation on the wiki, or if there's someone with more Windows experience than I who can contribute documentation, it would be greatly appreciated.
Matt -- Matt Woodward [email protected] http://www.mattwoodward.com/blogPlease do not send me proprietary file formats such as Word, PowerPoint, etc. as attachments.
http://www.gnu.org/philosophy/no-word-attachments.html
smime.p7s
Description: S/MIME Cryptographic Signature
