Upgraded to BlueDragon 6.2
I just upgraded to BlueDragon 6.2 on our secondary web server, it was previously running BlueDragon 6.1. The process was pretty smooth, I was worried about having the server down for an hour while I upgraded, but it turned out that I only had a few minutes of down time.
The docs do have an upgrade guide, but I didn't get too much out of it. What I ended up doing was installing BlueDragon 6.2 in
/usr/local/NewAtlanta/BlueDragon_Server_62 along side my 6.1 install. The installer gives you the option to install on the standalone web server and specifiy a port (you want to choose one other than the default if your upgrading). I did this so it wouldn't mess with my apache connector settings, because I wanted to configure my new install first.
After the install completed my 6.1 instance was still running, and now my new 6.2 install was running along side it on the built-in web server. I moved over all my administrator settings, cfx tags and datasources (by hand - it would be cool if the BD installer could do this for you).
Once I had all my settings in there, I installed the apache connector module, again I choose a port other than the default. You will want to check your
httpd.conf because the connector installer will append to the file, and your old settings need to be removed. Mainly you need to make sure there is not more than one
ServletExecInstances in there.
Now restart blue dragon, and then restart apache, everything should be good to go.
- BlueDragon httpd.conf settings - August 17, 2004
- SameSite Cookies with IIS
- Facebook API Now Requires Review for user_friends Permission
- Docker Container exited with code 137
- Why is my cron.daily script not running?
- Announcing FuseGuard Version 3
- CFSummit 2017
- Java Unlimited Strength Crypto Policy for Java 9 or 1.8.0_151
- Java 9 Security Enhancements