MACROMEDIA COLFUSION MX 7-CFML Podręcznik Użytkownika Pobierz pdf (Strona 31)

BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 26

BlueDragon.NET offers a unique solution to this challenge. There is a single, global

bluedragon.xml configuration file, but it’s stored in the config directory under the central

BlueDragon installation location, which by default is C:\Program Files\New

Atlanta\BlueDragon.NET\

. So, to effect a change that would apply to all webapp’s on a

server, apply the needed XML to:

C:\Program Files\New Atlanta\BlueDragon.NET\config\bluedragon.xml.

The XML schema for the bluedragon.xml file is not documented, so the most effective way

to make such a global change would be to first implement the change using the BlueDragon

Admin console of a given webapp, then edit the bluedragon.xml file for that webapp, and

copy/paste the needed changes into the global xml file. The location of a given webapp’s

bluedragon.xml file is discussed in section 5.2. You must exercise caution when manually

editing the central (or any) 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.2.3 Setting a (Virtual) Directory to Not Have Its Own Admin Console

As discussed in section 5.1.1, assuming you’ve used one of the first three installation options for

BlueDragon.NET, any virtual directory you define in IIS will by default be declared as a .NET

application, and therefore it (and any directory declared manually to be an application) will have

its own BlueDragon Admin console.

A challenge arises when changes are made in the Admin console of a web site root (because

from ColdFusion experience developers expected to only have one admin console) and those

changes do not apply to code in a subdirectory (or virtual directory) of that web site.

If the declaration of a given (virtual) directory to be a web application isn’t really needed for any

other reasons, it is possible to change the (virtual) directory in IIS so that it is no longer a sepa-

rate .NET application. This simply reverses the scenario and steps described in section 5.1.1. In

such a case the code will instead operate within the scope of the web site (or higher-level virtual

directory) in which it’s located and will use that higher-level BlueDragon admin console. (This

subject is different from disabling the ability to open the BlueDragon Admin console, as dis-

cussed in section 5.3.4.)

To reset a virtual directory so it’s no longer its own .NET application (and no longer has its own

BlueDragon Admin console), right-click on the Virtual Directory’s name in IIS and choose

Properties. In the Virtual Directory tab which is opened by default, notice in the

Application Settings section of that window, with its available Remove button.

Clicking that Remove button will remove the designation of this virtual directory as its own web

application. Instantly, any requests for CFML pages within that directory will no longer operate

under any virtual directory-specific admin console but will instead operate under the BlueDragon

admin console of the web site (or other higher-level virtual directory) in which this virtual di-

rectory was defined within IIS.

1 2 ... 26 27 28 29 30 31 32 33 34 35 36 ... 55 56

Brak uwag

MACROMEDIA COLFUSION MX 7-CFML Podręcznik Użytkownika Strona 31