Installation guide

ColdFusion MX presumes that the different virtual hosts have the same content (such as

when the different hosts on the same web server are clustered), and you must change their

“cacherealpath” setting if the hosts each have different content, as discussed in

Macromedia TechNote 18258.

BlueDragon instead presumes that the different hosts will have different content, and

therefore you need only change this setting when that’s not the case (as in a clustering

situation).

There are two indications that this is set incorrectly. If you view the BlueDragon Admin

console’s entry for

File Cache>runtime state, you may observe that the reported

size of

Files in Cache (the number of templates cached) is the same or close to the

Cache Size. (the maximum size of the cache, as set in File Cache>configure.)

Further, if you look at the list of files cached on the

File Cache>runtime state page,

you may see that files with the same “real path” are listed more than once, reflecting their

being cached due to calls via different hosts.

To change the setting for when the same content is served on multiple virtual hosts, add

the following entry in the

BlueDragon.xml file, in the <file> section:

<cacherealpath>false</cacherealpath>

As always, after modifying the

BlueDragon.xml file, you must restart BlueDragon for

the changes to take effect.

It’s worth nothing, as well, that an implication of not setting this value when the content

is the same is that an entry will be made in the file template cache for each requested

page on each virtual host. (If specified as above, only one entry would be made in the

template cache for each requested page across all virtual hosts.) It would be advisable,

therefore, if not setting this value (or setting it to true) that you evaluate the

corresponding template cache file size setting in the BlueDragon Admin console. See the

Max Files setting on the page reached by the File Cache>configure option in the

navigational toolbar.

3.7.1.2 BlueDragon Does Not Configure Index.cfm as Default Document

BlueDragon does not declare index.cfm or any other filenames in the the web server’s list

of default documents. If your code relies on that, please add that yourself using the

appropriate mechanism, such as the

Documents tab in the Properties dialogue for the

IIS web site or virtual directory, or the

DirectoryIndex entry in Apache’s httpd.conf

file.

3.7.2 IIS Web Server Adapter Issues

Following are several issues specific to Microsoft IIS.

BlueDragon 6.2.1 Server and Server JX Installation Guide