0

Ubuntu6.10 and BlueDragon 7 install and working, well, kinda.

Ubuntu

Well, I've made some progress here. Beside my not reading the documentation good enough about the datasourses, it's gone pretty good.

I've got Apache 2 and Blue Dragon 7rc installed. The admin page and built in webserver are working, but the Apache connector isn't working, yet.

So, here's what I've done so far. I found Adam Howitt's Blog about installing BD 7 with Apache 2.l2 on Draper Drake Ubuntu and a post on we3geeks explaining how to do this. Neither article uses the exact version numbers I have, but they are close.

So, i installed Apache 2 from the Synatics Package manager in Ubuntu, If your so new to Ubuntu that you don't know how to do this, email me or check out the Ubuntu forums . I'd love to help you with what I can.

Once I installed Apache, i tested it, and it worked.

I then downloaded BlueDragon. While it was downloading I read the BlueDragon 7 Installation guide. Personally, and don't laugh, you need to know more than me to follow the Linux instructions in that manual. we3geeks for me was much more helpful. Don't get me wrong, it's a good manual as far as manuals go, but the we3geeks is a bit more helpful for the install part.

 So, based on the the we3geeks article,I started to setting up the directory structure. Well, I'm still new enough on Linux that I've not created to many symbolic links.  So, just to make sure I was right I verified that my apache was located where is was supposed to be.  In my Ubuntu the 4 directories I was  concerned with were located here:

"/etc/apache2

/var/www <--document root

/usr/lib/apache2/modules

/usr/sbin/apache2 "

Once I verified where those directories were located I followed the we3geeks leading and typed in a terminal the following.

"sudo mkdir -p /usr/local/apache/bin
sudo mkdir -p /usr/local/apache/conf
sudo ln -s /etc/apache2/apache2.conf /usr/local/apache/conf/httpd.conf
sudo ln -s /var/www /usr/local/apache/htdocs
sudo ln -s /usr/lib/apache2/modules /usr/local/apache/modules
sudo ln -s /usr/sbin/apache2 /usr/local/apache/bin/httpd"

If for some reason your apache is located somewhere other than the from directories listed above, I think all you would need to do is put your paths as the first argument in the lines that start "sudo ln -s /"  Your local paths would be the first path listed, as the second path listed on each line in the path is the symbolic link?  Right?  LOL I told you I'm no linux guy.  now that is done, I moved to installing BlueDragon.  

In a terminal window I typed "sudo sh BlueDragon_Server_70_337-Linux.sh"

One note on the install, the article on we3geeks doesn't talk about it, but the BlueDragon Install guide does. You can install blue dragon in either GUI or console mode. Since I'm a GUI kinda guy, I chose the GUI instal.  If I would have done a console install I would have typed "sudo sh BlueDragon_Server_70_337-Linux.sh -i console"

The install was pretty uneventful.  I took the defaults on everything.  If you take the default on everything remember the number, 9999.  That's the Apache port number that BlueDragon talks to Apache on via the Apache connector. 

 At this point I restarted apache, then BlueDragon.

 " sudo /etc/init.d/apache2 restart" and then

"  cd /usr/local/NewAtlanta/BlueDragon_Server_70/bin/" <--Default BlueDragon Location

then " sudo StopBlueDragon.sh" 

then " sudo StartBlueDragon.sh"

 At that point, I tested the admin console by going to http://localhost:8080/bluedragon/admin.cfm in my browser.  it worked!  Cool.

 I then tried Apache by creating a very simple test.cfm page that set the time as a variable and outputs it.  Not so cool it didn't work. 

At this point it was 11:00 and I have to be up at 5am, so that where I stopped for now.

 That at least got me started.  BD is a least working.  So on to my next project of figuring out what I did wrong to make Apache not work with it.

I'm leaving for Colorado for a few days tomorrow and won't be able to mess with it until next week, but I'll update the status when i figure something out.

 Any help you guys could lend as a good place to start looking for the Apache problem I'd love to hear it!

 

Later,

Mark 

 

tags:
Ubuntu

Search