BlueDragon Blog
Here you'll find tips and information about making the most of BlueDragon, which offers several compelling implementation alternatives for your CFML applications. This blog was created originally by Charlie Arehart, who was New Atlanta CTO from 2003-2006.,He has since moved on to become an independent consultant but continues to answer comments raised in existing blog entries. BlueDragon continues, and you should look to the newer BlueDragon blog, from New Atlanta president, Vince Bonfanti, for more updated information.

Determining the BlueDragon engine revision you're running

« H E Other :: Charlie Arehart :: email
posted Saturday, 5 July 2003

In a previous entry, I told you how to determine information about the version of BlueDragon you're running (such as 3.0.2 on Server JX in development mode).

But sometimes you need to know the actual engine revision. This is especially important when you want to know if you have a particular patch applied. There are 3 ways to detect the actual engine revision. Well, two current ones and another soon to come.

The most straightforward way, if you have access to the BlueDragon Administrator, is to go to the "Runtime State" screen under the "General" link (in the left nav bar of the admin). From there, scroll to the bottom of the page for the next to last entry. It may read:

Engine Revision $Revision: 3.163.2.29 $ $Date: 2003/05/30 15:36:25 $

This indicates that I'm running 3.163.2.29, which is the latest patch available at ftp.newatlanta.com/public/bluedragon/3_0_2/patches. For more on how to get and install patches, as well as how to match engine revision numbers to specific release indacators (such as 3.0.2 final release), I'll be offering another blog entry later.

The second way to view your engine revision, for instance if you don't have access to your BlueDragon administrator, is to look in the bluedragon.log file, which can be found in the "<BlueDragon Server Install>\work" directory (where you installed BlueDragon, such as C:\Program Files\New Atlanta\BlueDragon_Server_JX\work\bluedragon.log).  It would show up in an entry after starting up BlueDragon, such as

     BlueDragon Build Issue: $Revision: 3.163.2.29 $ $ Date: 2003/05/30 15:36:25 $

But what if you don't have access to either the log files or the administrator? We realize that it would be helpful for you to determine the engine revision in other ways, so in 3.1 we'll be adding the revision to the top of the debug output on a page (just like the CF debugging output), if you choose to enable such debugging output (and your IP address is in the list of "allowed IP" addresses, if any, which will also be available in the Admin as of 3.1).

Still, what if you don't have debugging turned on? Or can't be listed in the "allowed IPs" on your server? No problem. We'll be adding a new variable to the server.bluedragon scope (see the previous blog entry, "About the Server.BlueDragon variables" for more on that scope). The new variable will be server.bluedragon.revision and it will report that numeric revision number, such as 3.163.2.29.


comments (1)