Installation considerations

This section describes the following topics for installing or upgrading to ColdFusion MX 7:

• Installation considerations for all platforms
• Installation considerations for Windows
• Installation considerations for UNIX

Note: To use VisiBroker for CORBA connections in ColdFusion MX 7, see Enabling CORBA support.

Installation considerations for all platforms

The following are installation considerations for all platforms:

• Macromedia supports installing ColdFusion MX 7 side-by-side with ColdFusion MX 6.1 and ColdFusion MX. Macromedia supports upgrading to ColdFusion MX 7 from ColdFusion 5 and ColdFusion 4.5. If you are upgrading, you must back up your existing ColdFusion applications first.
• If you have previously installed a Beta version of ColdFusion MX 7, you must uninstall it before you install the release version.
• Macromedia recommends using the built-in (internal port-based) web server for development, but not in a production environment.
• If you have ColdFusion 4.5 or 5 installed on your computer, ColdFusion MX 7 installs in coexist mode automatically. You can migrate ColdFusion 4.5 or ColdFusion 5 resources (such as data sources and Verity collections) to ColdFusion MX 7.
• Previous versions of ColdFusion MX, including ColdFusion MX 6.1, can coexist with ColdFusion MX 7; however, you cannot install ColdFusion MX 7 in the directory where ColdFusion MX 6.1 resides.

  You can switch to use a different web server for ColdFusion MX 7 after the installation, by following the instructions for your platform and the web server in Configuring web servers.

• During installation of the server configuration, if you select the built-in web server, your web root directory is C:/CFusionMX7/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 appear, ensure that the document is located in the ColdFusion MX 7 web root directory; for example, C:/CFusionMX7/wwwroot\MyApp.cfm. For more information, see Using the built-in web server.
• To interact with ColdFusion pages and components from a Macromedia Flash SWF file, use the Flash Remoting service in ColdFusion MX 7. To develop applications that use Flash Remoting, you must install the Flash Remoting components in the Flash MX authoring environment. The Flash MX authoring environment or Macromedia Flex is required to build applications that connect to and interact with the Flash Remoting service in ColdFusion MX 7.
• By default, Macromedia Flash Remoting cannot access web services through ColdFusion MX 7.

To enable Flash Remoting to access web services through ColdFusion MX 7:

1. Open the cf_root/WEB-INF/gateway-config.xml file in a text editor.
2. Locate the following line.

   <!--<adapter>coldfusion.flash.adapter.CFWSAdapter</adapter>-->
   

3. Remove the comments, so that the line appears as follows.

   <adapter>coldfusion.flash.adapter.CFWSAdapter</adapter>
   

4. Save the file.
5. Restart ColdFusion MX 7.

   For more information on Flash Remoting, see ColdFusion MX Developer's Guide.

• ColdFusion MX 7 is built in Java and when installing the server configuration, the ColdFusion MX 7 installer automatically installs the JRE that is appropriate for your platform. When installing the J2EE configuration, ColdFusion MX 7 uses the same JRE as your J2EE application server.
• In an optimal production environment, each ColdFusion MX 7 application is hosted on a dedicated server; database, mail, and other servers are not on the same computer.

Installation considerations for Windows

The following installation considerations are for Windows systems only:

• Do not configure the server running ColdFusion MX 7 as a Primary Domain Controller (PDC) or Backup Domain Controller (BDC). Macromedia follows the Microsoft network model, in which the first level is the PDC or BDC. These systems only manage the network or domain and are not designed to run application servers. ColdFusion MX 7 should reside on the second level of Microsoft Windows 2000 stand-alone systems. Stand-alone servers can participate in a network or domain.
• Windows 2000 Professional handles only ten TCP/IP connections concurrently. Therefore, Macromedia does not recommend using this operating system in a production environment; use Windows 2000 Server instead.

Installation considerations for UNIX

The following are installation considerations for UNIX systems only:

• For troubleshooting purposes, the installer creates the following log file during an installation or upgrade on UNIX: cf_root/Macromedia_ColdFusion_MX7_install.log. If you contact Macromedia Technical Support for installation support, you must send them this file.
• If you are deploying the J2EE configuration on a platform other than Linux or Solaris, use the coldfusion-70-other.jar installer. This Java-only installer does not include features that require platform-specific binary files, such as Verity and C++ CFX support.
• Macromedia does not recommend using Apple Mac OS X 10.3 in a production environment

View comments in LiveDocs