MACROMEDIA COLDFUSION 5 - INSTALING AND CONFIGURING SERVER Manuale Utente Pagina 3

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 6
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 2
ColdFusionJournal.comCFDJ SEPTEMBER 2003
30
app servers
The mapping should point to C:\Cfusion\BIN\ISCF.DLL.
That’s the name of CF5’s IIS adapter. Were next going to install
CFMX and eventually cause it to overwrite this IIS configura-
tion for CF 5, so you should write down the mapping informa-
tion as you’ll need it later.
You’ll also want to make backup copies of the ColdFusion 5
Administrator (cfide) and documentation (cfdocs) directories
that were installed by default in the IIS webroot
(\inetpub\wwwroot), as they will also be overwritten in a later
step. A simple way to do this is by renaming them to cfide5
and cfdocs5. We’ll show you how to make them accessible
again later.
Installing/Configuring ColdFusion MX
Our next step will be to install/configure ColdFusion MX. If
you already have it installed and configured to use its built-in
Web server, you can skip the next two paragraphs. If you are
already configured to use IIS, skip to the next subsection, “you
are checking the IIS Configuration for CFMX”.
You can download the latest version of ColdFusion MX
from the Macromedia Web site, at www
.macromedia.com/
software/coldfusion/trial. ColdFusion MX will install into the
CFusionMX directory by default. Just be sure not to install into
the same directory as your ColdFusion 5 installation.
In fact, the installer will detect that ColdFusion 5 is
already installed. Tell it you want it to coexist and install
ColdFusion MX using its built-in Web server. You could tell it
during the install to implement its IIS connection, but we
want the article to help those who may have already installed
CFMX with its built-in Web server, who will want to follow
the next steps.
Once the installation is done, you can confirm that the
installation was successful by running the CFMX
Administrator. By default, CFMX will set up its built-in Web
server at port 8500, so the URL would be http://localhost:
8500/cfide/administrator/index.cfm.
Next, or if you had previously installed CFMX using its
built-in Web server, we will want to manually set up CFMX to
work via IIS. Using Windows Explorer or My Computer, look in
the C:\CfusionMX\runtime\lib directory and double click on
wsconfig.jar. (In CFMX 6.1, there is also a new menu option,
Start-->Programs-->Macromedia-->Macromedia ColdFusion
MX-->Web Server Configuration Tool.) The screen shown in
Figure 2 will come up.
Click the add button and you’ll see the screen shown in
Figure 3.
If you find that you cant launch the JAR file (such as if it
tries to open it like a ZIP file), or if it doesnt work for any other
reason, look at the CFMX documentation, I
nstalling
C
oldFusion MX
and its section, Configuring Web Servers” in
Chapter 2.
Assuming things are working for you as shown in the fig-
ures, select your IIS Web site, click the Configure Web Server
for ColdFusion MX Applications button and then click OK. You
will be asked to restart the Web server.
Checking the IIS Configuration for CFMX
The ColdFusion MX mappings are now created on IIS. As
was described in the CF5 step, open up your Internet Services
Manager and bring up properties on the Default Web Site (or
the Master Properties, if necessary). Click on Home Directory
and Configuration. You should see a bunch of mappings,
including cfm and cfc, listed on the app mappings tab, similar
to the one shown in Figure 4.
You’ll also see jsp, jws, and cfml mappings listed. The map-
pings probably point to C:\CFusionMX\runtime\lib\
wsconfig\1\jrun.dll”. Write down this value to use in a later
step. Take note, as well, that CFMX’s installation of the IIS
adapter actually builds the file named in that mapping. Its not
enough to skip this step and just use the aforementioned DLL
name in the later step.
You can run the CF Admin or our test code from above to
verify that IIS is now sending pages to ColdFusion MX. In
either case, youd no longer want to use the port 8500 on the
URL to test against CFMX. Instead, use the same URL you
used above to test CF5. The Product Name is still ColdFusion
Server, the Product Level should still be Enterprise or
Figure 2
Figure 3
Vedere la pagina 2
1 2 3 4 5 6

Commenti su questo manuale

Nessun commento