Setting up OpenBD on Centos with support for virtual hosts

I needed to set up a development platform that could serve different dev projects on separate subdomains with several of them using openBD to handle .CFM templates. My chosen platform is Centos 5.5 using the Apache 2.2 web server.

I first tried doing this over a year ago and spent quite a while reading through the various documentation provided by the openBD community but never managed to get it to work. Recently my hosting company (Vivio Technologies) changed their pricing and suggested that I switch from BlueDragon Server JX to OpenBD so I decided to have another go setting up my dev platform so I can test the CFML apps I have running there with openBD before making the switch on the production server.

Since my last attempt the installation process has been made a lot easier due to the OpenBD installer packages created by Jordan Michaels.

I started by installing a fresh VM with Centos 5.5, configuring a couple of subdomains as virtual hosts and creating their respective document root folders under /www. Then, by just running the installer (openbd-1.3-pl0-linux-installer.bin) and accepting all of the default options, I was able to get openBD to successfully serve its demo pages which are contained in the Tomcat webapps/ROOT folder by browsing <CentosVM IP address>/demo/cfdump.cfm.

OpenBD demo page <cfdump>

I also got the openBD administrator by browsing <CentosVM IP address>:8888/bluedragon/administrator/index.cfm

openBD administrator

The next stage, getting virtual hosts was not quite so straightforward. There are some really good instructions on the OpenBD Wiki. The salient point here is that the server.xml file in the tomcat’s conf folder needs to have entries made for each virtual host in much the same way as the httpd.conf file does. But on my first attempt at doing this, something went wrong and I kept getting ‘Service Temporarily Unavailable’ errors from the browser when trying to browse a CFM page from a virtual host. I ended up rolling back my VM to a previous snapshot and reinstalling openBD. This time I re-added the virtual host to the server.xml file and it worked. Now, finally after over a year of trying I have a working dev server that uses OpenBD to parse CFM files and I can get on with the next steps….testing my CFML apps and then deploying them to an OpenBD production server and in the process save myself $10 a month for the BlueDragon Server JX license fee. :)

Update: I wrote this shell script that automates the addition of new virtual hosts

Starting and Stopping Bluedragon Server JX from the command line

Assuming that Bluedragon has been installed in the default way then there should have been an “rc” standard script created in the the /etc/init.d folder so that means the server can be started and stopped using the following command:

# service BlueDragon_Server_JX {start|stop|restart}

Using chkconfig to control init scripts in Centos

chkconfig is a very useful utility that allows you to quickly deploy the symlinks in the various rc directories that control what gets launched at boot time and shutdown when powerinf down.

To add or remove an init script to a run level is very easy with the chkconfig command. Here are some useful examples:

1. To list the current configuration of all init scripts:


chkconfig --list

produces output such as…

[root@CentosOpenBD3 ~]# chkconfig --list
NetworkManager 0:off 1:off 2:off 3:off 4:off 5:off 6:off
acpid 0:off 1:off 2:on 3:on 4:on 5:on 6:off
anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off
apmd 0:off 1:off 2:on 3:on 4:on 5:on 6:off
atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off

... etc

2. To find out if a service is set currently configured to be launched at boot time in the current runlevel:

chkconfig mysqld

3. To add a script to run levels 3,5 4 & 5

chkconfig --level 345 mysqld on

(just use ‘off’ instead of ‘on’ if the script shouldn’t be run at that run level)

4. To remove a script

chkconfig --del mysqld

Install CFMX7.0.2 / Apache2.2 / Centos5.2 / Virtual PC 2007

I’ve just spent the last two days preparing a new development environment on a Virtual PC 2007 VM for the application I’m currently building.
The idea behind this setup is that it mirrors as closely as possible the production environment which is CFMX7.0.2 / Centos 5.2 / Apache 2.2.

It took a lot of abortive attempts to get this right but I finally managed it with the help of the very well written walkthrough by Bill Mitchell which itself refers greatly to another blog post by Steve Erat. Mr Mitchell’s guide is great – it covers several different methods of installing the Apache connector in CFMX7 – he can take all of the credit for this, in fact I copied large sections of his procedure (thanks Mr Mitchell :)).

