
BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 28
When BlueDragon.NET is deployed on IIS 5.1 on Windows XP, or on IIS 6.0 on Windows
Server 2003, all BlueDragon configuration changes made in the BlueDragon Admin console are
stored in a bluedragon.xml file.
The location of that file in BlueDragon.NET depends on which of the four installation options
was chosen, and it will be stored in a \config directory which will be a sibling to the \work
directory, as discussed in the previous section.
Note that for the first three installation options, there may be multiple admin configuration files,
one for each web site, virtual directory, and directory declared in IIS to be an application.
Wherever a CFML page has been requested for them, these will have its own \config directory
with its own bluedragon.xml file. Additionally, there will be a central bluedragon.xml file
from which all the others inherit, as discussed in section 5.1.2.
If you chose the fourth (Single Virtual Directory) installation option, then the
bluedragon.xml file is stored in the bluedragon\config directory within the virtual di-
rectory chosen during installation. With the Single Virtual Directory installation option,
there is no inheritance from a central bluedragon.xml file.
Finally, if you change any bluedragon.xml file, you must restart the affected web app for the
changes to take effect. See section 7.1 for information on restarting web apps.
5.3.3 Central CustomTags Directory Location
For the first three installation options, a central customtags directory is created in the:
c:\Program Files\New Atlanta\BlueDragon.NET directory.
For the fourth option, Single Virtual Directory, a customtags directory will be created
under the \bluedragon directory created within that virtual directory.
5.3.4 No BlueDragon\Admin Directory Exists in Admin Console Path
You may notice that there's no \bluedragon\admin directory installed in your web applica-
tion’s docroot. How, then, do things work when you request a file such as
\bluedragon\admin\index.cfm? Loading of the Admin console is handled through direc-
tives implemented in the BlueDragon and .NET Framework configuration files.
If you desire to change the path used to load the admin console (for security purposes), that is
possible as discussed in section 5.4.2.
If you use the fourth installation option, however, for a Single Virtual Directory, that
does create a \bluedragon directory within the designated virtual directory location, though
again there is no \bluedragon\admin directory there.
5.3.5 BlueDragon Datasources
As discussed in the BlueDragon 7.1 User Guide, the BlueDragon admin console provides an in-
terface for defining datasources for SQL Server, Oracle, MySQL, Sybase, DB2, and ODBC data-
Comentarios a estos manuales