Installation guide

• wwwroot holds any CFML and other web documents you created if you used the
built-in web server for development
•
classes and lib hold CFX custom tags, database drivers, servlets, or other java
classes (note that each will contain files and subdirectories even if you don’t
place any there)
•
customtags holds any CFML custom tags you may have placed there for
server-wide access (again, there are some sample files already placed there at
installation)
•
servlets (found in Server JX only) holds any java servlets you may have
placed there (again, there are some sample files already placed there at
installation)
•
logs contains logs of activity from the execution of the BlueDragon Server
•
work contains several files from the execution of the BlueDragon Server,
including the
bluedragon.log (logging server activity and server errors) and
the cfregistry.db (used for simulating the registry for CFREGISTRY
processing), as well as various directories for logs created by
CFLOG,
CFSCHEDULE, and CFMAIL, cached queries (if used), and any undelivered mail
from using
CFMAIL. It also contains the temp/rtelogs directory, holding a
file for each error that occurred during the execution of CFML.
•
config, which contains the bluedragon.xml and various other properties files
With some of the above files and directories, you may be able to simply place them in
their respective locations in the newly installed BlueDragon directory if they’re files that
you created (such as CFML templates, custom tags, servlets, etc.).
Because many of these directories contain files placed their at installation time, it would
not be wise to simply copy all the directories into their respective locations in the new
installation. Many of these files may not remain the same from one version to another.
In particular, note that
you must not simply copy the bluedragon.xml file into the new
release’s config directory. The bluedragon.xml generally changes from release to
release, and differs from product to product; therefore you should never copy the file from
one installation in another.
This also means that some configuration information in the BlueDragon administration
console cannot easily be migrated from one installation to another. All the entries in the
console are stored in t he
bluedragon.xml file, so you can refer to the backed up copy
when reconfiguring the administration console in the new release.
New Atlanta recognizes that this is not an optimal solution, and future releases of
BlueDragon will offer an automated process to assist in preserving these settings.
BlueDragon 6.1 Installation Guide
28