So I’m going to now give a set of precise instructions on how to set up and configure this dev environment that should work first time. I’m also going to be a bit naughty and provide the wsconfig file for download off my server – this will save some more time.

  1. Begin by installing Centos 5.2 on a virtual machine running in Virtual PC – make sure to use “text mode” for the installation as VPC doesn’t support 24bit graphics and will not display the installer properly.
  2. Once installed, open the ports you need in the Centos firewall
  3. Install LAMP (Apache, PHP & MySQL) using Yum (see this article for details).
  4. Reboot the server and check that everything works properly so far. Once you’re sure it is then it is a good time to enable undo disks in VPC as the next phase of the install can go wrong and if it does you can just revert back to this safe position and try again. To enable undo disks:
    1. shut down the virtual machine
    2. in the VPC console open the VM’s settings
    3. select undo disks (6th item) and enable it
    4. restart the VM
  5. Download the coldfusion-702-lin.bin installer from the Adobe download site – on the main Coldfusion download page you will need to click the "related downloads" link to find the correct download
  6. Disable Selinux (find out how here)
  7. Install libXp
    yum install libXp
  8. Add a coldfusion runtime user
    adduser username
  9. Rename the binary installer
    [root@machine]# cp coldfusion-702-lin.bin coldfusion-702-lin.bin.backup 
  10. Use the following string replace command on the binary to comment out a line that causes problems
    [root@machine]# cat coldfusion-702-lin.bin.backup | sed "s/export LD_ASSUME/#xport LD_ASSUME/" > coldfusion-702-linux.bin 
  11. Make the modified binary executable
    [root@machine]# chmod 755 coldfusion-702-lin.bin 
  12. Execute the installer and select the “Built-In Webserver” option (don’t worry this will be replace with Apache later) IMPORTANT – DON’T LAUNCH THE COLDFUISON SERVER YET – if you do then you’ll have to start all over again.
  13. Open the /opt/coldfusionmx7/runtime/servers/coldfusion/SERVER-INF/jrun.xml file and
    1. Find the entry labeled ProxyService
    2. Add <attribute name=”deactivated”>false</attribute> (changed from true)
    3. Find the entry labeled WebService
    4. Add <attribute name="deactivated">true</attribute> (changed from false)
    5. Find the entry cacheRealPath
    6. Add <attribute name="cacheRealPath">true</attribute> (changed from false)
    7. Save the file
  14. In /opt/coldfusionmx7/runtime/lib/ create a directory called ‘wsconfig’
  15. In /opt/coldfusionmx7/runtime/lib/wsconfig create a driectory called ’1′ (one)
  16. In /opt/coldfusionmx7/runtime/lib/wsconfig create a file called wsconfig.properties and populate it with:
    #JRun Web Server Configuration File
    # edited by bill 10.31 Thur May 24
    1=Apache,/etc/httpd/conf,"","",""
    1 .srv=localhost,"coldfusion"
    

    and save the file

  17. In /opt/coldfusionmx7/runtime/lib/wsconfig/1 create a file called jrunserver.store and populate it with:
    proxyservers=127.0.0.1:51011 The 51011 is for ColdFusion MX 7:
  18. Download this file and place it into the /opt/coldfusionmx7/runtime/lib/wsconfig/1 directory
  19. Change ownership of the wsconfig directory and its contents to the coldfusion user:
    chown -R <coldfusion user> /opt/coldfusionmx7/runtime/lib/wsconfig

    for example, I created a user named ‘coldfusion’ so I entered:

    chown -R coldfusion /opt/coldfusionmx7/runtime/lib/wsconfig

    (when you manually create this folder / file structure everything will be owned by the root user. This will cause problems when Apache attempts to connect to coldfusion – hence the above step)

  20. Edit the httpd config file:
    vi /etc/httpd/conf/httpd.conf

    and find the line containing DirectoryIndex. Add index.cfm to the list of default file names so it should now look something like this:

    DirectoryIndex index.html index.html.var index.cfm

    and then append the following section to the end of the file and re-save it:

    # JRun Settings
    LoadModule jrun_module /opt/coldfusionmx7/runtime/lib/wsconfig/1/mod_jrun22.so
    
    JRunConfig Verbose false
    JRunConfig Apialloc false
    JRunConfig Ssl false
    JRunConfig Ignoresuffixmap false
    JRunConfig Serverstore /opt/coldfusionmx7/runtime/lib/wsconfig/1/jrunserver.store
    JRunConfig Bootstrap 127.0.0.1:51011
    #JRunConfig Errorurl 
    AddHandler jrun-handler .cfm .cfml .cfc .jsp .jws .cfr .cfswf
    
    
  21. Create a symlink to the CFIDE folder in the document root:
    cd /var/www/html
    ln -s /opt/coldfusionmx7/wwwroot/CFIDE
  22. Restart the apache server
    [root@machine ~]# service httpd restart 
  23. Start the Coldfusion server
    [root@machine ~]# service coldfusionmx7 start 
  24. Test everything works properly by putting an index.cfm containing some CFML scripting (eg <cfdump var=”#CGI#”>) into the apache web root and type:
     http://centos-VM/index.cfm

    You should see the CGI dump. Then test the coldfusion administrator works

    http://centos-VM/CFIDE/administrator

    where centos-VM is either a domain that you’ve set up for your new VM or its IP address on your LAN

  25. Now you should have a fully working virtual Centos server with CFML (& PHP) support. Don’t forget to install the MySQL connector J Driver too – I already blogged that one here

    Finally you really should should close the VM saving the changes. Before re-launching the VM I would recommend that you copy the VM folder to an archive location – you never know when you might need a freshly installed VM with this environment in the future. Leaving undo disks enabled in Virtual PC is a good idea if you can afford the extra disk space required – if you do break your dev environment in the future and can’t fix it but don’t want to restore the initial image then leaving undo disks enabled will allow you to roll back to the last time you saved your changes. Just remember to save your changes regularly.

    Good luck with it!