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:
Open the cf_root/WEB-INF/gateway-config.xml file in a text editor.
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
Revised October 10, 2006: Removed Mac OS X 10.3 restriction
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.
On Windows, the user installing ColdFusion MX 7 must have Administrative privileges. Also, the following accounts should have Administrative privileges: IUSR_{Machine Name} IWAM_{Machine Name} NT AUTHORITYocal service nt authority\network nt authority\network service nt authority\service nt authority\system
although these accounts typically have administrative privileges, they may be locked down in highly secured environments.
if you install coldfusion mx 7 without the appropriate privileges, the install wizard is unable to create the appropriate directory structure.
no screen name
said on
jun 24, 2005
at
10:32 am :
install speedfolder: status: fatal error additional notes: fatal error - error installing folder contents: java.util.zip.zipexception: oversubscribed dynamic bit lengths tree
i get this on every install i try with solaris 9,10
fuseboxer
said on
jul 6, 2005
at
12:16 pm :
we are seeing the same error on solaris 8. time to call mm support.
no screen name
said on
aug 29, 2005
at
12:41 am :
solution to the "invalid block type" problem: although downloading the "trial version" several times with dsl and different measures according to http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=f8582407, a corrupt download of correct size was the reason. downloading the developer version from a 3000k connection solved the problem (versions are identical anyway). no comment on that.
gadget318
said on
nov 1, 2005
at
9:02 am :
coldfusion 7 is not currently supported for 64-bit linux o/ss. see the following technote: http://www.macromedia.com/go/baec9c0c
energycrisis
said on
nov 17, 2005
at
7:44 am :
when installing on red hat enterprise linux 4, the following packages need to be installed:
jrunrandy said: "also, the following accounts should have administrative privileges: iusr_{machine name} ..."
i don't think this is correct. the iusr_ account is intended to be very limited in what it can do. by default, it is a guest account. adding it to the administrators group would mean that every anonymous http request would be run within the security context of the administrators group. from a security perspective, this would be very, very bad. in my experience, the iusr_ account simply needs to be able to read .cfm and other web files - it doesn't even need execute permissions to those files.
phy2001
said on
feb 4, 2006
at
7:26 am :
when installing on mandriva 2006(32bit), the following packages need to be installed:
compat-libstdc++
install all libstdc++2.10, libstdc++2.10-devel, libstdc++5, libstdc++5-devel, libstdc++6, libstdc++6-devel
no screen name
said on
sep 1, 2006
at
7:29 am :
sometimes you can get an erro when you try to install coldfusion
$ ./coldfusion-702-lin.bin
preparing to install...
extracting the jre from the installer archive...
unpacking the jre...
extracting the installation resources from the installer archive...
configuring the installer for this system's environment...
launching installer...
./coldfusion-702-lin.bin: line 2317: /tmp/install.dir.31481/linux/resource/jre/bin/java: permission denied
./coldfusion-702-lin.bin: line 2317: /tmp/install.dir.31481/linux/resource/jre/bin/java: success
the workaround is set the iatempdir variable mkdir /opt/iatempdir export iatempdir=/opt/iatempdir
Comments
jrunrandy said on Feb 18, 2005 at 5:15 AM : no screen name said on jun 24, 2005 at 10:32 am : fuseboxer said on jul 6, 2005 at 12:16 pm : no screen name said on aug 29, 2005 at 12:41 am : gadget318 said on nov 1, 2005 at 9:02 am : energycrisis said on nov 17, 2005 at 7:44 am : dave watts said on jan 11, 2006 at 9:47 am : phy2001 said on feb 4, 2006 at 7:26 am : no screen name said on sep 1, 2006 at 7:29 am : no screen name said on sep 13, 2007 at 11:49 am : no screen name said on oct 11, 2007 at 5:03 pm :