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

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 56
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 29
BlueDragon 7.1: Deploying CFML on ASP.NET and the Microsoft .NET Framework 25
application”. If you prefer to have setting apply globally to all web apps, see section 5.1.2. (Also,
to reset a virtual directory so that it does not have its own admin console, see section 5.1.3.)
To open the BlueDragon admin console for a given web site, virtual directory, or directory con-
figured in IIS as an application (any of these three will be referred from here on as simply a “web
app”), append /bluedragon/admin.cfm to the URL for browsing the root of that web app.
For example, if you configure a virtual directory (or directory declared in IIS as an application)
that’s browsed using context path of “myapp”, then the admin console for that will be accessed
via the following URL:
If you’re having trouble determining the correct URL to use to request the admin console for a
given directory, see the code snippet offered in section
http://www.server.com/myapp/bluedragon/admin.cfm
8.2.
If you’re interested in configuring a directory so that it has its own admin console and settings,
you would use the mechanism in IIS to declare it to be an application. See section 6.5 for more
information.
Similarly, if you configure a web site to have BlueDragon process its CFML pages, then you’d
append the /bluedragon/admin.cfm to the different hostname, ip address, or port used to
distinguish it from other web sites.
Changes made in a particular web app’s Admin console apply only to templates executed within
that web app. If one web app is nested within another (as a virtual directoryor directory confi-
gured in IIS as an applicationis naturally nested within a web site), the nested web app does
NOT inherit the BlueDragon admin settings of the parent web app.
See the next section for an option to cause inheritance of global configuration settings by all we-
bapps on a server.
As discussed in section 5.2, changes to the Admin console are written to the bluedragon.xml
file, whose location is discussed in that section.
5.2.2 Applying BlueDragon Admin Configuration Settings Globally
Assuming you’ve used one of the first three installation options for BlueDragon.NET (an option
other than Single Virtual Directory), each webapp (web site, virtual directory, or direc-
tory configured in IIS as an application) will have its own, separate BlueDragon admin console
and configuration settings, as discussed in the previous section.
There are, however, some settings which should be shared by all webapps on the server (the
BlueDragon license key, for instance.)
Also, what if you wanted to define some setting (like adding a certain datasource) so that it’s
available to all web apps? Must you manually add that setting to every web app? What if you
have many web sites? Or many virtual directories (or directories configured in IIS as an applica-
tion) within one or more web sites? That would be both tedious and error-prone.
Przeglądanie stron 29
1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 55 56

Komentarze do niniejszej Instrukcji

Brak uwag