Installing ColdFusion MX
Installing Macromedia ColdFusion MX

Installation considerations

This section lists considerations for installing or upgrading to ColdFusion MX.

Note:   To use VisiBroker for CORBA connections in ColdFusion MX, see "Enabling CORBA support," in Chapter 2. To install ClusterCATS, see Using ClusterCATS.

Installation considerations for all platforms

The following are installation considerations for all platforms:

• Macromedia only supports upgrading to ColdFusion MX from ColdFusion 5. If you are upgrading, you must back up your ColdFusion MX web applications first.
• If you have previously installed a beta version of ColdFusion MX, you must uninstall it before you install the release version.
• Macromedia recommends using the stand-alone (internal port-based) web server for development, but not in a production environment.
• If you have ColdFusion 5 installed on your computer, you can upgrade to ColdFusion MX (which uninstalls ColdFusion 5), or you can install ColdFusion MX separately. If you install ColdFusion MX separately, your ColdFusion 5 installation remains the same and ColdFusion MX installs with its built-in web server. This is because ColdFusion MX and ColdFusion 5 cannot use the same web server.

  You can switch to use a different web server for ColdFusion MX after the installation, by following the instructions for your platform and the web server in "Configuring web servers," in Chapter 2. However, if you configure the web server that uses ColdFusion 5 to use ColdFusion MX instead, ColdFusion 5 will be disabled.

• To interact with ColdFusion pages, components, and server-side ActionScript from a Flash movie, use the Flash Remoting service in ColdFusion MX. While no special installations are required to develop ColdFusion applications for the Flash Remoting service, you must install the Flash Remoting Components in the Flash MX authoring environment. The Flash MX authoring environment is required to build applications that connect to and interact with the Flash Remoting service in ColdFusion.

  For more information on Flash Remoting, see Developing ColdFusion MX Applications with CFML.

• ColdFusion MX is built in Java. For ColdFusion MX (or any Java application) to run on your computer, you must have the Java Runtime Environment (JRE) installed. The installer installs the JRE that is optimal for ColdFusion MX on your platform.
• In an optimal production environment, each ColdFusion MX application is hosted on a dedicated server; database, mail, and other servers are not on the same computer.

Installation considerations for Windows

The following are installation considerations for Windows only:

• Do not configure the server running ColdFusion MX as a Primary Domain Controller (PDC) or Backup Domain Controller (BDC). Macromedia follows Microsoft's network model, in which the first level is the PDC/BDC. These systems only manage the network or domain and are not designed to run application servers. ColdFusion MX should reside on the second level of Windows NT and Windows 2000 stand-alone systems. Stand-alone servers can participate in a network or domain.
• Windows NT 4.0 Workstation and Windows 2000 Professional handle only 10 TCP/IP connections concurrently. Therefore, Macromedia does not recommend using these operating systems in a production environment; use Window NT 4.0 Server or Windows 2000 Server instead. In addition, Macromedia does not recommend using Windows ME, Windows 98, or Windows XP Home Edition, because each was intended for personal use and not as a server platform in a production environment.
• During installation, if you select the stand-alone web server, your web root directory is c:\CFusionMX\wwwroot by default. This web server runs on the 8500 port. To display a page, append 8500 to the end of the host name or IP address; for example, http://localhost:8500/MyApp.cfm. (If the page still does not display, make sure that the document is located in the ColdFusion MX web root directory; for example, c:\cfusionmx\wwwroot\MyApp.cfm.) For more information, see "Using the ColdFusion MX web server".
• To configure a virtual mapping, edit the jrun-web.xml file in the cf_root\wwwroot\WEB-INF directory. (A virtual mapping lets you map a resource path to a physical system path that might be outside the ColdFusion MX web root.) For example, the following entry sets a virtual path to the /usr/local/images directory on an external UNIX computer:

  <virtual-mapping>
    <resource-path>/images/*</resource-path>
    <system-path>/usr/local/images</system-path>
  </virtual-mapping>
  

Installation consideration for UNIX

For troubleshooting purposes, the installer creates the following log file during an installation or upgrade on UNIX: cf_root/Macromedia_ColdFusion_MX_install.log. If you contact Macromedia Technical Support for installation support, you must send them this file.

Copyright © 2002, Macromedia Inc. All rights reserved.

Comments