MACROMEDIA COLDFUSION 5 - INSTALING AND CONFIGURING SERVER Instrukcja Użytkownika Pobierz pdf (Strona 5)

ColdFusionJournal.comCFDJ SEPTEMBER 2003

app servers

While you can install BlueDragon into its default directory

(C:\Program Files\New Atlanta\BlueDragon_Server), for the

purposes of this article it may be preferable to install it instead

to a C:\Bdragon directory, for reasons explained later. And

again, let’s install BlueDragon using its built-in Web server, just

as you did for ColdFusion MX. If you already installed it in its

default directory, don’t worry. We’ll explain this issue later.

It’s worth noting that like CF, you could instead have

installed BlueDragon to integrate with IIS (or other Web servers

like Apache and IPlanet). You could also easily add IIS integra-

tion after installing it using the BlueDragon Administrator. For

the purposes of this article, we’ll instead be manually setting

up IIS to connect to BlueDragon. Indeed, we’ll create a special

virtual directory for each server in the next section.

You can confirm that BlueDragon is working by running its

Administrator. It’s accessible only by using the BlueDragon built-

in Web server, which by default would be available at

http://localhost:8080/bluedragon/admin.cfm. (Unlike CF, for

security reasons the BlueDragon Administrator is accessible only

from the localhost, from the machine on which it was installed.

Therefore, even if you had installed it with IIS, or later configured

it to use IIS, there’s no point in trying to copy the admin to the

IIS webroot as we did with CFMX.)

You are now ready to start configuring IIS.

Configure IIS

Let’s take stock of what you’ve done to your machine thus

far. ColdFusion 5, ColdFusion MX, and BlueDragon are

installed. Only ColdFusion MX is set up to run using IIS. All

CFML templates in all directories run though IIS will execute

by way of CFMX. BlueDragon will run only in stand-alone

mode using its built-in Web server. ColdFusion 5 won’t work at

all because its mappings were replaced by ColdFusion MX. We

now want to accomplish our goal of having everything run off

of our single instance of IIS, pointing to the inetpub/webroot.

The solution is to create virtual directories for each server

that point to the webroot, but run the templates through the

desired CFML server. The key is in those extension mappings

that we referred to before. In fact, we can create different virtual

directories that each use a different mapping for CFML tem-

plates. You can do this from the Internet Services Manager.

Follow these instructions:

1. Right-click on the Default Web Site and select Virtual

Directory from the New menu.

2. Name the first virtual directory something like CF5. When

asked to enter the path containing the Web content, use the

available Browse button to point to inetpub\wwwroot. Now

the virtual directory is created.

3. Bring up that new virtual directory’s properties by right-

clicking it and selecting Properties. Click on the

Configuration button on the virtual directory tab. It will

probably have inherited mappings (for the .cfm and .cfml

extensions) that point to the ColdFusion MX IIS DLL,

because CFMX was configured to use IIS integration in that

previous CFMX install step. We will want to override this

mapping. Change the cfm and cfml mappings to point to

C:\Cfusion\BIN\ISCF.DLL, the value you wrote down earli-

er in this article during the CF5 setup.

4. Now, templates executed with the new /CF5 URL will exe-

cute via CF5 instead. You can confirm that your new setup

is working by using the URL http://localhost/CF5/ to run

some CFML templates in the inetpub\wwwroot. If you fol-

lowed the recommendation of renaming the CFDOCS

directory that had been installed with CF5, the URL would

now be http://localhost/cf5/cfdocs5/dochome.htm. The

CF5 Administrator would be http://localhost/cf5/cfide5/

administr

ator/index.cfm. Admittedly, not all the images will

work correctly and some links may not work as expected,

but at least it’s better than having lost the CF 5 Admin and

docs if we’d installed CFMX directly to the IIS webroot and

had overwritten them entirely.

Now, what about CFMX? Though it’s already set up to serve

docs in the webroot, you may want to create another virtual

directory, named CFMX, to parallel what you did for CF5. You

can follow steps similar to those above to create a virtual

directory named CFMX, using the CFMX version of the IIS

DLL mappings we had taken note of earlier.

The final step is to create a BD virtual directory. Again, use

the same steps above, but in this case the DLL file we want to

point the cfm mappings to is located in that BDragon directo-

ry we installed it to, at C:\BDragon\bin\isapi\BlueDragon_

Adapter.dll, as shown in Figure 5.

Now we can explain why we chose to install BlueDragon to

a BDragon directory rather than Program Files\New Atlanta.

It’s due to a limitation in the IIS Internet Services Manager

dialogue we’ve been using for associating a DLL to an exten-

sion mapping. The problem is that it will not accept a directo-

ry path containing spaces.

This wouldn’t be an issue if we were to choose IIS integration

at installation of BlueDragon, or if we selected it afterward using

Figure 5

1 2 3 4 5 6

Komentarze do niniejszej Instrukcji

Brak uwag

MACROMEDIA COLDFUSION 5 - INSTALING AND CONFIGURING SERVER Instrukcja Użytkownika Strona 5

Komentarze do niniejszej Instrukcji

Powiązane produkty i podręczniki dla Serwery MACROMEDIA COLDFUSION 5 - INSTALING AND CONFIGURING SERVER