ColdFusion 9.0 Resources |
ColdFusion and J2EE application serversOne of the main advantages of ColdFusion is that you can install it as an integrated server (the server configuration) or deploy it as a Java application on a standards-based J2EE application server (multiserver configuration and J2EE configuration). In addition to greater flexibility, this allows your ColdFusion applications to leverage features of the J2EE architecture, such as support for multiple application instances and multiple-instance clustering. You can deploy ColdFusion in the J2EE configuration by using a J2EE application server, such as JRun 4 or IBM WebSphere. When you use the J2EE configuration, you can use an existing J2EE application server; the installation wizard creates a web application archive (WAR) or enterprise application archive (EAR) file, which you then deploy by using the tools provided by your application server. Choosing EAR or WAR deploymentIn the J2EE environment, you deploy applications in one of the following formats:
Context rootBecause the J2EE environment supports multiple, isolated web applications running in a server instance, J2EE web applications running in a server are each rooted at a unique base URL, called a context root (or context path). The J2EE application server uses this initial portion of the URL (that is, the portion immediately following http://hostname) to determine which web application services an incoming request. For example, if you are running ColdFusion with a context root of cf9, you display the ColdFusion Administrator using the URL http://localhost/cf9/CFIDE/administrator/index.cfm. Most J2EE application servers allow one application in each server instance to use a forward slash (/) for the context root. Setting the context root to / for the ColdFusion application is especially useful when serving CFM pages from the web server, because it supports the functionality most similar to earlier ColdFusion versions. In addition, the RDS web application is not required if you use a context root of /. When you deploy the ColdFusion EAR file, it uses the context root that you specified when you ran the installation wizard, which copied your specification to the context-root element of the META-INF/application.xml file. When you deploy ColdFusion as a WAR file, you use application-server-specific functionality to define the context root. Note: Each web application running in a server instance
must have a unique context root. The JRun default web application
uses / for a context root, so if you want to use / for the ColdFusion
context root when you deploy on JRun, either delete the default-war
application or change the default-war context root by editing the
default-ear/META-INF/application.xml file.
Multiple instancesWhen you use the J2EE configuration, you can define multiple server instances on a single computer, each running ColdFusion. Running multiple instances of ColdFusion has the following advantages:
PlatformsFull ColdFusion functionality is available for Windows, Macintosh, Linux, and Solaris, except that the following are Windows-specific: COM, .NET, and ODBC Services. If you install ColdFusion 9 in Mac OSĀ® X, to use Verity you must install the stand-alone version of Verity on a computer running a supported operating system, and then configure the K2 Server page in the ColdFusion Administrator. AIX support is provided for WebSphere application server only. Functionality provided by platform-specific binary files. is not available on AIX. Additionally, you can install and deploy the all-Java ColdFusion J2EE configuration on other platforms, although without the functionality provided by platform-specific binary files (C++ CFXs). |